[SOLVED] Huawei E3372 won't register with mobile network when connected to AR750S

Installing and Using OpenWrt Network and Wireless Configuration
1

Good morning,

I have a GL-iNet AR750S running 3.022 of GL-iNet's software (OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.196.56128-9112198)). I'm having some trouble with my Huawei E3372 (non-Hilink version; firmware version is 21.xx.xx).

The modem registers fine with the moible network when plugged directly into my computer. It's recognised as a modem by the router, but is stuck in the 'registering' state and there is an error/timeout in the logs.

Could anybody advise how I might troubleshoot this? I'm a bit stuck. I've done a full reset of the router, but the result is the same.

lsusb shows this 
root@GL-AR750S:~# lsusb
Bus 002 Device 003: ID 05e3:0752 Genesys Logic, Inc.
Bus 001 Device 009: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0618 Genesys Logic, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dmesg | grep tty 
[    0.000000] Kernel command line:  board=GL-AR750S console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env),64k(art)ro,2048k(kernel),13052k(reserved);spi0.1:-(ubi) rootfstype=squashfs noinitrd
[    0.561224] console [ttyS0] disabled
[    0.585062] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 1562500) is a 16550A
[    0.594160] console [ttyS0] enabled
[   52.831574] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[   52.845233] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[30683.726924] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[30683.740368] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[30950.663425] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[30950.677618] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[31098.326956] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[31098.340488] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[31111.195146] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[31111.209376] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[31374.375214] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[31374.388684] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[31785.490136] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[31785.504298] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
logs 
Tue May 28 23:29:31 2019 kern.info kernel: [ 5109.024228] usb 1-1: new high-speed USB device number 2 using ehci-platform
Tue May 28 23:29:31 2019 kern.info kernel: [ 5109.281409] usb-storage 1-1:1.0: USB Mass Storage device detected
Tue May 28 23:29:31 2019 kern.info kernel: [ 5109.304388] scsi host1: usb-storage 1-1:1.0
Tue May 28 23:29:32 2019 kern.info kernel: [ 5109.741045] usb 1-1: USB disconnect, device number 2
Tue May 28 23:29:32 2019 kern.info kernel: [ 5110.534258] usb 1-1: new high-speed USB device number 3 using ehci-platform
Tue May 28 23:29:33 2019 kern.info kernel: [ 5110.839337] option 1-1:1.0: GSM modem (1-port) converter detected
Tue May 28 23:29:33 2019 kern.info kernel: [ 5110.845980] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
Tue May 28 23:29:33 2019 kern.info kernel: [ 5110.853521] option 1-1:1.1: GSM modem (1-port) converter detected
Tue May 28 23:29:33 2019 kern.info kernel: [ 5110.860108] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.001475] huawei_cdc_ncm 1-1:1.2: MAC-Address: 00:1e:10:1f:00:00
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.007948] huawei_cdc_ncm 1-1:1.2: setting rx_max = 16384
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.031361] huawei_cdc_ncm 1-1:1.2: NDP will be placed at end of frame for this device.
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.039882] huawei_cdc_ncm 1-1:1.2: cdc-wdm0: USB WDM device
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.046765] huawei_cdc_ncm 1-1:1.2 wwan0: register 'huawei_cdc_ncm' at usb-ehci-platform.0-1, Huawei CDC NCM device, 00:1e:10:1f:00:00
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.154477] usb-storage 1-1:1.3: USB Mass Storage device detected
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.175547] scsi host1: usb-storage 1-1:1.3
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.189224] usb-storage 1-1:1.4: USB Mass Storage device detected
Tue May 28 23:29:33 2019 kern.info kernel: [ 5111.264253] scsi host2: usb-storage 1-1:1.4
Tue May 28 23:29:34 2019 kern.notice kernel: [ 5112.190405] scsi 1:0:0:0: CD-ROM            HUAWEI   Mass Storage     2.31 PQ: 0 ANSI: 2
Tue May 28 23:29:34 2019 kern.notice kernel: [ 5112.371000] scsi 2:0:0:0: Direct-Access     HUAWEI   TF CARD Storage  2.31 PQ: 0 ANSI: 2
Tue May 28 23:29:34 2019 kern.notice kernel: [ 5112.385662] sd 2:0:0:0: [sdb] Attached SCSI removable disk
Tue May 28 23:29:38 2019 daemon.notice netifd: Interface 'modem_1_1' is setting up now
Tue May 28 23:29:40 2019 daemon.notice netifd: modem_1_1 (32155): cat: can't open '/tmp/modem.1-1/signal': No such file or directory
Tue May 28 23:29:41 2019 daemon.notice pppd[32214]: pppd 2.4.7 started by root, uid 0
Tue May 28 23:29:42 2019 local2.info chat[32299]: abort on (BUSY)
Tue May 28 23:29:42 2019 local2.info chat[32299]: abort on (NO CARRIER)
Tue May 28 23:29:42 2019 local2.info chat[32299]: abort on (ERROR)
Tue May 28 23:29:42 2019 local2.info chat[32299]: report (CONNECT)
Tue May 28 23:29:42 2019 local2.info chat[32299]: timeout set to 10 seconds
Tue May 28 23:29:42 2019 local2.info chat[32299]: send (AT+CGDCONT=1,"IP","three.co.uk"^M)
Tue May 28 23:29:43 2019 local2.info chat[32299]: timeout set to 30 seconds
Tue May 28 23:29:43 2019 local2.info chat[32299]: expect (OK)
Tue May 28 23:29:43 2019 local2.info chat[32299]: ^M
Tue May 28 23:29:43 2019 local2.info chat[32299]: OK
Tue May 28 23:29:43 2019 local2.info chat[32299]:  -- got it
Tue May 28 23:29:43 2019 local2.info chat[32299]: send (ATD*99***1#^M)
Tue May 28 23:29:43 2019 local2.info chat[32299]: expect (CONNECT)
Tue May 28 23:29:43 2019 local2.info chat[32299]: ^M
Tue May 28 23:29:43 2019 local2.info chat[32299]: ^M
Tue May 28 23:29:43 2019 local2.info chat[32299]: CONNECT
Tue May 28 23:29:43 2019 local2.info chat[32299]:  -- got it
Tue May 28 23:29:43 2019 local2.info chat[32299]: send ( ^M)
Tue May 28 23:29:43 2019 daemon.info pppd[32214]: Serial connection established.
Tue May 28 23:29:43 2019 kern.info kernel: [ 5121.079074] 3g-modem_1_1: renamed from ppp0
Tue May 28 23:29:43 2019 daemon.info pppd[32214]: Using interface 3g-modem_1_1
Tue May 28 23:29:43 2019 daemon.notice pppd[32214]: Connect: 3g-modem_1_1 <--> /dev/ttyUSB0
Tue May 28 23:30:14 2019 daemon.warn pppd[32214]: LCP: timeout sending Config-Requests
Tue May 28 23:30:14 2019 daemon.notice pppd[32214]: Connection terminated.
Tue May 28 23:30:15 2019 daemon.notice pppd[32214]: Modem hangup
Tue May 28 23:30:15 2019 daemon.info pppd[32214]: Exit.
Tue May 28 23:30:15 2019 daemon.notice netifd: Interface 'modem_1_1' is now down
Tue May 28 23:30:15 2019 daemon.notice netifd: Interface 'modem_1_1' is setting up now
Tue May 28 23:30:17 2019 daemon.notice netifd: modem_1_1 (580): cat: can't open '/tmp/modem.1-1/signal': No such file or directory
Tue May 28 23:30:17 2019 daemon.notice pppd[720]: pppd 2.4.7 started by root, uid 0
Tue May 28 23:30:18 2019 local2.info chat[744]: abort on (BUSY)
Tue May 28 23:30:18 2019 local2.info chat[744]: abort on (NO CARRIER)
Tue May 28 23:30:18 2019 local2.info chat[744]: abort on (ERROR)
Tue May 28 23:30:18 2019 local2.info chat[744]: report (CONNECT)
Tue May 28 23:30:18 2019 local2.info chat[744]: timeout set to 10 seconds
Tue May 28 23:30:18 2019 local2.info chat[744]: send (AT+CGDCONT=1,"IP","three.co.uk"^M)
Tue May 28 23:30:19 2019 local2.info chat[744]: timeout set to 30 seconds
Tue May 28 23:30:19 2019 local2.info chat[744]: expect (OK)
Tue May 28 23:30:49 2019 local2.info chat[744]: alarm
Tue May 28 23:30:49 2019 local2.info chat[744]: Failed
Tue May 28 23:30:49 2019 daemon.err pppd[720]: Connect script failed
/etc/config/network 
config interface 'modem_1_1'
	option ifname '3g-modem'
	option service 'umts'
	option apn 'three.co.uk'
	option proto '3g'
	option device '/dev/ttyUSB0'
	option metric '40'
	option disabled '0'

Many thanks.

2

Possibly not enough power from the USB Port to operate the E3372

Power input of GL-iNet AR750S is 10W and consumption is 6W, so only 4W spare for the E3371.
E3371 power consumption is 3.5W so should be just OK.

What are you powering GL-iNet AR750S with, is it at least 10W

Try and external powered HUB

1 Like
3

Thanks; will certainly give an external powered hub a whirl.

That said, I'm using a 5V 2500mA AC/DC adapter so at 12.5W I should be fine. Also, the modem powers-up fine: it just never completes registration with the mobile network; e.g:

Tue May 28 23:29:43 2019 local2.info chat[32299]: send (ATD*99***1#^M)
Tue May 28 23:29:43 2019 local2.info chat[32299]: expect (CONNECT)
Tue May 28 23:29:43 2019 local2.info chat[32299]: ^M
Tue May 28 23:29:43 2019 local2.info chat[32299]: ^M
Tue May 28 23:29:43 2019 local2.info chat[32299]: CONNECT
Tue May 28 23:29:43 2019 local2.info chat[32299]:  -- got it
Tue May 28 23:29:43 2019 local2.info chat[32299]: send ( ^M)
Tue May 28 23:29:43 2019 daemon.info pppd[32214]: Serial connection established.
Tue May 28 23:29:43 2019 kern.info kernel: [ 5121.079074] 3g-modem_1_1: renamed from ppp0
Tue May 28 23:29:43 2019 daemon.info pppd[32214]: Using interface 3g-modem_1_1
Tue May 28 23:29:43 2019 daemon.notice pppd[32214]: Connect: 3g-modem_1_1 <--> /dev/ttyUSB0
Tue May 28 23:30:14 2019 daemon.warn pppd[32214]: LCP: timeout sending Config-Requests
Tue May 28 23:30:14 2019 daemon.notice pppd[32214]: Connection terminated.
Tue May 28 23:30:15 2019 daemon.notice pppd[32214]: Modem hangup
Tue May 28 23:30:15 2019 daemon.info pppd[32214]: Exit.
4

This might help

https://openwrt.org/docs/guide-user/network/wan/wan_interface_protocols

https://openwrt.org/docs/guide-user/network/wan/wan_interface_protocols#protocol_wwan_usb_modems_autodetecting_above_protocols

delay number no 0 Seconds to wait before trying to interact with the modem (some ZTE modems require up to 30 s.)

1 Like
5

Thanks for the links. Made me realise that maybe option proto '3g' is incorrect, and I should be using 'wwan/' instead (along with setting a delay, as you suggest). I'll give it a whirl and let you know how I get on.

6

Randomly, it's started working. Here's what I did:

modified /etc/config/network with:

		option ifname '3g-modem'
		option mode 'auto'
		option apn 'three.co.uk'
		option proto 'ncm'
		option device '/dev/ttyUSB1'
		option metric '100'
		option ipv6 'auto'
		option delegate '0'
		option auto '0'

this did nothing: the logs were basically silent. Then, I switched back to:

config interface 'modem_1_1'
	option ifname '3g-modem'
	option service 'umts'
	option apn 'three.co.uk'
	option proto '3g'
	option device '/dev/ttyUSB1'
	option metric '40'
	option disabled '0'

and, magically, all started working again. Literally, I have no idea. Since I'm using option proto 3g, I don't hit 4G speeds, but I'll take that for now.

There are differences in the logs (see the first line of each, below):

Success 
Wed May 29 21:25:26 2019 local2.info chat[1043]: send ( ^M)
Wed May 29 21:25:26 2019 daemon.info pppd[913]: Serial connection established.
Wed May 29 21:25:26 2019 kern.info kernel: [34758.103964] 3g-modem_1_1: renamed from ppp0
Wed May 29 21:25:26 2019 daemon.info pppd[913]: Using interface 3g-modem_1_1
Wed May 29 21:25:26 2019 daemon.notice pppd[913]: Connect: 3g-modem_1_1 <--> /dev/ttyUSB1
Wed May 29 21:25:27 2019 daemon.warn odhcpd[2611]: DHCPV6 SOLICIT IA_NA from 0001000123c6a0a1f01dbcf3e8fd on br-lan: ok fd56:3f5a:232e:10::a55/128
Wed May 29 21:25:29 2019 daemon.warn pppd[913]: Could not determine remote IP address: defaulting to 10.64.64.64
Wed May 29 21:25:29 2019 daemon.notice pppd[913]: local  IP address 10.65.5.103
Wed May 29 21:25:29 2019 daemon.notice pppd[913]: remote IP address 10.64.64.64
Wed May 29 21:25:29 2019 daemon.notice pppd[913]: primary   DNS address 172.30.139.16
Wed May 29 21:25:29 2019 daemon.notice pppd[913]: secondary DNS address 172.31.139.16
Wed May 29 21:25:29 2019 daemon.notice netifd: Network device '3g-modem_1_1' link is up
Error 
Wed May 29 21:31:50 2019 local2.info chat[18415]: send (ATD*99***1#^M)
Wed May 29 21:31:50 2019 local2.info chat[18415]: expect (CONNECT)
Wed May 29 21:31:50 2019 local2.info chat[18415]: ^M
Wed May 29 21:31:50 2019 local2.info chat[18415]: ^M
Wed May 29 21:31:50 2019 local2.info chat[18415]: ERROR
Wed May 29 21:31:50 2019 local2.info chat[18415]:  -- failed
Wed May 29 21:31:50 2019 local2.info chat[18415]: Failed (ERROR)
Wed May 29 21:31:50 2019 daemon.err pppd[18292]: Connect script failed
Wed May 29 21:31:51 2019 daemon.info pppd[18292]: Exit.
Wed May 29 21:31:52 2019 daemon.notice netifd: Interface 'modem_1_1' is now down
Wed May 29 21:31:52 2019 daemon.notice netifd: Interface 'modem_1_1' is setting up now

If anyone has any insight here, or knowledge as to how I can control this, I'd love to know!

7

It seems this fixes it:

option dialnumber ''
1 Like
8

For posterity, I've also now got it working with NCM which gives me 4G connectivity:

config interface 'modem_1_1'
        option mode 'preferlte'
        option apn 'three.co.uk'
        option dialnum '*99#'
        option proto 'ncm'
        option ifname 'wwan0'
        option device '/dev/ttyUSB0'
        option ipv6 'auto'
        option metric '40'
        option delegate '0'
        option disabled '0'
1 Like
9

Hi,

since i have the same issue, where and how i can put the configuration that you posted?
I have also a GL-iNet AR750S with the same dongle.... and through WEBUI of 3.022 i wasn't able to get a connection.

Thank you

10

Welcome to the community, @superg1972

You'll need to ssh into the router, and edit /etc/config/network by hand. Step-by-step:

Check the following packages are installed (they seem to be there by default in the GL.iNet builds, but worth checking):

  • usbutils
  • usb-modeswitch
  • kmod-usb-net-huawei-cdc-ncm
  • kmod-usb-net-cdc-ether
  • comgt-ncm
  • kmod-usb-serial
  • kmod-usb-serial-option
  • kmod-usb-serial-wwan
  • luci-proto-ncm

Confirm that the modem is recognised and is driven by the Linux huawei_cdc_ncm driver (indicated by 12d1:1506 in the output below):

root@GL-AR750S:~# lsusb
Bus 001 Device 019: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard

Confirm there are two interfaces:

root@GL-AR750S:~# dmesg | grep tty
[ 1160.409071] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 1160.423206] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1

Check the current mode by sending AT commands (the GL-iNet firmware has a nice UI for sending AT commands manually. I had to send the commands to port /dev/ttyUSB0):

AT^SETPORT?
^SETPORT:“A1,A2;12,1,16,A1,A2
OK

16 is NCM mode, I believe; 1 is 3G

If you don't get the outputs similar to those above, it's possible your modem is the Hilink version (firmware v22.xxx.xx.xx.xx) rather than non-Hilink (firmware v21.xxx.xx.xx.xx). In which case, you'll need to do some Googling to switch it to the non-Hilink version. It may be possible to use the Hilink version 'as is', but I've never tried.

ssh into the router and edit /etc/config/network by hand. Add the following, using your mobile provider's APN and username/password if requried:

config interface 'modem_1_1'
        option mode 'preferlte'
        option apn 'three.co.uk'
        option dialnum '*99#'
        option proto 'ncm'
        option ifname 'wwan0'
        option device '/dev/ttyUSB0'
        option ipv6 'auto'
        option metric '40'
        option delegate '0'
        option disabled '0'

then

root@GL-AR750S:~# uci commit /etc/config/network
root@GL-AR750S:~# service network restart

In the logs, you'll see something like this. It's up-and-running if there are no errors and a DHCP lease is obtained

Fri May 31 07:47:54 2019 daemon.notice netifd: Interface 'modem_1_1_4' is disabled
Fri May 31 07:47:54 2019 daemon.notice netifd: modem_1_1 (5878): Stopping network modem_1_1
Fri May 31 07:47:55 2019 daemon.notice netifd: modem_1_1 (5878): sending -> AT^NDISDUP=1,0
Fri May 31 07:47:55 2019 daemon.warn odhcpd[1856]: DHCPV6 SOLICIT IA_NA from 00010001221705213c15c2c0fd64 on br-lan: ok fd56:3f5a:232e:10::2fb/128
Fri May 31 07:47:55 2019 daemon.notice netifd: modem_1_1 (5878): Command failed: Permission denied
Fri May 31 07:47:55 2019 daemon.notice netifd: Interface 'modem_1_1' is now down
Fri May 31 07:47:55 2019 daemon.notice netifd: Interface 'modem_1_1' is setting up now
Fri May 31 07:47:56 2019 daemon.warn odhcpd[1856]: DHCPV6 REQUEST IA_NA from 00010001221705213c15c2c0fd64 on br-lan: ok fd56:3f5a:232e:10::2fb/128
Fri May 31 07:47:59 2019 daemon.notice netifd: modem_1_1 (6032): sending -> AT
Fri May 31 07:47:59 2019 daemon.notice netifd: modem_1_1 (6032): sending -> ATZ
Fri May 31 07:48:00 2019 daemon.notice netifd: modem_1_1 (6032): sending -> ATQ0
Fri May 31 07:48:01 2019 daemon.notice netifd: modem_1_1 (6032): sending -> ATV1
Fri May 31 07:48:01 2019 daemon.notice netifd: modem_1_1 (6032): sending -> ATE1
Fri May 31 07:48:02 2019 daemon.notice netifd: modem_1_1 (6032): sending -> ATS0=0
Fri May 31 07:48:03 2019 daemon.notice netifd: modem_1_1 (6032): sending -> AT+CGDCONT=1,"IP","three.co.uk"
Fri May 31 07:48:03 2019 daemon.notice netifd: modem_1_1 (6032): Configuring modem
Fri May 31 07:48:03 2019 daemon.notice netifd: modem_1_1 (6032): Setting mode
Fri May 31 07:48:04 2019 daemon.notice netifd: modem_1_1 (6032): sending -> AT^SYSCFGEX="030201",3fffffff,2,4,7fffffffffffffff,,
Fri May 31 07:48:05 2019 daemon.notice netifd: modem_1_1 (6032): Starting network modem_1_1
Fri May 31 07:48:05 2019 daemon.notice netifd: modem_1_1 (6032): Connecting modem
Fri May 31 07:48:06 2019 daemon.notice netifd: modem_1_1 (6032): sending -> AT^NDISDUP=1,1,"three.co.uk"
Fri May 31 07:48:06 2019 daemon.notice netifd: modem_1_1 (6032): Setting up wwan0
Fri May 31 07:48:07 2019 daemon.notice netifd: Interface 'modem_1_1_4' is enabled
Fri May 31 07:48:07 2019 daemon.notice netifd: Interface 'modem_1_1' is now up
Fri May 31 07:48:07 2019 daemon.notice netifd: Network device 'wwan0' link is up
Fri May 31 07:48:07 2019 daemon.notice netifd: Network alias 'wwan0' link is up
Fri May 31 07:48:07 2019 daemon.notice netifd: Interface 'modem_1_1_4' has link connectivity
Fri May 31 07:48:07 2019 daemon.notice netifd: Interface 'modem_1_1_4' is setting up now
Fri May 31 07:48:07 2019 daemon.notice netifd: modem_1_1_4 (6862): udhcpc: started, v1.28.3
Fri May 31 07:48:08 2019 daemon.notice netifd: modem_1_1_4 (6862): udhcpc: sending discover
Fri May 31 07:48:08 2019 daemon.notice netifd: modem_1_1_4 (6862): udhcpc: sending select for 100.93.141.179
Fri May 31 07:48:08 2019 daemon.notice netifd: modem_1_1_4 (6862): udhcpc: lease of 100.93.141.179 obtained, lease time 518400
Fri May 31 07:48:09 2019 daemon.notice netifd: Interface 'modem_1_1_4' is now up
Fri May 31 07:48:19 2019 user.notice firewall: Reloading firewall due to ifup of modem_1_1 (wwan0)
11

Thank you very much for the detailed guidelines.

So far i didn't have still time to apply them, but yesterday i tried to send the command and i got exactly what you reported

Magically yesterday i got connected the device (steady blue led on the dongle) and i got an public IP from 4G connection.
The only problem is that even if it looked like connected i couldn't surf in internet (SIM and dongle are working fine connected to a computer).
If i use the GL-iNet AR750S connected to a WiFi connection all works fine.
I'm becoming crazy!!!
Thank you for any help

12

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.