Has anyone successfully implemented on Route 10 Router - WAN 1 and WAN 2 with dual ISP’s for use as failover?
I am able to get WAN 1 to work on AT&T and WAN 2 using Spectrum, but I am not able to get them to properly fail over and back properly.
I can go from WAN 1 to WAN 2. But not From WAN 2 to WAN 1.
Wondering if anyone else has any similar experience with this?
During testing, did you set the metric correctly for each? I have not played with this yet, but I bet that will help.
This makes sense. Thank you
So put the Metric at 20 on WAN 1 and 30 on WAN 2. I am not sure what numbers to use?
I did reboot Route 10 unit and it now will not move to WAN 1 at all. it is stuck on WAN 2 and will not move back to WAN 1.
Is there a failover via ping? I can not see this feature… ie. set ping 1.1.1.1 if no ping detected go to WAN2. when WAN1 has ping switch back.
Currently WAN failover will work if 1) Lower metric link goes down, or 2) Lower metric gateway is unreachable. If you see a case where this isn’t true, we’d love to know. We are actively working on improving this to also ping an internet address to detect connectivity.
Multi-WAN isn’t yet implemented. So the if WAN with metric 1 fails 2 will work but 2 won’t go to 1. When Multi-WAN rolls out it will have load balance and true failover I’m guessing.
Hey Jeff, Do we know if this still works? Was working perfectly fine but no idea when it broke but when WAN1(Metric 100) is down WAN2 (Metric 200) doesn’t work/take over. It used to work but no longer.
@WhyAydan It depends on the failure mode. Currently the failover is very basic. Are you disconnecting the link on WAN1 or otherwise making its gateway IP unavailable in your test?
I am indeed unplugging the cable 
Issue might be that both WANs are static?
I ran into this earlier and observed when the WAN interfaces are static the default route associated with that WAN is not removed so the traffic will be blackholed until you either manually pull it or bring down the interface using something like ifconfig eth3 down. I since transitioned back to using DHCP and that part is taken care of.
I ended up having to remove the metric manually from ssh to bring the internet back. But hey, the MultiWAN isn’t fully here yet.
Can confirm setting it as DHCP for both WANs on a test environment works. But the moment I set static for both WANs (as this is what both my ISPs) the failover doesn’t work
