CaptnDanLKW
Senior Member
House under construction, temporary fiber line strung out in the open, tucked under siding, draped across trees. Been damaged by the 'skilled' people doing construction 4 times in 9 months - again this morning.
Finally, just trying to figure out and learn the failover process - it never 'just works'.
I suspect the root cause is that when my fiber goes out, my 'Primary WAN' never seems 'fully' go down - the LED never goes RED and the main screen in the router continues to say 'connected'. The Fiber gateway is still up and eth0 is still connected so the PHY interface status never changes. This is probably 99% of all ISP failure scenarios, so I can't imagine eth0 has to go down before a failover event is triggered.
So dual wan does not fail over unless I physically shut down the Fiber Gateway, taking down eth0. Then it goes RED, then I can plug in my phone and it will start to work on the 'Secondary WAN'
Is this just a by-product of having a Static Address? or does the detection use the "Network Monitoring" (& its settings) and/or 'Enable WAN down browser redirect notice'?
TIA
Finally, just trying to figure out and learn the failover process - it never 'just works'.
I suspect the root cause is that when my fiber goes out, my 'Primary WAN' never seems 'fully' go down - the LED never goes RED and the main screen in the router continues to say 'connected'. The Fiber gateway is still up and eth0 is still connected so the PHY interface status never changes. This is probably 99% of all ISP failure scenarios, so I can't imagine eth0 has to go down before a failover event is triggered.
So dual wan does not fail over unless I physically shut down the Fiber Gateway, taking down eth0. Then it goes RED, then I can plug in my phone and it will start to work on the 'Secondary WAN'
Is this just a by-product of having a Static Address? or does the detection use the "Network Monitoring" (& its settings) and/or 'Enable WAN down browser redirect notice'?
TIA
