GL-XE300: SIM card not registered

Technical Support for Routers
1

Hello

I have a GL-XE300 which was working perfectly until it was shutdown and moved to another location. Now the SIM will not register with any network, with two different multi-network roaming SIMs having been tried.

Checking the logs shows a continual loop of the following:

Wed Apr 16 07:06:18 2025 daemon.notice netifd: Interface 'modem_1_1_2' is setting up now
Wed Apr 16 07:06:19 2025 daemon.notice netifd: modem_1_1_2 (4444):
Wed Apr 16 07:06:19 2025 daemon.notice netifd: modem_1_1_2 (4444):
Wed Apr 16 07:06:19 2025 daemon.notice netifd: modem_1_1_2 (4444): ERROR
Wed Apr 16 07:06:19 2025 daemon.notice netifd: modem_1_1_2 (4444):
Wed Apr 16 07:06:19 2025 daemon.notice netifd: modem_1_1_2 (4444):
Wed Apr 16 07:06:19 2025 daemon.notice netifd: modem_1_1_2 (4444): OK
Wed Apr 16 07:06:20 2025 daemon.notice netifd: modem_1_1_2 (4444): Failed to parse message data
Wed Apr 16 07:06:21 2025 daemon.notice netifd: modem_1_1_2 (4444):
Wed Apr 16 07:06:21 2025 daemon.notice netifd: modem_1_1_2 (4444):
Wed Apr 16 07:06:21 2025 daemon.notice netifd: modem_1_1_2 (4444): ERROR
Wed Apr 16 07:06:21 2025 daemon.notice netifd: modem_1_1_2 (4444):
Wed Apr 16 07:06:21 2025 daemon.notice netifd: modem_1_1_2 (4444):
Wed Apr 16 07:06:21 2025 daemon.notice netifd: modem_1_1_2 (4444): OK
Wed Apr 16 07:06:22 2025 daemon.notice netifd: modem_1_1_2 (4444): Waiting for SIM initialization
Wed Apr 16 07:06:23 2025 daemon.notice netifd: modem_1_1_2 (4444): Failed to connect to service
Wed Apr 16 07:06:23 2025 daemon.notice netifd: modem_1_1_2 (4852): Stopping network modem_1_1_2
Wed Apr 16 07:06:23 2025 daemon.notice netifd: modem_1_1_2 (4852): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "modem_1_1_2" } (Permission denied)
Wed Apr 16 07:06:23 2025 daemon.notice netifd: Interface 'modem_1_1_2' is now down
Wed Apr 16 07:06:23 2025 daemon.notice netifd: Interface 'modem_1_1_2' is setting up now
Wed Apr 16 07:06:24 2025 daemon.notice netifd: modem_1_1_2 (4883):
Wed Apr 16 07:06:24 2025 daemon.notice netifd: modem_1_1_2 (4883):
Wed Apr 16 07:06:24 2025 daemon.notice netifd: modem_1_1_2 (4883): ERROR
Wed Apr 16 07:06:24 2025 daemon.notice netifd: modem_1_1_2 (4883):
Wed Apr 16 07:06:24 2025 daemon.notice netifd: modem_1_1_2 (4883):
Wed Apr 16 07:06:24 2025 daemon.notice netifd: modem_1_1_2 (4883): OK
Wed Apr 16 07:06:25 2025 daemon.notice netifd: modem_1_1_2 (4883): Failed to parse message data
Wed Apr 16 07:06:25 2025 daemon.notice netifd: modem_1_1_2 (4883):
Wed Apr 16 07:06:25 2025 daemon.notice netifd: modem_1_1_2 (4883):
Wed Apr 16 07:06:25 2025 daemon.notice netifd: modem_1_1_2 (4883): ERROR
Wed Apr 16 07:06:26 2025 daemon.notice netifd: modem_1_1_2 (4883):
Wed Apr 16 07:06:26 2025 daemon.notice netifd: modem_1_1_2 (4883):
Wed Apr 16 07:06:26 2025 daemon.notice netifd: modem_1_1_2 (4883): OK
Wed Apr 16 07:06:27 2025 daemon.notice netifd: modem_1_1_2 (4883): Waiting for SIM initialization
Wed Apr 16 07:06:27 2025 daemon.notice netifd: modem_1_1_2 (4883): Failed to connect to service
Wed Apr 16 07:06:28 2025 daemon.notice netifd: modem_1_1_2 (5261): Stopping network modem_1_1_2
Wed Apr 16 07:06:28 2025 daemon.notice netifd: modem_1_1_2 (5261): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "modem_1_1_2" } (Permission denied)
Wed Apr 16 07:06:28 2025 daemon.notice netifd: Interface 'modem_1_1_2' is now down

I hope somebody can enlighten me as to what to do next.

Thanks

2

I got it working by switching from QMI (which was working previously in the UK), to 3G mode, which is the only setting which works for the router in Greece. Does anybody know why this would be necessary?

3

@davegr From logread, it is known that when the qmi protocol is dialed, the qmi message sent to the module does not respond, resulting in "Failed to connect to service", and then the dialing fails, you can restart the device and try QMI dialing again to see if there is still a problem