Good evening,
I am having problems with my RUT955 with firmware version RUT9_R_00.07.06.16
This was also the case with RUT9_R_00.07.05.
The whole thing is noticeable in that it does not switch to the SIM.
It gives the error “WAN (XX) is down, no more backups to switch” in the LOG
Strangely enough, this problem is not always there, but only sporadically. The router is usually connected to the Wifi with the vehicle, when the vehicle leaves the Wifi it does not seem to select the mobile port, possibly marking it as not available.
In my opinion, the problem always reappears after a time X. A simple reboot via the web interface helps.
I have also added a scheduled reboot once a week, unfortunately this does not help either.
I’ve also thought about setting up a blanket reboot every time I leave the WiFi, but haven’t found an option yet.
I also don’t know what the router does when I activate the reboot on no connection. How often does it reboot if there really is no connection? Both sim cards no data, no wifi? Does it then reboot permanently? :'D
kind regards!
43381 2024-09-19 19:07:08 Failover WAN (wifi1) is down, switched to backup WAN (mob1s1a1)
43389 2024-09-21 13:38:50 Failover WAN (wifi1) is down, switched to backup WAN (mob1s1a1)
43400 2024-09-21 17:26:20 Failover WAN (mob1s1a1) is down, no more backups to switch
43399 2024-09-21 16:43:08 Switch Events Port link state of port LAN3 changed to DOWN
43398 2024-09-21 15:47:15 Failover WAN (mob1s1a1) is down, no more backups to switch
43397 2024-09-21 13:56:21 Switch Events Port speed for port LAN3 changed to 100 baseT
43401 2024-09-24 08:42:14 Failover WAN (wifi1) is down, switched to backup WAN (mob1s1a1)
43419 2024-09-24 17:14:00 Failover WAN (wifi1) is down, no more backups to switch
7505 2024-09-24 17:38:48 Failover WAN (mob1s1a1) is down, no more backups to switch
7504 2024-09-24 17:38:23 DHCP Leased XX.XX.XX.189 IP address for client MAC-ADR***
7503 2024-09-24 17:38:22 WiFi Wifi_Name: WiFi client connected: MAC-ADR***
7502 2024-09-24 17:37:51 Failover WAN (mob1s1a1) is down, no more backups to switch
7501 2024-09-24 17:37:51 Network Operator Connected to 26201 operator (internal modem)
7500 2024-09-24 17:37:51 Network Type Joined LTE network (internal modem)
7499 2024-09-24 17:37:51 Mobile Data Mobile data connected (internal modem)
ID Date Event Type Event
7515 2024-09-25 17:37:57 WiFi Wifi_Name: WiFi client connected: MAC-ADR***
7514 2024-09-24 21:21:32 DHCP Leased XX.XX.XX.163 IP address for client MAC-ADR***MAC-ADR***
7513 2024-09-24 18:01:08 WiFi Wifi_Name: WiFi client disconnected: MAC-ADR***
7512 2024-09-24 17:57:50 WiFi Wifi_Name: WiFi client connected: MAC-ADR***1
7511 2024-09-24 17:57:43 WiFi Wifi_Name: WiFi client disconnected: MAC-ADR***
7510 2024-09-24 17:57:43 WiFi Wifi_Name: WiFi client disconnected: MAC-ADR***
7509 2024-09-24 17:52:42 WiFi Wifi_Name: WiFi client disconnected: MAC-ADR***
7508 2024-09-24 17:52:23 Switch Events Port link state of port LAN3 changed to DOWN
7507 2024-09-24 17:41:03 DHCP Leased XX.XX.XX.172 IP address for client MAC-ADR***
7506 2024-09-24 17:41:01 WiFi Wifi_Name: WiFi client connected: MAC-ADR***MAC-ADR***
7000 Entries from Networklog; 40000 Entries from General Log as soon as the Problem was detected
Thank you for providing the logs and screenshots for additional information.
Could you try moving the wifi1 interface to the top in the Failover page (if this is your primary connection)? Additionally, ensure you select Flush connection on for both the ‘wifi1’ and ‘mob1s1a1’ interfaces by clicking on the Edit icon next to each specific interface, as shown in the screenshot below.
Regarding your question about the Auto Reboot feature: It works by sending a ping (ICMP request/packet) to a host (by default, it’s set to 8.8.8.8 – Google’s DNS server) at specified intervals. The router waits for a response from the host, and the Interval count represents the number of consecutive failures to receive a response before triggering the reboot. So, if both SIM cards and WiFi are unavailable, the router will reboot once the defined failure threshold is met – it won’t reboot permanently.
Let me know if this helps resolve the issue, or if you need further assistance.
I have tested the setup you described on a RUT955 device with firmware version RUT9_R_00.07.06.16, and the Failover functionality worked as expected. When the WWAN (wireless WAN / wifi1) connection was lost, it automatically switched to the mobile WAN (mob1s1a1). Once ‘wifi1’ became available again, the device reverted back to the primary WAN connection.
Regarding the “Flush connections on” option, you can find this setting by navigating to Network → Failover, and then pressing Edit on the required interface as shown in the screenshot below.
Here you should be able to select all four “Flush connections” options. This feature flushes established connections when the selected scenario occurs, ensuring that the priorities of your configured interfaces are renewed.
I hope this explanation helps! If you need further assistance or have any additional questions, please feel free to reach out.
unfortunately I still have the following line in the network event log. (See screenshot)
I had just tested what happens if I intentionally set the SIM2 mob1s2a1 as default, it recognizes it and switches to it. It also goes back when I reset it.
Nevertheless, this morning, for example, it happens that it recognizes that the mob1s1a1 is not available and says no backup available
Could you try performing a factory reset on the RUT955 and then reconfiguring the failover settings from scratch? After reconfiguring, please test to see if the issue persists.
If the issue still occurs after the reset, I’ve sent you a form to fill out. For the ticket ID, please use “9325”. Once submitted, I’ll reach out to you privately via HubSpot and request the troubleshoot file to investigate further.
Let me know if this helps or if you have any additional questions.
