I'm seeing an issue with failback, however. The ping failure that causes the failover initially appears to be an issue on Comcast's network. The cable modem is not going down. Since the cable modem interface is still active, as soon as the the Failback Execution Time expires, the router tries to fail back to the cable modem. However, the Comcast network still has an issue and the ping fails again. So, the router ends up bouncing between the primary and secondary WAN. Having downtime every few minutes while the router tries to fail back to a connection that isn't really working kind of defeats the purpose of auto failover and failback.
I think the router should not fail back until a ping on the primary WAN succeeds, indicating service is really restored on the primary. A dual WAN router that I used years ago handled this correctly.
Last edited:
