RUT950 keeps disconnecting, despite 4G presence

I have two RUT950’s and both have same intermittent problems.
Each day, they disconnect the internet connection, even though there is an available 4G network. I have been experiencing this issue for a long time (2 years) and one modem was replaced under warranty. The replacement has now done the same and is out of warranty. I have attached screenshots. Rebooting the modem normally works, but I do not know why they disconnect in the first place? This happens about 1-2 times per day. I always update the FW in the hope the latest will resolve the problem, but it has not definitively solved the issue to date.

This problem is not happening with my RUT240, RUT241 and RUT360. It’s only the RUT950’s which have shown to be the weakest devices so far.

Hello,

Do you notice any patterns as to when this occurs? Maybe it happens at specific times?

You mentioned that other devices are working fine. Are those devices in the same location, use the same SIM card, and have identical configurations?

Next time when this occurs, please, access the WebUI, navigate to System → Administration → Troubleshoot. There, press the button to ‘view’ system logs. Please, hide any sensitive information, like IP addresses, and paste the logs here.

Kind Regards,

Hi!
I have tested and can confirm two things so far: It is definitely not time related and I have bought a new sim card and placed it into the router. Same issue.

I have two other thoughts:

  1. it could happen when the cell tower changes between 3G and 4G. This signal change causes the router to disconnect. Perhaps the “Low Signal Reconnect” page may offer something.

    What do you think?
  2. I have noticed that “sim failover” may cause the router to get confused. During several sim card changes, it also failed to connect, despite showing 4G signal. I then proceeded to disable sim 2, clicked on “sim 1 default” and switched OFF “sim failover”.
    Let me see how this continues and I will let you know.

Andzej, regarding the logs: It is a bog log and I cannot find all mac addresses and IMEI and IP addresses. Is there a secure server or email where I can send them to?
Many thanks

Hello,

Unfortunately, there is no way to share information privately. Without logs, it is hard to say what can be the exact issue here.

Are those functional RUT240 devices placed in the same area? Could you check what bands those use when they are connected?

Could you please share the firmware and internal modems FW? You can find those in System → Firmware.

Also, could you try configuring Servieces → Auto reboot → Ping reboot and set action to be ‘restart mobile connection’ or ‘modem reboot’? Does the connection restore itself this way after some time?

Kind Regards,

The RUT360 is in the same area and uses a duplicate sim off the same contract. See mobile stats in the screenshot:

Firmware Versions:

RUT360:
Firmware version: 07.04.5
Internal modem firmware: EG06ELAR04A04M4G

RUT950 (1):
Firmware version: 07.04.5
Internal modem firmware: EC25ECGAR06A04M1G_01.004.01.004

RUT950 (2):
Firmware version: 07.04.5
Internal modem firmware: EC25ECGAR06A04M1G_01.004.01.004

Auto Reboot has been configured. Let’s wait and see! :grinning:

I see I cannot upload a .log file? Am I correct? Or am I doing something wrong?

Hello,

There are some limitations when it comes to file uploads. Would it be possible for you to paste just some of the logs that were generated around the time when the device disconnected?

Also, the internal modem’s firmware is quite old. One of the options would be to update the internal modem. Can you check if its available from System → Firmware? Select internal modem and update from server.

Also, let me know if the connection is automatically restored via auto reboot.

Kind Regards,

I will have to go through the log file and look for something of importance to paste.

There is no newer internal modem firmware available.

The auto reboot does not work at this stage… :laughing: :laughing:

Hello,

Whether it is worth it to update the modem depends on the situation. However, usually we recommend to update the modem when we know that the issue if related to the modem’s firmware, or as the last resort.

The fact that it takes some time to log in can be related to poor connectivity. However, could you please clarify if there are other connectivity issues on the device when it is connected via 4G? If so, I would like you to navigate to Network → Interfaces → edit mob1s1a1 → Advanced settings tab and try to set a custom MTU. Values to try are 1460, 1360, 1260.

Let me know if it improves anything.

Kind Regards,

Hi, I doubt it has anything to do with connectivity. I am sitting next to the modem and whether I connect via LAN cable or via wifi, it is slow to load the admin page after entering the login password. I am not trying to connect remotely via RMS.

