Netgear R6220 + Huawei E392 4G LTE usb setup issues

jjabba · June 16, 2025, 1:47pm

Im trying to build a 4G mobile/travel hotspot using this router:

Netgear R6220

and usb-stick 4G modem from Huawei:

Huawei LTE multimode USB stick model E392u-12

The router is running OpenWrt 24.10.1 and I've been following How to use LTE modem in QMI mode for WAN connection:

The modem shows up in dmesg, but no new devices show up when I try to add an a new interface.

I'm currently stuck trying to figure out if QMI is indeed the right mode?

P.s.
The dongle works without issues on my raspberry pi where it's listed as using 'qmi_wwan', if that helps.

AndrewZ · June 16, 2025, 1:50pm

Please show the output of cat /sys/kernel/debug/usb/devices
Use </> to format the output.

jjabba · June 16, 2025, 2:43pm

root@OpenWrt:~# cat /sys/kernel/debug/usb/devices 

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 6.06
S:  Manufacturer=Linux 6.6.86 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1506 Rev= 0.00
S:  Manufacturer=Huawei Technologies
S:  Product=HUAWEI Mobile
C:* #Ifs= 7 Cfg#= 1 Atr=c0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=option
E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=02 Driver=option
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=03 Driver=option
E:  Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=03(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 3 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=01 Prot=09 Driver=(none)
E:  Ad=85(I) Atr=03(Int.) MxPS=  64 Ivl=2ms
I:* If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=08 Driver=(none)
E:  Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
I:* If#= 5 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=87(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
I:* If#= 6 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=88(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 6.06
S:  Manufacturer=Linux 6.6.86 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

AndrewZ · June 16, 2025, 2:46pm

Do you have kmod-usb-net-qmi-wwan installed as shown in the wiki?

Please also query the modem with the following AT commands:

at^setport?
at^setport=?

jjabba · June 16, 2025, 8:51pm

I decided to re-flash the router back to a pristine state OpenWrt. All the packages I had installed made it murky, and no, i had not installed the 'kmod-usb-net-qmi-wwan', but now I'm going to follow the qmi wiki and ONLY the qmi wiki to the tee.

I'll report back soon.

jjabba · June 16, 2025, 9:07pm

So after starting fresh I have now installed the following packages:

root@OpenWrt:~# opkg install kmod-usb-net-qmi-wwan uqmi luci-proto-qmi kmod-usb-serial-option picocom

After reboot and a modem unplug/replug this is what I find in cat /sys/kernal/debug/usb/devices:

root@OpenWrt:~# cat /sys/kernel/debug/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 6.06
S:  Manufacturer=Linux 6.6.86 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3 Spd=480  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=12d1 ProdID=1505 Rev= 0.00
S:  Manufacturer=Huawei Technologies
S:  Product=HUAWEI Mobile
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 6.06
S:  Manufacturer=Linux 6.6.86 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

the wiki suggests to try ls -l /dev/cdc*

ls -l /dev/cdc*
ls: /dev/cdc*: No such file or directory

Perhaps I do need to install usb-modeswitch to get the modem into the right 'usb-mode'?

AndrewZ · June 16, 2025, 9:14pm

Yes, or ... connect it to your RPi where the dongle works without issues and change the mode there. You should be able to run the AT commands I mentioned from a terminal app in RPi.
Keep the dongle in RPi for now.

jjabba · June 16, 2025, 9:17pm

I had made the assumtion that the dongles usb-mode was
ephemeral, but it's not?

I will try!

jjabba · June 16, 2025, 10:19pm

Plugged the modem into my Raspberry Pi. I then used minicom to send commands you asked me to and this is what I got back.

sudo minicom -D /dev/ttyUSB0

at^setport?                                                                     
                                                                                
A1;1,2,3,7,A1,A2

and

at^setport=?                                                                    
                                                                                
1:MODEM                                                                         
2:PCUI                                                                          
3:DIAG                                                                          
4:PCSC                                                                          
5:GPS                                                                           
6:GPS CONTROL                                                                   
7:NDIS                                                                          
A:BLUE TOOTH                                                                    
B:FINGER PRINT                                                                  
D:MMS                                                                           
E:PC VOICE                                                                      
A1:CDROM                                                                        
A2:SD                                                                           
                                                                                
                                                                                
OK

AndrewZ · June 16, 2025, 10:20pm

Then send it AT^SETPORT="FF;2,7" and put it back to the router.

jjabba · June 16, 2025, 10:39pm

Great! That worked and it's now showing up as a device, so I went ahead and added an interface as outlined in the guide.

root@OpenWrt:~# ls -l /dev/cdc*
crw-------    1 root     root      180, 176 Jun 16 22:14 /dev/cdc-wdm0

However, there is an issue with the connection, i'm getting the same error on repeat in the OpenWrt system log on the router:

Mon Jun 16 22:24:32 2025 daemon.notice netifd: 4G_LTE_WAN (21817): Stopping network 4G_LTE_WAN
Mon Jun 16 22:24:32 2025 daemon.notice netifd: 4G_LTE_WAN (21817): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "4G_LTE_WAN" } (Permission denied)
Mon Jun 16 22:24:32 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is now down
Mon Jun 16 22:24:32 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is setting up now
Mon Jun 16 22:24:32 2025 daemon.notice netifd: 4G_LTE_WAN (21825): Waiting for SIM initialization
Mon Jun 16 22:24:32 2025 daemon.notice netifd: 4G_LTE_WAN (21825): PIN verification is disabled
Mon Jun 16 22:24:32 2025 daemon.notice netifd: 4G_LTE_WAN (21825): Waiting for network registration
Mon Jun 16 22:24:33 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:24:37 2025 daemon.notice netifd: 4G_LTE_WAN (21825): Starting network 4G_LTE_WAN
Mon Jun 16 22:24:37 2025 daemon.notice netifd: 4G_LTE_WAN (21825): Unable to connect IPv4
Mon Jun 16 22:24:37 2025 daemon.notice netifd: 4G_LTE_WAN (21962): Stopping network 4G_LTE_WAN
Mon Jun 16 22:24:37 2025 daemon.notice netifd: 4G_LTE_WAN (21962): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "4G_LTE_WAN" } (Permission denied)
Mon Jun 16 22:24:37 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is now down
Mon Jun 16 22:24:37 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is setting up now
Mon Jun 16 22:24:37 2025 daemon.notice netifd: 4G_LTE_WAN (21970): Waiting for SIM initialization
Mon Jun 16 22:24:37 2025 daemon.notice netifd: 4G_LTE_WAN (21970): PIN verification is disabled
Mon Jun 16 22:24:38 2025 daemon.notice netifd: 4G_LTE_WAN (21970): Waiting for network registration
Mon Jun 16 22:24:38 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:24:43 2025 daemon.notice netifd: 4G_LTE_WAN (21970): Starting network 4G_LTE_WAN
Mon Jun 16 22:24:43 2025 daemon.notice netifd: 4G_LTE_WAN (21970): Unable to connect IPv4
Mon Jun 16 22:24:43 2025 daemon.notice netifd: 4G_LTE_WAN (22112): Stopping network 4G_LTE_WAN
Mon Jun 16 22:24:43 2025 daemon.notice netifd: 4G_LTE_WAN (22112): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "4G_LTE_WAN" } (Permission denied)
Mon Jun 16 22:24:43 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is now down
Mon Jun 16 22:24:43 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is setting up now
Mon Jun 16 22:24:43 2025 daemon.notice netifd: 4G_LTE_WAN (22120): Waiting for SIM initialization
Mon Jun 16 22:24:43 2025 daemon.notice netifd: 4G_LTE_WAN (22120): PIN verification is disabled
Mon Jun 16 22:24:44 2025 daemon.notice netifd: 4G_LTE_WAN (22120): Waiting for network registration
Mon Jun 16 22:24:44 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:24:49 2025 daemon.notice netifd: 4G_LTE_WAN (22120): Starting network 4G_LTE_WAN
Mon Jun 16 22:24:49 2025 daemon.notice netifd: 4G_LTE_WAN (22120): Unable to connect IPv4
Mon Jun 16 22:24:49 2025 daemon.notice netifd: 4G_LTE_WAN (22257): Stopping network 4G_LTE_WAN
Mon Jun 16 22:24:49 2025 daemon.notice netifd: 4G_LTE_WAN (22257): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "4G_LTE_WAN" } (Permission denied)
Mon Jun 16 22:24:49 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is now down
Mon Jun 16 22:24:49 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is setting up now
Mon Jun 16 22:24:49 2025 daemon.notice netifd: 4G_LTE_WAN (22265): Waiting for SIM initialization
Mon Jun 16 22:24:49 2025 daemon.notice netifd: 4G_LTE_WAN (22265): PIN verification is disabled
Mon Jun 16 22:24:49 2025 daemon.notice netifd: 4G_LTE_WAN (22265): Waiting for network registration
Mon Jun 16 22:24:50 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:24:54 2025 daemon.notice netifd: 4G_LTE_WAN (22265): Starting network 4G_LTE_WAN
Mon Jun 16 22:24:54 2025 daemon.notice netifd: 4G_LTE_WAN (22265): Unable to connect IPv4
Mon Jun 16 22:24:55 2025 daemon.notice netifd: 4G_LTE_WAN (22402): Stopping network 4G_LTE_WAN
Mon Jun 16 22:24:55 2025 daemon.notice netifd: 4G_LTE_WAN (22402): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "4G_LTE_WAN" } (Permission denied)
Mon Jun 16 22:24:55 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is now down
Mon Jun 16 22:24:55 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is setting up now
Mon Jun 16 22:24:55 2025 daemon.notice netifd: 4G_LTE_WAN (22410): Waiting for SIM initialization
Mon Jun 16 22:24:55 2025 daemon.notice netifd: 4G_LTE_WAN (22410): PIN verification is disabled
Mon Jun 16 22:24:55 2025 daemon.notice netifd: 4G_LTE_WAN (22410): Waiting for network registration
Mon Jun 16 22:24:56 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:25:00 2025 daemon.notice netifd: 4G_LTE_WAN (22410): Starting network 4G_LTE_WAN
Mon Jun 16 22:25:00 2025 daemon.notice netifd: 4G_LTE_WAN (22410): Unable to connect IPv4
Mon Jun 16 22:25:00 2025 daemon.notice netifd: 4G_LTE_WAN (22547): Stopping network 4G_LTE_WAN
Mon Jun 16 22:25:00 2025 daemon.notice netifd: 4G_LTE_WAN (22547): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "4G_LTE_WAN" } (Permission denied)
Mon Jun 16 22:25:00 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is now down
Mon Jun 16 22:25:00 2025 daemon.notice netifd: Interface '4G_LTE_WAN' is setting up now
Mon Jun 16 22:25:00 2025 daemon.notice netifd: 4G_LTE_WAN (22555): Waiting for SIM initialization
Mon Jun 16 22:25:01 2025 daemon.notice netifd: 4G_LTE_WAN (22555): PIN verification is disabled
Mon Jun 16 22:25:01 2025 daemon.notice netifd: 4G_LTE_WAN (22555): Waiting for network registration
Mon Jun 16 22:25:01 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!

