GL-X3000 Spitz AX Cellular connection keeps loading and not connected

Hey,

I'm using the GL-X3000 in a motorhome so the 4G/5G masts change quite often. Sometimes the Cellular connection just disappears and when I connect to the admin dashboard I can see the following loading icon:

Rebooting the router fixes the issue but this has been happening on a daily basis during this week and it's getting pretty annoying.

Are there certain logs I could provide to the support? Could I add a cron job which would reload just the cellular connectivity when it fails to connect?

I'm running the latest 4.0 0701release3.

1 Like

Hi @onni, we need the system log and the modem log. And I‘ve contacted you via email, please check.

Support staff from GL.iNet told me in the emails that this was happening because I had poor signal and I would need to lock towers. This assumption doesn't seem to be true and today I had excellent signal strength but the connection was anyway lost for 5 minutes anyway:

This is probably happening because the IP-address from my 5G provider seems to change suddenly (IP-address is redacted as XXX.YYY.ZZZ.WWW below):

Sun Feb 16 11:11:15 2025 user.notice root: modem ip different, now regain ip ...
Sun Feb 16 11:11:15 2025 daemon.notice netifd: Interface 'modem_0001_4' has lost the connection
Sun Feb 16 11:11:15 2025 daemon.notice netifd: Interface 'modem_0001_4' is now down
Sun Feb 16 11:11:15 2025 daemon.notice netifd: Interface 'modem_0001_4' is disabled
Sun Feb 16 11:11:15 2025 daemon.notice netifd: Interface 'modem_0001_4' is enabled
Sun Feb 16 11:11:15 2025 daemon.notice netifd: Interface 'modem_0001_4' is setting up now
Sun Feb 16 11:11:15 2025 daemon.notice netifd: modem_0001_4 (20476): udhcpc: started, v1.33.2
Sun Feb 16 11:11:15 2025 user.notice firewall: Reloading firewall due to ifdown of modem_0001_4 ()
Sun Feb 16 11:11:15 2025 daemon.notice netifd: modem_0001_4 (20476): udhcpc: sending discover
Sun Feb 16 11:11:15 2025 daemon.notice netifd: modem_0001_4 (20476): udhcpc: sending select for XXX.YYY.ZZZ.WWW
Sun Feb 16 11:11:15 2025 daemon.notice netifd: modem_0001_4 (20476): udhcpc: lease of XXX.YYY.ZZZ.WWW obtained, lease time 7200
Sun Feb 16 11:11:15 2025 daemon.notice netifd: Interface 'modem_0001_4' is now up
Sun Feb 16 11:11:16 2025 kern.warn kernel: [482471.579182] 7981@C08L2,ap_peer_disassoc_action() 3645: ASSOC - 1 receive DIS-ASSOC request
Sun Feb 16 11:11:16 2025 kern.warn kernel: [482471.587709] 7981@C01L2,wifi_sys_disconn_act() 1002:  wdev_idx=2
Sun Feb 16 11:11:16 2025 kern.notice kernel: [482471.595618] 7981@C08L3,hw_ctrl_flow_v2_disconnt_act() 172: wdev_idx=2
Sun Feb 16 11:11:16 2025 kern.warn kernel: [482471.603177] 7981@C13L2,MacTableDeleteEntry() 1938: Del Sta:ee:86:22:6d:26:fd
Sun Feb 16 11:11:16 2025 user.notice firewall: Reloading firewall due to ifup of modem_0001_4 (rmnet_mhi0)

According to the logs this doesn't actually take that long time but for the connected clients it takes a few minutes to be back online. Would there a way to make this happen faster?

This is still happening with the latest firmware Version:4.0 & Firmware type: 0704release5.

[email protected] told me that this is happening because my connection is not stable.

I have been in the same spot now for 16 hours and I have needed to reboot the router 3 times. It works initially well for few hours but then the connection shuts down and keeps showing this loading icon in the dashboard:

I don't see any related errors from the logs.

When this bug appears I can't check the connection levels because the dashboard doesn't let me access it.

I can't believe it would be a unstable connection because it shows that I have 3/4 bars of connection strength and almost 0.5Gbps download speeds with 5G NSA.

Would someone be able to help me with this? I can't really trust the router anymore to do my work since it repeatedly shuts down and I thus can't really recommend these products anymore.

Even if the connection is unstable the software should not crash but should just retry and it definitely should allow user to see the cellular settings and connection strength statistics. Currently when this bug appears I can't access anything related to Cellular but everything else seems to work.


Support contacted me and mentioned that this might be fixed by updating the uboot boot loader and firmware and doing a hard reset. See more here: Critical Problem Notification for GL-MT2500/GL-X3000/GL-XE3000 - GL.iNet Router Docs 4

I bought USB-C -> Ethernet adapter and did this and I can still witness the same bug.

Support was nice and offered to replace my device but it's a bit hard to do since I'm currently traveling in southern Europe and the device is installed into my motorhome.

I ended up doing a nasty workaround of booting the router every time the bug appears by adding this into my crontab in the Luci admin https://192.168.8.1:8443/cgi-bin/luci/admin/system/crontab.

# Boot the router if the modem doesn't answer for 30s
* * * * * /usr/bin/timeout 30s /usr/bin/gl_modem -B 0001:01:00.0 AT AT || (echo "[$(date)] Modem 30s timeout reached. Rebooting..." >> /var/log/network-lost.log; /sbin/reboot)

I can't really use the router for online video chats but at least I can still use it for asynchronous work with this ugly hack. Hopefully this is useful for somebody else too :+1:.

I will try to schedule the replacement with the support once I know I'm in the same place for a longer amount of time.

