how to set up a dual-wifi/ethernet failover for zero-downtime online matches — router rules, scripts, and cheap hardware that actually keep you connected

I’ve lost more than one ranked match to a flaky ISP at the worst possible moment, and if you’re reading this it’s because you want to stop that from happening. I’m going to walk you through practical, real-world options for a dual-WiFi/ethernet failover that actually keeps you online during online matches — from cheap hardware builds and router rules to scripts you can paste and run. I’ve tested these approaches across rigs and living-room setups, and I’ll tell you the trade-offs so you can choose what fits your budget and tolerance for tinkering.

Why dual-WiFi/ethernet failover matters for gamers

Redundancy isn’t just about preventing a short outage — it’s about preserving low latency and avoiding match losses. A single ISP or single link going flaky can drop you mid-game. A proper failover setup switches traffic to a secondary path (Wi‑Fi backup, cellular dongle, or a second ISP on ethernet) with minimal interruption. That said, not all failovers are created equal:

Failover (route switching): Simple and cheap, but your public IP usually changes and some games will disconnect briefly.

Bonding (session-level aggregation): Keeps one virtual IP across links and provides smoother transitions — but is more complex and/or paid.

Smart routing (per-application): Route only game traffic through the best link and non-critical traffic through the backup — more advanced but preserves bandwidth for downloads.

What you can build on a budget

Here are realistic builds that I’ve used or tested:

Cheap and easy: Consumer router with dual-WAN support (e.g., TP-Link Archer with OpenWrt, or some ASUS models). Add a second connection via Wi‑Fi client or USB cellular modem.

Flexible and powerful: OpenWrt on an inexpensive router (GL.iNet, TP-Link Archer C7, etc.) + mwan3 package for policy-based multi-WAN.

Robust and pro-level: pfSense/OPNsense on a small x86 box (or Netgate SG-1100) — best control and logging, but more setup work.

Cellular backup: Cheap USB 4G/5G modem or MiFi + Raspberry Pi or router with USB support for automatic failover.

Bonding solution: Speedify (software) or commercial SD-WAN appliances if you want session continuity.

Router rules & settings you should enforce

When you configure failover, pay attention to these router rules. They’re small, but they prevent big headaches:

Health checks: Your router must test a reliable host (8.8.8.8, 1.1.1.1, or your game provider’s IP) with small UDP/TCP/ICMP probes. Don’t just check link status — check actual route reachability.

Route prioritization: Primary link should be preferred for low-latency traffic. Put gaming ports/protocols into a high-priority policy.

Stateful firewall & NAT: Keep NAT and connection tracking enabled. If you change the default gateway, existing connections may break unless you use connection-aware failover or session bonding.

DNS handling: Use local DNS cache (dnsmasq) so DNS queries don’t stall during a switch. Also avoid DNS servers reachable only through the primary link.

MTU and fragmentation: Ensure correct MTU across links — mismatched MTU can cause weird packet loss or long latency spikes.

Option A — OpenWrt + mwan3: reliable, free, and very configurable

OpenWrt with the mwan3 package is my go-to for router-based failover without buying expensive appliances. It supports multiple WANs, health checks, and policies for per-device or per-port routing.

Basic steps:

Install OpenWrt on a supported router (GL.iNet or supported TP‑Link models are cheap and easy).

Configure both interfaces as WAN (e.g., eth0 = primary ISP, wlan0 client or eth1 = backup).

Install mwan3 and create health checks (pings to multiple IPs) and failover policies.

Create rules to route your gaming PC’s IP through the primary unless it fails — fallback to secondary.

mwan3 gives you careful control so the switch is automatic and you can log failures for debugging.

Option B — Simple Linux script for Raspberry Pi/Router

If you want a tiny dedicated failover monitor instead of changing your main router, a Raspberry Pi or small Linux machine works great. It pings a target and swaps default route when needed. Here’s a straightforward bash script I use for testing. Put this on a Pi with two uplinks (eth0 primary, eth1 backup):

failover.sh

<pre>#!/bin/bashPRIMARY_GW="192.168.1.1"SECONDARY_GW="192.168.2.1"CHECK_IP="8.8.8.8"DOWN=0ping_check() { ping -I eth0 -c 3 -W 2 $CHECK_IP >/dev/null 2>&1 return $?}while true; do if ping_check; then if [ $DOWN -eq 1 ]; then ip route replace default via $PRIMARY_GW dev eth0 echo "$(date): primary up, switched to primary" DOWN=0 fi else if [ $DOWN -eq 0 ]; then ip route replace default via $SECONDARY_GW dev eth1 echo "$(date): primary down, switched to secondary" DOWN=1 fi fi sleep 5done</pre>

Run this as a systemd service or in a screen session. You’ll need ip forwarding/NAT configured if the Pi is doing routing:

<pre># enable NATiptables -t nat -A POSTROUTING -o eth0 -j MASQUERADEecho 1 > /proc/sys/net/ipv4/ip_forward</pre>

This approach is cheap and easy, but be aware it replaces the default gateway, so open TCP/UDP sessions may drop when the route switches.

Option C — Bonding for true session continuity

If you can’t tolerate disconnections, look into bonding/aggregation. Speedify is the most consumer-friendly option: it runs on Windows/macOS/Linux and bonds multiple links at the packet level so your public IP is maintained and sessions survive. Alternatives include setting up a VPN server (VPS) and using multipath VPNs (WireGuard + multipath/multiplexing hacks), or commercial SD-WAN services.

Trade-offs: bonding usually costs money or more advanced setup (VPS + VPN config). It’s the only way to really keep UDP game sessions alive during a link switch in many cases.

Practical tips I always use

Test during downtime: Schedule a practice session to simulate failovers. Don’t discover problems mid-ranked match.

Use multiple health targets: Ping two or three stable IPs, not just one. Some ISPs block ICMP or rate-limit it.

Prioritize traffic: Mark your gaming PC’s traffic as high priority in the QoS settings so background syncs don’t choke your game during failover.

Log everything: Keep logs of failovers. That helps you figure out whether the link or the router script is the culprit.

Consider a battery/UPS: Many “outages” are power blips. A small UPS for your router + modem goes a long way.

Brands and gear I recommend

Budget OpenWrt-ready router	GL.iNet GL-MT3000 (Brume) or TP-Link Archer C7
Small x86 firewall	Protectli Vault, used mini-PC for pfSense/OPNsense
Cellular backup	Huawei/EasyLink USB modem or a simple mobile hotspot (MiFi)
Bonding	Speedify software or VPS-based WireGuard multipath

Setups vary a lot by house, ISP, and how sticky your game server is about IP changes. If you want, tell me what hardware you currently have (router model, whether you can flash OpenWrt, whether you’re okay with a Raspberry Pi) and I’ll propose a step-by-step configuration tailored to your kit.