Router does not connect to LTE/Mobile network after standby

Hello everyone,
since the - apparently - last update, I’ve been having the problem that when my router no longer has a signal, it no longer reconnects to the internet by itself.

For example, if I put it on standby and then reactivate it, or when I come back from places (like the basement), it doesn't reconnect to the network.

Only after a full reboot does it quickly go back online.

This is what the router's start page looks like before I restart it.

thanks for help

Hello,

you’re dealing with a frustrating connectivity issue! It could be related to the router's firmware or a specific setting. Here are a few things you could try:

Check for Firmware Updates: Make sure your router's firmware is up to date. Sometimes updates can resolve bugs or connectivity issues.

Adjust Power Settings: Look into the router's power management settings. Some routers have options that control how they handle power-saving modes, which could affect reconnection.

Network Settings: Check the DHCP settings. Ensure that it's enabled, as this helps devices reconnect automatically.

Reset the Router: If you haven’t done this yet, a factory reset might help. Just remember to back up your settings if you have any custom configurations.

Consider a Different Channel: If you're in a crowded area, switching to a less congested Wi-Fi channel might improve stability.

Hello,

Firmware:
My firmware is up to date. I also reset the router once and restored the backup. It doesn't help.

Power saving:
It can't be related to power saving. I'm online with the router, then I go somewhere without reception, go offline, and come back into range four minutes later, and it doesn't reconnect. It wasn't in standby mode.

DHCP:
DHCP is active, I can access the router's web interface, otherwise, I wouldn't have been able to take the screenshot.

Reset:
Yes, I did it earlier, before posting here.

WIFI:
What good is a different Wi-Fi channel if LTE isn't connecting??

Thanks.

Hello,

I need help!!

I need to restart my router in bus, train or car very often.

Now i am at the same place. Offline since 60min.
Aber reboot without moving: online.

Thank you




Hello,

Today I am staying in a holiday home. The MUDI is powered via USB and has full reception. The internet was working perfectly. Then, at some point, everything just stopped. It said it was not connected again ("Not registered"). Traffic on all clients dropped to nearly 0.

After a reboot, I was able to browse the internet again with all devices.

Is no one else experiencing this problem?

These routers have issues with USB port and my guess its a design flaw. You could wait for Openwrt 24 and see if that fixes your issues, but im willing to bet $1 that it won't.

What does this have to do with the USB port? I'm having the problem both with USB and battery operation. Over USB, it's only receiving power.

When the signal drops, I can do a soft reset of the modem at the same location, and the internet works again.

But of course, that’s not a real solution. When you’re on the go, having to press the button every 20 minutes is far from ideal.

I would really appreciate it if support could respond here.

@bruce Might you have a look?

2 Likes

Restoring a backup after a reset mostly negates the reset. Any setting that could have been causing problems gets reloaded when you restore the backup. So, when resetting a router as part of a trouble shooting process DO NOT restore any settings.

1 Like

Hello, but I’d rather find the error than simply reconfigure the entire router, only to possibly face the same issue afterward.

If I were a user with no configuration who just wanted internet access, that would make sense, and I’d likely have a TP-Link router rather than a GLI router that offers features you don’t just want to reset away.

Hi there, +1!

I own a Slate Plus I am very satisfied with, and recently purchased a Mudi V2 which I am also satisfied with.

However, I agree with @Dustin282 Mudi V2 seems to be very slow to reconnect to 4G/LTE, which is very frustrating. By crossing borders it also disconnects for a while despite roaming activated, whereas other devices seamlessly reconnect abroad.

A firmware update to resolve these issues would be much appreciated!

Thank you

1 Like

But now that you mention Mudi V2!

I traveled with my Mudi V1 from Germany to Belgium, the Netherlands, back to Belgium, and back again without needing a reboot. It worked perfectly. Unfortunately, I physically damaged the Mudi V1 (it fell off the balcony). So, I got the V2, and since then, I've been having these problems!

Today, I reset the SIM settings completely and set up a new profile. Drove through an underground garage and lost connection. After a soft reset of the modem, the signal was excellent again.

Hi,

May I confirm that if the modem connection drop (like through the underground, signal too bad to lose the link), and then back to ground, the modem cannot re-connect, is it right?

Could you please provide the syslog when it occurs this situation? Maybe if the modem factory guys are needed to further check, will be required capturing the qlog to let them analysis, so it is possible bother, could you mind with help us to check?

Hello @bruce,

thanks for the response.

Yes, that’s correct. As soon as you’ve been underground, crossed a border, or traveled long distances and the connection drops, it doesn’t reconnect. A soft reset of the modem in the GLI interface helps re-establish the connection.

