i have had my GL-X3000 for around 5 months now and it was working perfectly. since around november it hasnt been able to stay on for more than 10 mins or when i start to dowload something to just shuts off. i have bought 3 different sim cards, restarted and clean restarted numerous times and non seem to work. i also downloaded the new beta softwear but it still dosent work.
investigate the logs or share it here so other may help you.
logread.tar (139 KB)
I spotted a problem: your modem is getting invalid IP address (192.0.0.2) every few seconds.
Thu Jan 4 21:27:21 2024 kern.info kernel: [ 532.981124] IPv6: ADDRCONF(NETDEV_CHANGE): rmnet_mhi0: link becomes ready
Thu Jan 4 21:27:21 2024 daemon.notice netifd: Network device 'rmnet_mhi0' link is up
Thu Jan 4 21:27:21 2024 daemon.notice netifd: Network alias 'rmnet_mhi0' link is up
Thu Jan 4 21:27:21 2024 daemon.notice netifd: Interface 'modem_0001_4' has link connectivity
Thu Jan 4 21:27:21 2024 daemon.notice netifd: Interface 'modem_0001_4' is setting up now
Thu Jan 4 21:27:21 2024 user.info mwan3rtmon[5301]: Detect rtchange event.
Thu Jan 4 21:27:21 2024 daemon.notice netifd: modem_0001_4 (14340): udhcpc: started, v1.33.2
Thu Jan 4 21:27:21 2024 daemon.notice netifd: modem_0001_4 (14340): udhcpc: sending discover
Thu Jan 4 21:27:21 2024 daemon.notice netifd: modem_0001_4 (14340): udhcpc: sending select for 192.0.0.2
Thu Jan 4 21:27:21 2024 daemon.notice netifd: modem_0001_4 (14340): udhcpc: lease of 192.0.0.2 obtained, lease time 7200
Thu Jan 4 21:27:21 2024 daemon.notice netifd: Interface 'modem_0001_4' is now up
Thu Jan 4 21:27:22 2024 user.notice firewall: Reloading firewall due to ifup of modem_0001 (rmnet_mhi0)
Thu Jan 4 21:27:22 2024 user.notice mwan3[14682]: Execute ifup event on interface modem_0001_4 (rmnet_mhi0)
Thu Jan 4 21:27:22 2024 user.notice mwan3[14682]: Starting tracker on interface modem_0001_4 (rmnet_mhi0)
Can you reset the modem to default settings? Can you try to insert the SIM in the other slot and share the result?
By the way, are you connecting any other modems to the X3000 router?
i will try that now. and i am not connecting to any other modems
I guess I found the cause! Your modem is trying to ping google every few seconds to make sure the Internet is working. But because your ISP (virgin UK) is blocking the ping to Google, the modem disconnect and connect every few seconds in an endless loop!
Please disable the troublesome WAN tracking feature, which causing the 5-second loop:
2 Likes
here is the new log, dose anything look weird here?
logread (2).tar (140 KB)
Did you disable the tracking feature I mentioned above?
yes but it crashed again
Make sure it is disabled. And then reboot the modem and share the result?
logread (3).tar (139 KB)
First, reset the modem to default settings. Then disable the WAN Tracking feature. Then click “Auto Setup” to connect to the Internet.
MAKE SURE NO ANY COMPUTER IS CONNECTED TO THE MODEM EXCEPT ONE USING AN ETHERNET CABLE - NOT WIFI.
1 Like
Thank you @SpitzAX3000. I’m testing your suggestions as I’m encountering the same issue with my GL-X3000. Seems a few people are having similar issues around the same time range with these devices crashing/rebooting.
While reviewing the logs, crash report I did notice:
<7>[ 940.020526] ------------[ cut here ]------------ followed by <2>[ 940.020543] Kernel BUG at do_undefinstr+0x2e8/0x2f8 and <0>[ 940.029742] Internal error: Oops - BUG: 0 [#1] SMP
and ends with:
<0>[ 940.463626] Kernel panic - not syncing: Fatal exception
Not sure what instruction is causing it, but it seems to be from the do_undefinstr function.
Anywho, I’ve disabled the tracking feature and will see if this happens again in the next few hours.
There is a bug in the gl software , which is even if you disable the tracking from the Admin Panel the process is not being properly killed. The proper way to do it is logging into the modem using ssh. Then run:
ps - w | grep -i track*
Once you find the process id, kill it using:
kill -9 pid
Kill the process after establishing the connection.
Beautiful, thanks that’s perfect, Guess I’ll use the machete.
Love lingering processes.
Will give it a try and appreciate the quick response
Killed the process, after about 5 minutes the device crashed/rebooted again.
SSH’ed back into the box, the process was running again - killed it again.
However, it has now been running without a crash for 2.5 hours now, which atleast gives me a bit of hope. We shall see
It should not crash unless you killed another process 
by mistake!
Definitely did not kill another process 
. It was working fine all afternoon, woke up this morning to something strange:
- Device was on;
- power, internet, 4g, 5g, signal (where all green, static, not flashing).
- However, I had 0 internet and all my connected devices were offline
Couldn’t access the admin panel or even ping the device??
Rebooted → ssh’ed → killed the trace process again.
Really not sure what’s going on, any thoughts/suggestions?
Mine is running. For few days without a single problem.
In order to do it the right way, can you please tell All the services you use on the modem? For example, zerotier, adgurad, WiFi … etc?
Thanks and certainly:
- WiFi
- LAN Connected to a Netgear swtich
- Plugins: only default (nothing added)
- Features:
Dynamics DNS: No
GoodCloud: No
Adguard: No
Parental Control: No
ZeroTier: No
TailScale: no
No extra firewall rules;
Multi-Wan > Tracking disabled
Disabled DNS rebinding > manual DNS config (just cloudflare and google)
Mode: Router
IPv6 disabled
Mac Address: Factory Default
Drop-in Gateway: no
IGMP: no
network acceleration: no
Pretty much defaults in most areas