I can confirm that there are no other connectivity issues when connected via 4G. The tower is on 4G about 99% of the time with the remaining 1% being on 3G. Apart from the daily disruptions which the tower gets (due to South Africa’s load shedding scheme) it is generally reliable.

I have disabled the ping-reboot option and the current setting for MTU is 1460. I will monitor this for a few days.

At this stage the two RUT950’s are working, so I do not want to risk one or both failing permanently in the internal modem firmware upgrade.

How do I post a response to this topic chain if it is about to end?

Hello,

I have changed the timer on this topic.

If all of your devices are configured in the same way, use the same SIM cards, and are in the same area, but the issue occurs only on RUT950, then I assume that the issue is not related to the configurations. Also, since this issue appears on multiple RUT950’s, it is unlikely that the issue is hardware related either. The main difference I see is in the firmware version of the internal modem.

However, as I mentioned before, it would be great to see system logs.

You can try swapping the PSU and antennas to ensure that those are not causing issues.

I would suggest experimenting a bit and if you decide that it is not acceptable, you can try updating the modem on one of the devices to see if it resolves the issue.

Kind Regards,

I keep a list going of every time the internet connection is disabled. Since we made changes on the ping-reboot and the MTU, the problem has not returned. Here are the network logs of the past several hours:

|
|2608|2023-09-07 23:25:16|Network Operator|Connected to MTNSA ItsAllAboutYou operator (internal modem)|
|2607|2023-09-07 23:25:16|Network Type|Joined LTE network (internal modem)|
|2606|2023-09-07 23:25:16|Mobile Data|Mobile data connected (internal modem)|
|2605|2023-09-07 23:25:07|Network Operator|Connected to MTNSA ItsAllAboutYou operator (internal modem)|
|2604|2023-09-07 23:25:07|Network Type|Joined LTE network (internal modem)|
|2603|2023-09-07 23:25:07|Mobile Data|Mobile data connected (internal modem)|
|2602|2023-09-07 23:24:13|Mobile Data|Mobile data disconnected (internal modem)|
|2601|2023-09-07 17:51:02|Network Operator|Connected to MTNSA ItsAllAboutYou operator (internal modem)|
|2600|2023-09-07 17:51:02|Network Type|Joined LTE network (internal modem)|
|2599|2023-09-07 17:51:02|Mobile Data|Mobile data connected (internal modem)|
|2598|2023-09-07 17:50:55|Network Operator|Connected to MTNSA ItsAllAboutYou operator (internal modem)|
|2597|2023-09-07 17:50:55|Network Type|Joined LTE network (internal modem)|
|2596|2023-09-07 17:50:54|Mobile Data|Mobile data connected (internal modem)|
|2595|2023-09-07 17:50:39|Mobile Data|Mobile data disconnected (internal modem)|
|2594|2023-09-07 17:28:37|Network Operator|Connected to MTNSA ItsAllAboutYou operator (internal modem)|
|2593|2023-09-07 17:28:37|Network Type|Joined LTE network (internal modem)|
|2592|2023-09-07 17:28:37|Mobile Data|Mobile data connected (internal modem)|
|2591|2023-09-07 17:28:28|Network Operator|Connected to MTNSA ItsAllAboutYou operator (internal modem)|
|2590|2023-09-07 17:28:28|Network Type|Joined LTE network (internal modem)|
|2589|2023-09-07 17:28:28|Mobile Data|Mobile data connected (internal modem)|
|2588|2023-09-07 17:28:13|Mobile Data|Mobile data disconnected (internal modem)|
|2587|2023-09-07 17:27:58|Network Operator|Connected to MTNSA ItsAllAboutYou operator (internal modem)|
|2586|2023-09-07 17:27:58|Network Type|Joined LTE network (internal modem)|

System Events:

ID Date Event Type Event
17 2023-08-28 19:25:58 Reboot Request from Web UI
16 2023-08-26 20:30:55 Reboot Request from Web UI
15 2023-08-26 12:58:17 Reboot Request from Web UI
14 2023-08-26 11:34:20 Reboot Request from Web UI
13 2023-08-24 08:20:42 Reboot Request from Web UI
12 2023-08-23 20:22:13 Reboot Request from Web UI
11 2023-08-22 19:33:54 Reboot Request from Web UI
10 2023-08-21 16:26:19 Reboot Request from Web UI
9 2023-08-19 20:23:06 Reboot Request from Web UI
8 2023-08-19 08:20:28 Reboot Request from Web UI
7 2023-08-16 07:24:40 Reboot Request from Web UI
6 2023-08-14 10:25:04 Reboot Request from Web UI
5 2023-08-05 09:06:30 sysupgrade Image signature not present
4 2023-08-05 09:06:28 Reboot Request after FW upgrade
3 2023-08-05 09:06:21 sysupgrade Image signature not present
2 2023-08-05 09:06:14 sysupgrade Image signature not present
1 2023-08-05 09:00:37 Reboot Request from Web UI