I’ll try to capture this, but pinpointing the exact time in the log is a bit of a hassle.

X3000 here having this same issue since 2 upgrades ago. Hoped the last would fix it but no luck. Anytime I change modem settings band etc and hit apply it just sits there forever and wont reconnect until I reboot the device.

1 Like

Hello @bruce,
can't you reproduce it if so many people have it? I've only been at home or at work for the last few days. There are no connection drops on the 5km :-(.

I would have to drive 40km to the nearest underground car park to do a proper test.

Hello, I drove on the motorway today and after about 60km my iPhone reported that the WiFi no longer had internet and now wanted to use mobile data.

In the log it was 08:15:31.

I then saved it and did a soft modem reset - in a parking lot.

The router had full mobile reception, but only an X where LTE should be.

Here is the log with modem reset

Wed Nov 13 08:15:18 2024 daemon.notice netifd: kkorg2 (13404): Try again: `myadress.dyndns.org:13231'. Trying again in 1.00 seconds...
Wed Nov 13 08:15:24 2024 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) cc:88:26:5c:ca:7b
Wed Nov 13 08:15:24 2024 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 172.33.20.61 cc:88:26:5c:ca:7b
Wed Nov 13 08:15:24 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.33.20.61 cc:88:26:5c:ca:7b
Wed Nov 13 08:15:24 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.33.20.61 cc:88:26:5c:ca:7b Tesla_Model_S
Wed Nov 13 08:15:24 2024 daemon.notice netifd: kkorg2 (13404): Try again: `myadress.dyndns.org:13231'. Trying again in 1.20 seconds...
Wed Nov 13 08:15:24 2024 daemon.info dnsmasq-dhcp[1]: DHCPRELEASE(br-lan) 172.33.20.61 cc:88:26:5c:ca:7b
Wed Nov 13 08:15:24 2024 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED cc:88:26:5c:ca:7b
Wed Nov 13 08:15:24 2024 daemon.info hostapd: wlan1: STA cc:88:26:5c:ca:7b IEEE 802.11: disassociated
Wed Nov 13 08:15:25 2024 daemon.info hostapd: wlan1: STA cc:88:26:5c:ca:7b IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Nov 13 08:15:30 2024 daemon.notice netifd: kkorg2 (13404): Try again: `myadress.dyndns.org:13231'. Trying again in 1.44 seconds...
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:12:46:419] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:13:01:458] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:13:16:499] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:13:31:539] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:13:46:579] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:14:01:619] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:14:16:659] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:14:31:699] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:14:46:738] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:15:01:779] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:31 2024 daemon.notice netifd: modem_1_1_2 (6438): [11-13_08:15:16:818] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW
Wed Nov 13 08:15:37 2024 daemon.notice netifd: kkorg2 (13404): Try again: `myadress.dyndns.org:13231'. Trying again in 1.73 seconds...
Wed Nov 13 08:15:40 2024 daemon.info hostapd: wlan1: STA cc:88:26:5c:ca:7b IEEE 802.11: authenticated
Wed Nov 13 08:15:40 2024 daemon.info hostapd: wlan1: STA cc:88:26:5c:ca:7b IEEE 802.11: associated (aid 5)
Wed Nov 13 08:15:40 2024 daemon.notice hostapd: wlan1: AP-STA-CONNECTED cc:88:26:5c:ca:7b
Wed Nov 13 08:15:40 2024 daemon.info hostapd: wlan1: STA cc:88:26:5c:ca:7b RADIUS: starting accounting session 2FD8ED1034FDBD27
Wed Nov 13 08:15:40 2024 daemon.info hostapd: wlan1: STA cc:88:26:5c:ca:7b WPA: pairwise key handshake completed (RSN)
Wed Nov 13 08:15:40 2024 daemon.notice hostapd: wlan1: EAPOL-4WAY-HS-COMPLETED cc:88:26:5c:ca:7b
Wed Nov 13 08:15:40 2024 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 172.33.20.61 cc:88:26:5c:ca:7b
Wed Nov 13 08:15:40 2024 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 172.33.20.61 cc:88:26:5c:ca:7b Tesla_Model_S
Wed Nov 13 08:15:41 2024 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED cc:88:26:5c:ca:7b
Wed Nov 13 08:15:41 2024 daemon.info dnsmasq-dhcp[1]: DHCPRELEASE(br-lan) 172.33.20.61 cc:88:26:5c:ca:7b

Update:

Because this requirement is about the modem remaining connected to the base station, or the modem continuing to try to redial after being disconnected, GL needs to communicate with Quectel and evaluate whether it can be achieved if it is done through the router firmware codes alone.

Okay, so that means you're contacting the manufacturer, Quectel, to clarify if they can fix the issue?