AndrewZ · June 17, 2025, 6:41am

Did you check/configure the APN on the modem as shown in the wiki?

jjabba · June 18, 2025, 9:17am

I will try that next and report back. In the meantime, if my RPi uses the modem successfully, wouldn't that indicate that the modem APN setting is at least working as is?

AndrewZ · June 18, 2025, 9:35am

We don't have visibility of the connection procedure used by RPi, so it's hard to compare.
Please also show the relevant fragment of your /etc/config/network so we could see how the modem interface is setup there.

jjabba · June 18, 2025, 10:29am

Is this referring to the RPi or the OpenWrt router?
(My RPi didn't have a /etc/config/network)

AndrewZ · June 18, 2025, 10:37am

From the router, certainly.

jjabba · June 18, 2025, 10:50am

SUCCESS!

Thank you AndrewZ

I used minicom on the RPi to look at the modems APN settings and they were indeed wrong.

AT+CGDCONT?             
                       
+CGDCONT: 1,"IP","data.tre.se","0.0.0.0",0,0

^ Incorrect

And after setting it and validating the new setting:

AT+CGDCONT=1,"IP","internet.tele2.se"                                           
                                                                                
OK                                                                              
AT+CGDCONT?                                                                     
                                                                                
+CGDCONT: 1,"IP","internet.tele2.se","0.0.0.0",0,0                              
                                                                                
OK

It now works upon plugging it into the router!

Wed Jun 18 09:57:37 2025 daemon.notice netifd: 4G_LTE_WAN_4 (11287): udhcpc: lease of 100.*.*.* obtained from 100.*.*.*, lease time 7200
Wed Jun 18 09:57:37 2025 daemon.notice netifd: Interface '4G_LTE_WAN_4' is now up
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using nameserver 130.244.127.161#53
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using nameserver 130.244.127.169#53
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Jun 18 09:57:37 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan

And for the sake of completeness, here is the output from my routers /etc/config/network

root@OpenWrt:~# cat /etc/config/network 

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd19:cdf0:10a9::/48'
	option packet_steering '1'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ipaddr '192.168.1.1'
	option netmask '255.255.255.0'
	option ip6assign '60'

config interface 'wan'
	option device 'wan'
	option proto 'dhcp'

config interface 'wan6'
	option device 'wan'
	option proto 'dhcpv6'

config interface '4G_LTE_WAN'
	option proto 'qmi'
	option device '/dev/cdc-wdm0'
	option apn 'internet.tele2.se'
	option auth 'none'
	option pdptype 'ipv4'

AndrewZ · June 18, 2025, 10:54am

Good.

Consider using a simpler interface name without uppercase symbols and underscores, something like lte or wwan.

jjabba · June 18, 2025, 11:39am

I spoke too soon @AndrewZ ...

After running fine for a while the lte link went down and it wouldn't reconnect.

I took this oppertunity to rename the interface to lte as suggested. Modem works when plugged into the RPi, and I was able to 'listen in' using minicom while the RPi was setting things up, here is what is prompted back on RPi-init:

Välkommen till minicom 2.8

FLAGGOR: I18n 
Port /dev/ttyUSB2, 13:30:08

Tryck CTRL-A Z för hjälp om specialtangenter


^SRVST:1

^MODE:5,4

^STIN:99,1,0

^SIMST:1

^HWNAT:06

^MODE:5,4

^SRVST:2
ATATE0
OK

OK

OK

+CRSM: 105,129,""

OK

+CPMS: "ME",0,50,"ME",0,50,"ME",0,50

OK

+CCLK: "25/06/18,11:31:06"+08"

OK

OK

OK

The system log on my router now shows this when I plug the modem back in:

Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1600.292619] usb 1-2: new high-speed USB device number 6 using xhci-mtk
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1600.496978] hub 1-2:1.0: USB hub found
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1600.506145] hub 1-2:1.0: 4 ports detected
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1600.832384] usb 1-2.1: new high-speed USB device number 7 using xhci-mtk
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1600.982585] option 1-2.1:1.0: GSM modem (1-port) converter detected
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1600.995711] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB0
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1601.015554] qmi_wwan 1-2.1:1.1: cdc-wdm0: USB WDM device
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1601.027816] qmi_wwan 1-2.1:1.1 wwan0: register 'qmi_wwan' at usb-1e1c0000.xhci-2.1, WWAN/QMI device, a2:61:bc:99:ef:0a
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1601.050101] option 1-2.1:1.2: GSM modem (1-port) converter detected
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1601.063353] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB1
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1601.078240] option 1-2.1:1.3: GSM modem (1-port) converter detected
Mon Jun 16 22:43:37 2025 kern.info kernel: [ 1601.091418] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB2
Mon Jun 16 22:43:38 2025 daemon.notice netifd: Interface 'lte' is setting up now
Mon Jun 16 22:43:38 2025 daemon.notice netifd: lte (8450): Waiting for SIM initialization
Mon Jun 16 22:43:40 2025 daemon.notice netifd: lte (8450): Request timed out
Mon Jun 16 22:43:40 2025 daemon.notice netifd: lte (8450): Failed to parse message data
Mon Jun 16 22:43:40 2025 daemon.notice netifd: lte (8450): SIM in illegal state - Power-cycling SIM
Mon Jun 16 22:43:43 2025 daemon.notice netifd: lte (8450): "Failed to connect to service"
Mon Jun 16 22:43:44 2025 daemon.notice netifd: lte (8450): Failed to parse message data
Mon Jun 16 22:43:44 2025 daemon.notice netifd: lte (8450): PIN status failed (not_initialized)
Mon Jun 16 22:43:45 2025 daemon.notice netifd: lte (8533): Stopping network lte
Mon Jun 16 22:43:45 2025 daemon.notice netifd: lte (8533): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "lte" } (Permission denied)
Mon Jun 16 22:43:45 2025 daemon.notice netifd: Interface 'lte' is now down
Mon Jun 16 22:43:46 2025 daemon.warn odhcpd[1676]: No default route present, overriding ra_lifetime to 0!