1 Like

It seems to now be working at least a bit better. Earlier I needed to boot it every 2 hours but now it's running already for 8 hours.

What I did:

1.Downloaded the latest modem firmware RM520NGLAAR01A08M4G_01.206.01.206.
2. Renamed the file name from RM520NGLAAR01A08M4G_01.206.01.206.zip.zip to RM520NGLAAR01A08M4G_01.206.01.206.zip.
3. Opened System -> Upgrade -> Module local upgrade and drag’n’dropped the zip file there and ran the upgrade.
4. Removed 2nd SIM card (which was not even used).
5. Disabled Network Acceleration under Network tab.

Would someone know if there's a better way to reload the modem than just rebooting?

Eg if-down and if-up or something else?

Currently I'm checking if the modem stops responding with this command:

/usr/bin/timeout 30s /usr/bin/gl_modem -B 0001:01:00.0 AT AT

And then doing the reboot but this takes quite long time and I'm wondering if there's something else I could do to just reload the modem without booting :thinking:.

The modem now worked for 20 hours before failing.

The problem seems to be that the /dev/mhi_DUN stops answering and thus the loading icon in the dashboard.

I'm wondering if the your sim card may not support ipv6, please contact your carrier errors are actually related or not :thinking:.

# This prints nothing
$ timeout 5s echo -e "AT\r" > /dev/mhi_DUN
$ opkg install pciutils
$ lspci
0000:00:00.0 Unclassified device [0002]: MEDIATEK Corp. Device 7981
0001:00:00.0 PCI bridge: MEDIATEK Corp. Device 1f32 (rev 01)
0001:01:00.0 Unassigned class [ff00]: Qualcomm Device 0308 

$ ls -lah /dev/mhi*
crw-------    1 root     root      245,   0 Apr 14 02:17 /dev/mhi_BHI
crw-------    1 root     root      246,   1 Apr 14 02:17 /dev/mhi_DIAG
crw-------    1 root     root      246,   3 Apr 14 02:17 /dev/mhi_DUN
crw-------    1 root     root      246,   0 Apr 14 02:17 /dev/mhi_LOOPBACK
crw-------    1 root     root      246,   2 Apr 14 02:17 /dev/mhi_QMI0
$ logread | grep -i modem
Tue Apr 15 06:41:54 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:42:20 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:180
Tue Apr 15 06:42:28 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:42:34 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:42:36 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:43:06 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:30
Tue Apr 15 06:43:14 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:43:14 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:43:22 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:43:30 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:43:39 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:43:47 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:43:54 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:43:55 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:44:03 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:44:11 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:44:19 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:44:27 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:44:34 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:44:35 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:44:43 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:44:51 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:8
Tue Apr 15 06:45:14 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:45:21 2025 daemon.err modem_AT: (modem_AT.c:155) AT_Read@155 The number of times the epoll reached timeout:30
Tue Apr 15 06:45:54 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:38:59:963] QmiWwanSendQMI poll=0, revents = 0x0, errno: 4 (Interrupted system call)
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:40:59:964] requestSetupDataCall message timeout
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:40:59:964] requestSetupDataCall err = 110
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:40:59:964] try to requestSetupDataCall 60 second later
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:40:59:964] your sim card may not support ipv6, please contact your carrier
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:40:59:964] check whether the sim card has obtained an ipv6 address. AT command 'AT+CGPADDR'
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:42:04:988] QmiWwanSendQMI poll=0, revents = 0x0, errno: 4 (Interrupted system call)
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:44:04:989] requestSetupDataCall message timeout
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:44:04:989] requestSetupDataCall err = 110
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:44:04:989] trying to get ipv6 address
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:44:09:994] QmiWwanSendQMI poll=0, revents = 0x0, errno: 4 (Interrupted system call)
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:46:09:994] requestSetupDataCall message timeout
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:46:09:994] requestSetupDataCall err = 110
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:46:09:995] try to requestSetupDataCall 60 second later
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:46:09:995] your sim card may not support ipv6, please contact your carrier
Tue Apr 15 06:46:09 2025 daemon.notice netifd: modem_0001 (13302): [04-15_06:46:09:995] check whether the sim card has obtained an ipv6 address. AT command 'AT+CGPADDR'
Tue Apr 15 06:46:34 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:47:14 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout
Tue Apr 15 06:47:54 2025 daemon.err eco[11388]: call modem.get_sim_signal fail: timeout

I have this issue today, for the first time. Did you make any progress in diagnosing the cause? I am on EE in the UK.

For what it's worth, my GL-X3000 did not like RM520NGLAAR01A08M4G and seems happier on RM520NGLAAR03A04M4G.

Thanks. Mine has stopped connecting overnight, with no changes made on my end. I have tried a factory reset to no avail. I am starting to suspect a hardware issue, so have contacted support.

I’m still checking if I have the same problem or not
But the device I have is running all day
Then I’m receiving this message

The interface is connected, but the Internet can't be accessed

Then it tries to connect to the 5G network
But it is just not working
After 8-10 times I just rebooted
And all fine again
What I have noticed, then I got a new IP from the carrier

Any idea?

I’m on Version 4.0 0704release5

Any response on this from GLinet techs?

Cathy @ GL.inet sent me the following

Please download the new Uboot bootloader from https://fw.gl-inet.com/firmware/x3000/uboot/uboot-x3000-20250328-2c152d7aad44678ec7411b551ce5c7b0.bin

And then refer to the tutorial at Upgrade Uboot version - GL.iNet Router Docs 4 to update the Uboot and try it again.

This brought my unit back to life.

Worth a try.

1 Like