Huawei E3372 Hilink To Stick Mode

Hullo All,

I'chiliad hoping someone here either has direct experience with these things, or like.

For those who aren't aware, the E3372-607 comes in a range of flavors, but normally its in what'due south known equally Hullo-Link fashion. This essentially creates an extra level of NAT whereby you connect to a web interface at 192.168.8.i whilst the device itself gets its IP for the 4G provider and routes it accordingly. I've substantially flashed the firmware (21.200.07.00.00) to put information technology in "Stick" mode which in theory ways it volition go the IP from the ISP.

This works in Windows if yous have the drivers loaded. In Linux however, it appears to exist attempting to get an IP, merely never really gets there... On one hand it looks similar it connects, then fails, but it never obtains an IP.

If you disconnect and reconnect the device, lsusb will show the device is in Mass Storage mode. This can exist corrected with the control:
usb_modeswitch -5 12d1 -p 14fe -c /etc/usb_modeswitch.d/12d1\:14fe

The contents of the same file is:

TargetProduct=0x14fe MessageContent="55534243123456780000000000000011063000000000010000000000000000"

I'd appreciate anyone who has experience with nmcli mmcli etc etc who tin betoken me in the right direction... I ultimately need to brand this work with both Optus and Telstra SIM Cards.

root@NanoPi-NEO:~# lscpu Architecture:          armv7l Byte Order:            Little Endian CPU(south):                4 On-line CPU(south) listing:   0-3 Thread(s) per cadre:    i Core(southward) per socket:    4 Socket(due south):             1 Model name:            ARMv7 Processor rev five (v7l) CPU max MHz:           1008.0000 CPU min MHz:           480.0000

root@NanoPi-NEO:~# lsmod Module                  Size  Used by cdc_mbim               16384  0 cdc_ncm                24576  one cdc_mbim nls_ascii              16384  one 8189es               1024000  0 brcmfmac              180224  0 brcmutil               16384  1 brcmfmac xradio_wlan           110592  0 88XXau               1753088  0 8821cu               1683456  0 g_mass_storage         16384  0

root@NanoPi-NEO:~# lsusb Charabanc 008 Device 001: ID 1d6b:0001 Linux Foundation ane.one root hub Passenger vehicle 005 Device 002: ID 12d1:155e Huawei Technologies Co., Ltd. Jitney 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Omnibus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation ii.0 root hub Motorcoach 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation ii.0 root hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@NanoPi-NEO:~# mmcli -m 0  /org/freedesktop/ModemManager1/Modem/0 (device id 'effca7df7e7b12103fa5c64a09e26cd2d2491590')   -------------------------   Hardware |   manufacturer: 'huawei'            |          model: 'E3372'            |       revision: '21.200.07.00.00'            |      supported: 'gsm-umts'            |        current: 'gsm-umts'            |   equipment id: '86XXX'   -------------------------   System   |         device: '/sys/devices/platform/soc/1c1d000.usb/usb5/5-1'            |        drivers: 'option1, cdc_ncm'            |         plugin: 'Huawei'            |   primary port: 'ttyUSB2'            |          ports: 'ttyUSB0 (at), wwx001e101f0000 (net), ttyUSB2 (at)'   -------------------------   Numbers  |           own : '+61468XXXXXX'   -------------------------   Status   |           lock: 'none'            | unlock retries: 'sim-pivot (3), sim-pin2 (3), sim-puk (x), sim-puk2 (10)'            |          state: 'continued'            |    power state: 'on'            |    access tech: 'lte'            | signal quality: '100' (recent)   -------------------------   Modes    |      supported: 'allowed: 2g; preferred: none            |                  immune: 3g; preferred: none            |                  allowed: 4g; preferred: none            |                  allowed: 2g, 3g, 4g; preferred: none'            |        electric current: 'allowed: 2g, 3g, 4g; preferred: none'   -------------------------   Bands    |      supported: 'unknown'            |        current: 'unknown'   -------------------------   IP       |      supported: 'ipv4'   -------------------------   3GPP     |           imei: '86XXX'            |  enabled locks: 'none'            |    operator id: '50502'            |  operator name: 'amaysim'            |   subscription: 'unknown'            |   registration: 'home'   -------------------------   SIM      |           path: '/org/freedesktop/ModemManager1/SIM/0'    -------------------------   Bearers  |          paths: '/org/freedesktop/ModemManager1/Bearer/0'

root@NanoPi-NEO:~# systemctl status ModemManager ● ModemManager.service - Modem Manager    Loaded: loaded (/lib/systemd/arrangement/ModemManager.service; enabled; vendor preset: enabled)    Active: active (running) since Thu 2021-04-29 05:05:03 UTC; 27s agone  Primary PID: 473 (ModemManager)    CGroup: /system.slice/ModemManager.service            └─473 /usr/sbin/ModemManager  April 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered) Apr 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Unproblematic connect started... Apr 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Simple connect state (4/8): Wait to get fully enabled Apr 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Simple connect state (five/8): Register Apr 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Simple connect state (vi/eight): Bearer Apr 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Unproblematic connect state (seven/8): Connect April 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: country inverse (registered -> connecting) Apr 29 05:05:28 NanoPi-NEO ModemManager[473]: <warn>  Couldn't find associated cdc-wdm port for 'internet/wwx001e101f0000' April 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Modem /org/freedesktop/ModemManager1/Modem/0: state inverse (connecting -> connected) Apr 29 05:05:28 NanoPi-NEO ModemManager[473]: <info>  Simple connect state (8/8): All done