((Note: I was using a powered USB hub to eliminate power draw issues in the console output above))

jjabba · June 18, 2025, 7:42pm

Another update, after a shutdown of the router, a power plug pull and a long wait, I rebooted, and then and only then inserted the usb modem, and voila. The connection is working:

Mon Jun 16 22:27:50 2025 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.191 14:7d:da:90:21:b5
Mon Jun 16 22:27:50 2025 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.191 14:7d:da:90:21:b5
Mon Jun 16 22:27:50 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:27:54 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:27:55 2025 daemon.notice netifd: lte (3099): Starting network lte
Mon Jun 16 22:27:55 2025 daemon.notice netifd: lte (3099): Setting up wwan0
Mon Jun 16 22:27:55 2025 daemon.notice netifd: Interface 'lte' is now up
Mon Jun 16 22:27:55 2025 daemon.notice netifd: Network device 'wwan0' link is up
Mon Jun 16 22:27:56 2025 daemon.notice netifd: Network alias 'wwan0' link is up
Mon Jun 16 22:27:56 2025 daemon.notice netifd: Interface 'lte_4' is enabled
Mon Jun 16 22:27:56 2025 daemon.notice netifd: Interface 'lte_4' has link connectivity
Mon Jun 16 22:27:56 2025 daemon.notice netifd: Interface 'lte_4' is setting up now
Mon Jun 16 22:27:56 2025 daemon.notice netifd: lte_4 (3319): udhcpc: started, v1.36.1
Mon Jun 16 22:27:56 2025 user.notice firewall: Reloading firewall due to ifup of lte (wwan0)
Mon Jun 16 22:27:56 2025 daemon.notice netifd: lte_4 (3319): udhcpc: broadcasting discover
Mon Jun 16 22:27:56 2025 daemon.notice netifd: lte_4 (3319): udhcpc: broadcasting select for 10.42.53.98, server 10.42.53.97
Mon Jun 16 22:27:56 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:27:56 2025 daemon.notice netifd: lte_4 (3319): udhcpc: lease of 10.*.*.* obtained from 10.*.*.*, lease time 7200
Mon Jun 16 22:27:56 2025 daemon.notice netifd: Interface 'lte_4' is now up
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using nameserver 130.244.127.161#53
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using nameserver 130.244.127.169#53
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for test
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for local
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Mon Jun 16 22:27:56 2025 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Mon Jun 16 22:27:57 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!
Mon Jun 16 22:27:58 2025 user.notice firewall: Reloading firewall due to ifup of lte_4 (wwan0)
Mon Jun 16 22:27:59 2025 daemon.warn odhcpd[1678]: No default route present, overriding ra_lifetime to 0!

I'm not overly optimistic about the stability of the connection but I'll report back.