Failover Failback on Asus RT-AC66U

[ASchaeffer]

Hello,
I am trying to add a wireless 4G modem to my system and use the failover/failback capability of the Asus RT-AC66U. "Enable Ping to Internet" (google) is set to "Yes" and it is set using a 4 second detect interval x 10 tries.

Here is what I've tried:
Firmware 380.4180 - If I remove the networking cable between my router and my cable modem, the router will failover to my 4G modem - recognizing the cat5 cable has been removed. Reinserting the cable failsback properly. This is what I expect! If instead, I remove the coax cable from my cable modem, the router will never recognize that there is no connection to the internet and never failover. Yes, I have the ping process enabled - though interestingly, if I try to use "network tools" to ping - whether connected or not - it doesn't return anything.

Firmware 380.4005 - Same exact behavior as above *BUT* "network tools" will ping properly if connected to the network and return nothing at all if there is no connection.

Merlin 380.64 - Works properly (as above) if cat5 cable is removed. If coax cable is removed from cable modem, it seems to recognize that it needs to failover as the 4G modem shows a standby state (and gets an IP address along with DNS) but never failsover. It shows the WAN as "connected" (even though it properly shows no IP address) and the Secondary as "Standby" but never failsover.

Not sure what to try next. Anyone have any suggestions?

Thanks,
Arn

 

[seanr22a]

ASUS implementation of Dual WAN is not working and from what I'm been reading on this forum Merlin stay away from their dual-wan implementation. Do a search on dual wan or similar and you find a lot of threads about it.

I'm one of many Asus router owners that bought the Asus router mainly because of its dual-wan capabilities but it's simply not working. 2 months ago I switched to a pfSense box and are now running with three WANs with load balancing and failover - not a glitch so far. My AC88U have been degraded to AP running Merlin 380.65_alpha1.

 

[Robert Lord Hood]

Hello,
I am trying to add a wireless 4G modem to my system and use the failover/failback capability of the Asus RT-AC66U. "Enable Ping to Internet" (google) is set to "Yes" and it is set using a 4 second detect interval x 10 tries.

Here is what I've tried:
Firmware 380.4180 - If I remove the networking cable between my router and my cable modem, the router will failover to my 4G modem - recognizing the cat5 cable has been removed. Reinserting the cable failsback properly. This is what I expect! If instead, I remove the coax cable from my cable modem, the router will never recognize that there is no connection to the internet and never failover. Yes, I have the ping process enabled - though interestingly, if I try to use "network tools" to ping - whether connected or not - it doesn't return anything.

Firmware 380.4005 - Same exact behavior as above *BUT* "network tools" will ping properly if connected to the network and return nothing at all if there is no connection.

Merlin 380.64 - Works properly (as above) if cat5 cable is removed. If coax cable is removed from cable modem, it seems to recognize that it needs to failover as the 4G modem shows a standby state (and gets an IP address along with DNS) but never failsover. It shows the WAN as "connected" (even though it properly shows no IP address) and the Secondary as "Standby" but never failsover.

Not sure what to try next. Anyone have any suggestions?

Thanks,
Arn

I'm having the same exact issue but on the n66u. At first it was with a DSL modem and I thougt that the stupid modems redirect for any time the connection was down was falsely letting the ASUS router think it still had a connection. But I tried with a cable modem today and it's doing the same thing. Won't detect that the modem has no internet. It's just doing a simple "If there's something plugged into my WAN port - use that. I don't care if it has internet or not."

REALLY, REALLY frustrating. I've emailed tech support to see if maybe they can address it with a new firmware patch...