atchristian
New Around Here
Hey Everyone,
I am kind of at a loss with what to do here. I currently have DUAL WAN working (without the fallback option checked but I do have the Auto Network Detection with Ping enabled) on my AC5300. My network will now fail-over to my backup internet if there are no responsive pings to google for 60 seconds.
This weekend I had an outage and my network switched over to the backup WAN without a hitch. When my primary internet comes back online, I simply reboot my router and it auto connects to the primary WAN. Here's a test that I performed and now I have an issue. I was thinking "what if I rebooted the router while the primary WAN was still down? Would it detect that outage and fail-over upon startup?"
It does not. I "killed" the primary WAN, watched my router fail-over to the backup. I then rebooted the router while the primary was still unavailable. When it came back online, it just sat there for 5 minutes while saying "Connected" to the primary WAN. Has anyone ever seen this? This seems to be a major design flaw that the ping timer does not detect an outage upon startup.
Am I possibly missing something here? Is there a way in the admin interface that I could tell the router to switch back to the primary WAN without rebooting it? Why does the ping not seem to work upon a fresh reboot? Thanks for any help!
I am kind of at a loss with what to do here. I currently have DUAL WAN working (without the fallback option checked but I do have the Auto Network Detection with Ping enabled) on my AC5300. My network will now fail-over to my backup internet if there are no responsive pings to google for 60 seconds.
This weekend I had an outage and my network switched over to the backup WAN without a hitch. When my primary internet comes back online, I simply reboot my router and it auto connects to the primary WAN. Here's a test that I performed and now I have an issue. I was thinking "what if I rebooted the router while the primary WAN was still down? Would it detect that outage and fail-over upon startup?"
It does not. I "killed" the primary WAN, watched my router fail-over to the backup. I then rebooted the router while the primary was still unavailable. When it came back online, it just sat there for 5 minutes while saying "Connected" to the primary WAN. Has anyone ever seen this? This seems to be a major design flaw that the ping timer does not detect an outage upon startup.
Am I possibly missing something here? Is there a way in the admin interface that I could tell the router to switch back to the primary WAN without rebooting it? Why does the ping not seem to work upon a fresh reboot? Thanks for any help!
