Dual WAN Failover Setup and Testing When One Line Goes Down
The biggest real-world gift of two connections is not speed — it is that one line can die and nobody's work stops. But failover only protects you if it is set up and tested before the day the line actually fails.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 9 minute read
🎥 Watch the full process in the video — combining 2 connections with real testing, step-by-step
In the combining video, the office runs multiple lines, and the quiet hero of that setup is failover: when one connection drops, the router moves traffic to the surviving line automatically. This page covers the settings that decide how fast and how cleanly that switch happens — and the honest limits, because failover is fast, but it is not magic.
Router status during a failover event
🔴 WAN1 — BroadbandDisconnected
🟢 WAN2 — Leased lineConnected — carrying all traffic
Live check from a PC
Reply from 8.8.8.8: bytes=32 time=21ms TTL=117
Reply from 8.8.8.8: bytes=32 time=20ms TTL=117
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=34ms TTL=116
A short gap of lost pings during the switch is normal — the router needs time to detect the failure
1
Choose the Right Mode for Your Goal
Failover mode: line 2 stays idle and takes over only when line 1 fails — best when line 2 is costly or capped, like a 4G SIM
Load balance with failover: both lines work daily, and the survivor automatically absorbs everything when one dies — best for two proper broadband lines
Pick the mode in the router's WAN / Dual WAN section, then set which line is primary
Either way, failover must be switched on — on some routers load balancing alone does not remove a dead line from rotation, which leaves half your new sessions going nowhere.
2
Set the Health Check Properly
The router can only fail over when it knows a line is dead. It checks by pinging a target through each WAN:
Set the check target to a reliable anycast address such as 8.8.8.8 or your ISP's DNS server
Check interval: around 5-10 seconds; failure count before switching: 3 is a sensible balance
Avoid pinging the router's own gateway address only — a line can have a live gateway and dead internet behind it
With these values, detection usually takes 15-40 seconds. Tighter settings switch faster but can flap on a shaky line; looser settings feel calmer but leave a longer dead gap.
3
Test It Yourself — Pull the Cable
Never trust a failover you have not watched working:
Start a continuous ping on a PC: ping 8.8.8.8 -t
Note your current public IP in a browser (search 'my IP')
Unplug WAN1's cable from the router
Watch the ping: some Request timed out lines are expected, then replies should return
Check 'my IP' again — it should now show the second line's address
Reconnect WAN1 and confirm traffic settles back (this is called failback)
If pings never return, the health check or mode is wrong — fix it now, in peace, not during a real outage.
4
What Failover Cannot Do — The Honest Part
Live sessions break: an ongoing video call, game or download was connected through the dead line's public IP — it will drop and reconnect on the new line. Failover saves the next minute, not the current second
Speed halves: after failover, everyone shares one line — work continues, but big transfers slow down
Both lines can share one fate: two connections entering through the same pole, duct or exchange can die together in a fibre cut or power failure. A 4G backup on a different medium is the real insurance
Set expectations with your family or team in these exact words and failover will be loved for what it is: continuity, not invisibility.
🔴 An untested failover is a hope, not a setup. Pull the cable once a month, watch the pings recover, and check the public IP actually changes. Five minutes of testing beats discovering a wrong setting during a real outage.
🎥 Watch the Complete Video Guide
See the video for the office setup with multiple live lines — and how the connections behave when real work is running on them.
Typically 15 to 60 seconds, depending on the router's health-check interval and failure count. During that gap, pages stall and calls may drop. After the switch, new sessions work normally on the surviving line.
Will my download continue after failover?
The download's connection was tied to the dead line's public IP, so it breaks. Download managers with resume will reconnect through the new line and continue; a plain browser download may need to be restarted.
Failover or load balancing — which should I choose?
Choose failover when the second line is expensive or data-capped (like a 4G SIM) and should stay idle. Choose load balancing with failover enabled when both are full broadband lines — you get daily combined capacity plus automatic backup.
This guide is based on the Technical Anshu video on combining 2 LAN connections • Stuck on a step? Ask in the video comments — the community helps there 🙏