This is where I switched OFF the ping reboot. It seems to have continued working since then, for some strange reason… :laughing:

142 2023-09-06 08:37:38 CONFIG ping_reboot configuration has been changed
141 2023-09-06 07:10:06 Ping Reboot Restarting modem after 2 unsuccessful tries
140 2023-09-06 05:10:06 Ping Reboot Restarting modem after 2 unsuccessful tries
139 2023-09-05 23:20:00 Ping Reboot Restarting modem after 2 unsuccessful tries
138 2023-09-05 23:10:05 Ping Reboot Restarting modem after 2 unsuccessful tries
137 2023-09-05 21:10:06 Ping Reboot Restarting modem after 2 unsuccessful tries
136 2023-09-05 19:15:05 Ping Reboot Restarting modem after 2 unsuccessful tries
135 2023-09-05 17:25:06 Ping Reboot Restarting modem after 2 unsuccessful tries

This is the corresponding (same time) Network Logs

2510 2023-09-06 05:10:28 Network Operator Connected to operator (internal modem)
2509 2023-09-06 05:10:27 Network Type Joined network (internal modem)
2508 2023-09-06 05:10:27 Mobile Data Mobile data connected (internal modem)
2507 2023-09-06 05:10:17 Mobile Data Mobile data disconnected (internal modem)
2506 2023-09-05 23:23:34 Network Operator Connected to MTNSA ItsAllAboutYou operator (internal modem)
2505 2023-09-05 23:23:34 Network Type Joined LTE network (internal modem)
2504 2023-09-05 23:23:34 Mobile Data Mobile data connected (internal modem)
2503 2023-09-05 23:23:26 Network Operator Connected to MTNSA ItsAllAboutYou operator (internal modem)
2502 2023-09-05 23:23:26 Network Type Joined LTE network (internal modem)
2501 2023-09-05 23:23:26 Mobile Data Mobile data connected (internal modem)
2500 2023-09-05 23:10:17 Mobile Data Mobile data disconnected (internal modem)
2499 2023-09-05 21:13:14 Network Operator Connected to MTNSA ItsAllAboutYou operator (internal modem)

Hello,

These logs do not provide much insight into the cause of the issue. Would it be possible for you to share some logs from System → Administration → Troubleshoot → ‘View’ system logs?

By the way, if you look at the time when ping reboot was executed, you can see that it took place after the ping_reboot configuration was changed. I assume that change was when you disabled the ping reboot? The list shows the newest events on top.

Kind Regards,

The disconnection at 21:02:55 is normal. It is the local telecoms 4G tower which goes off every few hours. 12-15 minutes later it comes back online. this happens 3 times per day. The problem of the RUT950 is that it used to disconnect itself with no correlation to the tower switching off.