root@NanoPi-NEO:~# ifconfig eth0      Link encap:Ethernet  HWaddr 02:81:35:58:b9:ab             inet addr:192.168.10.6  Bcast:192.168.ten.255  Mask:255.255.255.0           inet6 addr: fe80::bc73:ccfa:e22e:c61e/64 Scope:Link           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:1528 errors:0 dropped:0 overruns:0 frame:0           TX packets:993 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:1000           RX bytes:133876 (133.eight KB)  TX bytes:113723 (113.7 KB)           Interrupt:40  lo        Link encap:Local Loopback             inet addr:127.0.0.1  Mask:255.0.0.0           inet6 addr: ::i/128 Scope:Host           Upwards LOOPBACK RUNNING  MTU:65536  Metric:1           RX packets:802 errors:0 dropped:0 overruns:0 frame:0           TX packets:802 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:yard           RX bytes:120515 (120.v KB)  TX bytes:120515 (120.5 KB)  wwx001e101f0000 Link encap:Ethernet  HWaddr 00:1e:10:1f:00:00             Upward BROADCAST MULTICAST  MTU:1500  Metric:1           RX packets:192 errors:0 dropped:0 overruns:0 frame:0           TX packets:163 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:1000           RX bytes:8832 (8.viii KB)  TX bytes:55494 (55.4 KB)

root@NanoPi-NEO:~# nmcli d DEVICE   Blazon      STATE                                  Connexion          eth0     ethernet  connected                              Wired connection 1 ttyUSB2  gsm       connecting (getting IP configuration)  Optus              lo       loopback  unmanaged

I believe I've solved the issue although I'm not sure what the stability is similar at this point. I've also non tested it against a Telstra SIM at this point.

The MessageContent in usb_modeswitch was non correct. Beneath is the correct one versus the one-time i (OP) but commented out.

root@NanoPi-NEO:~# true cat /etc/usb_modeswitch.d/12d1\:14fe TargetProduct=0x14fe #MessageContent="55534243123456780000000000000011063000000000010000000000000000" # Broadband modem manner 12d1:1442 MessageContent="55534243000000000000000000000011060000000000000000000000000000" HuaweiNewMode=1

This and then gives y'all:

root@NanoPi-NEO:~# lsusb Passenger vehicle 005 Device 002: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard

The outcome of this change was that the system then recorded this as a new modem and device. This meant the ttyUSBx was different and requires you to update /etc/NetworkManager/organisation-connects/i*UUID* of your connection accordingly.

root@NanoPi-NEO:~# ifconfig eth0      Link encap:Ethernet  HWaddr 02:81:35:58:b9:ab             inet addr:192.168.ten.6  Bcast:192.168.10.255  Mask:255.255.255.0           inet6 addr: fe80::bc73:ccfa:e22e:c61e/64 Scope:Link           Upwardly BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:899 errors:0 dropped:0 overruns:0 frame:0           TX packets:623 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:1000           RX bytes:111406 (111.4 KB)  TX bytes:68632 (68.six KB)           Interrupt:40  lo        Link encap:Local Loopback             inet addr:127.0.0.1  Mask:255.0.0.0           inet6 addr: ::1/128 Scope:Host           UP LOOPBACK RUNNING  MTU:65536  Metric:1           RX packets:336 errors:0 dropped:0 overruns:0 frame:0           TX packets:336 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:yard           RX bytes:29700 (29.7 KB)  TX bytes:29700 (29.7 KB)  ppp0      Link encap:Point-to-Bespeak Protocol             inet addr:ten.18.182.108  P-t-P:0.0.0.0  Mask:255.255.255.255           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1           RX packets:446 errors:0 dropped:0 overruns:0 frame:0           TX packets:448 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:iii           RX bytes:60982 (60.9 KB)  TX bytes:32303 (32.three KB)  wwx001e101f0000 Link encap:Ethernet  HWaddr 00:1e:10:1f:00:00             inet6 addr: fe80::21e:10ff:fe1f:0/64 Telescopic:Link           Upwardly BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:0 errors:0 dropped:0 overruns:0 frame:0           TX packets:49 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:1000           RX bytes:0 (0.0 B)  TX bytes:13318 (xiii.3 KB)

My second mail service above wasn't not a consummate resolution. Whilst this would create a ppp0 interface, this might non exist enough for some people. If you demand an actual wwan interface, yous need to brand some changes to /etc/usb_modeswitch.d/12d1\:14fe
TargetVendor=0x12d1 TargetProduct=0x1442 MessageContent="55534243000000000000000000000011060000000000000000000000000000"
I should as well point out that when you disconnect the modem, shutdown or on occasions reboot, the modem will announced as a Mass Storage Device again. To address this, adding a udev rule resolve that issue: /lib/udev/rules.d/twoscore-usb_modeswitch.rules
Activeness=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", ATTR{idProduct}=="14fe", RUN+="/usr/sbin/usb_modeswitch -v 12d1 -p 14fe -M '55534243000000000000000000000011060000000000000000000000000000'"
This doesn't call the same file, but rather runs the message command required to brand the magic happen. Having both this, and the manual option may exist handy however. From here, you should be able to bridge the connection to the Ethernet adapter. I also found that during my testing, it was handy to have an autossh connection to a system on the Internet. This would let me to connect over the 4G connection should I do something wrong and break the LAN connection somehow.