Hello friends!
I have trouble with failover performance on my RUT955.
I have Starlink on WAN set to failover to Mobile WAN. (I will show screenshots of failover settings).
Starlink seems to have a VERY brief interruption every two hours - perhaps to do with satellite movements.
according to the logread output, the wan connectivity is detected as lost at 9:58:06, and reconnected again within 2s, at 9:58:08, however the ifdown event starts after 1s at 9:58:07.
Now at 9:58:10 it says WAN is now up
then at 9:58:14 it says "Execute disconnected event on interface wan (eth1)"
and at 9:58:16 kern.info WAN (wan) is down, switching to backup WAN (mob1s1a1)
What I'm seeing here is a very brief interruption, but the mechanism of failing over is initiated, and doesn't stop, even though the WAN connectivity comes straight back. To fix this I have tried increasing the time interval (from 10s to 30s) between ping tests for failover and also changing the thresholds for deciding when the WAN is up or down (this was set at 50 and didn't help), but I still get the failovers, regularly, and they interrupt my connections.
Any ideas?
( I also am aware I don't understand the meaning/application of flush connections, or of failover policies, so perhaps my answer lies here but I will need help to understand this).
I should also say that before the RUT955, I used a RUT240 with very old firmware (6.2 ish?) and it didn't have this problem - the connections were maintained perfectly.
Logread output attached
EDIT - sorry added logread file