I also have this problem where the failover doesn’t revert back to priority 1 (cellular), even when I know the cellular signal is restored and has internet again.
For my setup I am using cellular as priority 1 connection, since it has more bandwidth.
My cellular ISP is resetting the IP every 4 hours, so there is a short period of disconnecting/connecting happening, not ideal but it is what it is.
Failover to priority 2 (ethernet with HTTC connection) is working perfectly, however mwan3 is not switching back to the interface modem_0001, when cellular comes available again.
It seems mwan3 module does not update the status of interface modem_0001
root@GL-X3000:~# mwan3 interfaces
Interface status:
interface wan is online 03h:49m:52s, uptime 07h:03m:54s and tracking is active
interface wwan is offline and tracking is down
interface tethering is offline and tracking is down
interface wan6 is offline and tracking is down
interface wwan6 is offline and tracking is down
interface tethering6 is offline and tracking is down
interface secondwan is offline and tracking is down
interface secondwan6 is offline and tracking is down
interface modem_0001 is error and tracking is active
interface modem_0001_6 is offline and tracking is down
Performing a ping test on the cellular interface to check if the modem is connected
root@GL-X3000:~# ping 1.1.1.1 -I rmnet_mhi0
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: seq=0 ttl=51 time=44.962 ms
64 bytes from 1.1.1.1: seq=1 ttl=51 time=44.775 ms
64 bytes from 1.1.1.1: seq=2 ttl=51 time=44.740 ms
64 bytes from 1.1.1.1: seq=3 ttl=51 time=42.574 ms
64 bytes from 1.1.1.1: seq=4 ttl=51 time=44.473 ms
64 bytes from 1.1.1.1: seq=5 ttl=51 time=39.152 ms
64 bytes from 1.1.1.1: seq=6 ttl=51 time=32.117 ms
^C
--- 1.1.1.1 ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 32.117/41.827/44.962 ms
root@GL-X3000:~# ping 8.8.8.8 -I rmnet_mhi0
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=110 time=88.329 ms
64 bytes from 8.8.8.8: seq=1 ttl=110 time=32.245 ms
64 bytes from 8.8.8.8: seq=2 ttl=110 time=33.109 ms
64 bytes from 8.8.8.8: seq=3 ttl=110 time=29.964 ms
64 bytes from 8.8.8.8: seq=4 ttl=110 time=31.722 ms
64 bytes from 8.8.8.8: seq=5 ttl=110 time=32.531 ms
^C
--- 8.8.8.8 ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 29.964/41.316/88.329 ms
root@GL-X3000:~#
I also tested removing the ethernet cable, so that interface wan (eth0) becomes unavailable, and interface modem_0001 was the only remaining interface.
I was able to navigate internet, so cellular connection was up and ok. This while mwan3 stats still showed interface modem_0001 as error.
interface modem_0001 is error and tracking is active
Now when I plug the ethernet cable back, the interface wan (eth0), which has priority 2, becomes the active interface again (traceroute test confirmed this). So still not switching back to cellular (priority 1).
To get mwan3 to update the status of interface modem_0001 I can manually trigger a restart of the module either switching priority order of the failover interfaces in Multi-Wan (for example inverting Teetering and Repeater, both not used) or using the “mwan3 restart” command via SSH. Both these methods will restart mwan3 after which cellular interface modem_0001 becomes the active WAN connection again.
root@GL-X3000:~# mwan3 interfaces
Interface status:
interface wan is online 00h:01m:17s, uptime 00h:09m:55s and tracking is active
interface modem_0001 is online 00h:01m:14s, uptime 11h:18m:30s and tracking is active
Let me know if I can supply any more data to perform proper debug of this issue.
Thanks
GL-X3000
Firmware: v4.0 - 0406release1 - 2024-01-23 15:20:08(UTC+08:00)
RM520N version: RM520NGLAAR01A07M4G_01.201.01.201