Fri Sep 8 20:58:10 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: deauthenticated due to local deauth request
Fri Sep 8 21:02:55 2023 user.notice qmux_track: Connection lost.
Fri Sep 8 21:03:10 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 8c:7b:9d:d6:d5:28
Fri Sep 8 21:03:10 2023 kern.notice BAYERN: WiFi client disconnected: 8C:7B:9D:D6:D5:28
Fri Sep 8 21:03:10 2023 daemon.info hostapd: wlan0: STA 8c:7b:9d:d6:d5:28 IEEE 802.11: disassociated
Fri Sep 8 21:03:11 2023 daemon.info hostapd: wlan0: STA 8c:7b:9d:d6:d5:28 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Sep 8 21:03:22 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: authenticated
Fri Sep 8 21:03:22 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: associated (aid 5)
Fri Sep 8 21:03:22 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:03:23 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:03:24 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:03:25 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:03:31 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: deauthenticated due to local deauth request
Fri Sep 8 21:06:02 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: authenticated
Fri Sep 8 21:06:02 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: associated (aid 5)
Fri Sep 8 21:06:02 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:06:03 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:06:04 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:06:05 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:06:11 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: deauthenticated due to local deauth request
Fri Sep 8 21:11:22 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: authenticated
Fri Sep 8 21:11:22 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: associated (aid 5)
Fri Sep 8 21:11:22 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:11:23 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:11:24 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:11:25 2023 daemon.notice hostapd: wlan0: AP-STA-POSSIBLE-PSK-MISMATCH 1c:d6:be:a0:63:44
Fri Sep 8 21:11:31 2023 daemon.info hostapd: wlan0: STA 1c:d6:be:a0:63:44 IEEE 802.11: deauthenticated due to local deauth request
Fri Sep 8 21:12:28 2023 daemon.info hostapd: wlan0: STA 8c:7b:9d:d6:d5:28 IEEE 802.11: authenticated
Fri Sep 8 21:12:28 2023 daemon.info hostapd: wlan0: STA 8c:7b:9d:d6:d5:28 IEEE 802.11: associated (aid 5)
Fri Sep 8 21:12:28 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 8c:7b:9d:d6:d5:28
Fri Sep 8 21:12:28 2023 kern.notice BAYERN: WiFi client connected: 8C:7B:9D:D6:D5:28
Fri Sep 8 21:12:28 2023 daemon.info hostapd: wlan0: STA 8c:7b:9d:d6:d5:28 RADIUS: starting accounting session 256D4D820206C27E
Fri Sep 8 21:12:28 2023 daemon.info hostapd: wlan0: STA 8c:7b:9d:d6:d5:28 WPA: pairwise key handshake completed (RSN)
Fri Sep 8 21:12:28 2023 daemon.info dnsmasq-dhcp[3551]: DHCPREQUEST(br-lan) 192.168.1.219 8c:7b:9d:d6:d5:28
Fri Sep 8 21:12:28 2023 daemon.info dnsmasq-dhcp[3551]: DHCPACK(br-lan) 192.168.1.219 8c:7b:9d:d6:d5:28 OZTOP
Fri Sep 8 21:12:29 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED e8:d8:d1:21:65:6f
Fri Sep 8 21:12:29 2023 kern.notice BAYERN: WiFi client disconnected: E8:D8:D1:21:65:6F
Fri Sep 8 21:12:29 2023 daemon.info hostapd: wlan0: STA e8:d8:d1:21:65:6f IEEE 802.11: authenticated
Fri Sep 8 21:12:29 2023 daemon.info hostapd: wlan0: STA e8:d8:d1:21:65:6f IEEE 802.11: associated (aid 1)
Fri Sep 8 21:12:29 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED e8:d8:d1:21:65:6f
Fri Sep 8 21:12:29 2023 kern.notice BAYERN: WiFi client connected: E8:D8:D1:21:65:6F
Fri Sep 8 21:12:29 2023 daemon.info hostapd: wlan0: STA e8:d8:d1:21:65:6f RADIUS: starting accounting session D232B3F5781DB1C4
Fri Sep 8 21:12:29 2023 daemon.info hostapd: wlan0: STA e8:d8:d1:21:65:6f WPA: pairwise key handshake completed (RSN)
Fri Sep 8 21:12:36 2023 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED e8:d8:d1:21:65:6f
Fri Sep 8 21:12:36 2023 kern.notice BAYERN: WiFi client disconnected: E8:D8:D1:21:65:6F
Fri Sep 8 21:12:36 2023 daemon.info hostapd: wlan0: STA e8:d8:d1:21:65:6f IEEE 802.11: authenticated
Fri Sep 8 21:12:36 2023 daemon.info hostapd: wlan0: STA e8:d8:d1:21:65:6f IEEE 802.11: associated (aid 1)
Fri Sep 8 21:12:38 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED e8:d8:d1:21:65:6f

Hi, I have absolutely the same problems with my RUT950.

Modem stops working multiple times a day.

This was already the problem on holday in Italy this year and now here in Germany, too (at the moment in Hamburg).

I use different SIM cards - WindTRE in Italy and Telekom in Germany, but same problem.

So for my kind of view the modem Firmware is faulty.
Router is three years old, but never had this really big problems.