When we specify Failover order for Multi wan, let’s say we have 3 wan 2 from Wifi 2.4 and 5 Ghz and one from WAN eth port. Sometimes when I change the order of WANs in failover metrics, i can see the Interface’s order is changing in OS (SSH to RUT and run route) but this does not affect the UI. I can still see that the lower priority (higher metric) is Online and the higher priority (lower metric) is in Standby mode.
We really need to monitor which interface is activated to provide a stable connection at all times and it prevent us to do that.
Could you please provide the following for better understanding:
A screenshot of your Failover metrics configuration (with any sensitive details such as public IPs hidden),
Output of ip r or route -n from the CLI/SSH,
Also screenshots of the configuration settings for each of the interfaces used in failover.
Just to clarify – when you change the metrics in Failover, it should also update the default route priorities, which can be seen in the Network → WAN page.
Unfortunately (or fortunately ) I couldn’t recreate the problem. what happened for me again today was that the refresh button on the Failover page (screenshot below) doesn’t work and refreshing the whole page updated the Failover is actually acting the way it should.
Also, the Network → WAN page doesn’t help much. When something happens and I don’t know which WAN is being used as the main one, I need to go to the failover page, especially when there are multiple WANs (more than 2) and more than one of them are alive, and RUT should select the one with higher priority.
In the Failover page, i have the possibility to see that the lower priorities are in the “Standby” state when higher priority is “Online”.
) I couldn’t recreate the problem. what happened for me again today was that the refresh button on the Failover page (screenshot below) doesn’t work and refreshing the whole page updated the Failover is actually acting the way it should.
