Bonding: your two internet connections play at the same time — and the fastest copy always wins

7 min read
bondingpacket-duplicationtwo-connections4gfailovertibiarubinotpokexgamespxgresilience

If you’ve played Tibia, RubinOT or PokéXGames with two internet connections, you know failover: when the main one drops, the other takes over. It works — but there’s a moment, however short, between the drop and the switch. In that moment the packet is lost. Mid-hunt, that’s enough for a DC.

Bonding solves this differently: it doesn’t wait for anything to drop. Both connections carry the game at the same time — if one fails, the copy that came over the other has already arrived. Zero gap.

What bonding is

In passive mode, PingArmor uses one connection at a time and keeps the other in reserve. In bonding, it uses both at once: each game packet is sent in duplicate, one over the primary and one over the secondary, simultaneously.

On the other side, whoever arrives first wins. The server (and your PC) keeps the first copy and discards the second automatically — this is free, WireGuard itself already rejects the repeated packet. You don’t see any of it: you just feel the connection stop stumbling.

The consequence is what matters: for the game to drop, both connections would have to fail in the same millisecond. As long as one is up, the packet gets through.

Passive switches; bonding duplicates

This is the difference that changes everything. It’s not the same protection “a bit better” — it’s a different approach:

Passive failoverBonding
How it actsReactive — waits for the primary to drop, then switchesProactive — both already carry the game from the 1st packet
On a dropDetects → switches connection → there’s a gapThe copy from the other connection was already arriving — zero gap
RedundancySits in reserve, kicks in laterAlready active the whole time

Passive is a plan B that has to be triggered. Bonding is a double plan A — the redundancy isn’t triggered, it’s already there.

On the dashboard, the interfaces card shows both connections working together, with the DUPLICATING badge on both:

Network Interfaces · Bonding 28ms
Ethernet Duplicating
↑ 1.2 MB ↓ 5.4 MB
Mobile USB Duplicating
↑ 205.1 KB ↓ 810.5 KB 4G

Notice: both rows say DUPLICATING. There’s no “active” and “standby” like in failover — in bonding, both are carrying the game at the same time.

The fastest copy

Since each packet goes out in duplicate, one of the two paths delivers first. It’s not always the same one: it depends on which connection has the shortest millisecond at that moment. The panel shows who’s winning the race:

Fastest copy
Ethernet 60% Mobile USB 40%
bonding: ~3.2 ms faster

Here Ethernet won 60% of the races and 4G, 40% — and overall bonding delivered ~3.2 ms sooner than the best single connection would. A balance near 50/50 is normal with two good connections. If one gets worse, the other naturally starts winning more races and holds the game up — without you touching anything.

Only the game is duplicated (and why your data plan thanks you)

Duplicating everything over both connections would double the usage — and on metered 4G that would be expensive. That’s why bonding is surgical: only game traffic is duplicated. Everything else (browser, YouTube, Discord, Windows updates) goes exclusively over the primary.

This isn’t a setting you adjust — it’s a fixed rule of the product. The web stays pinned to the primary by route priority, deterministically. In normal operation, your secondary carries only the game copies — which are light. That’s what the card’s notice shows:

Mobile USB 4G
Bonding duplicates game traffic over the secondary. This session it's using ~1.5 MB/h. On metered 4G, watch the per-interface total above.

In other words: day to day, turning on bonding doesn’t blow your data cap — 4G only carries the game copy, which is usually a few MB per hour. And you track the per-interface number in real time, without installing anything else. (It’s the same count as the per-interface 4G monitor.)

Data usage, no sugarcoating

There’s one case where the math changes, and we’d rather tell you up front: when the primary drops completely.

If your main internet dies for good (the cable dropped, the ISP wobbled), 4G becomes the only one left — and then it takes on everything: the game and the web. In that scenario, the browser, Discord and whatever else is open start eating the data cap alongside the game.

That’s the price of maximum resilience: bonding prioritizes keeping you connected over saving data. The game stays protected by duplication, but the data cap gets used until the primary comes back. The recommendation is simple: if your primary dropped and you’re on 4G only, close what you don’t need (or disconnect) until the cable is back — and watch the per-interface usage, still there on the card showing you the total.

The honest edges: what bonding v1 doesn’t solve yet

No protection is perfect, and we won’t pretend this one is. There’s one known limit of this first version of bonding — worth knowing when it happens and what to do:

The web going to 4G on a total drop — the scenario from the previous section. On a complete death of the primary, the web migrates to 4G and eats the data cap. The game stays protected by duplication; the data cap doesn’t. What to do: close heavy web traffic while you’re on 4G only, and watch the usage on the card.

This is on our roadmap to improve in upcoming versions. We’d rather launch with this limit documented than sell you a “perfect” protection that isn’t.

How to turn on bonding

Turning it on is one click. Go to Network Setup (the gear icon), confirm you have both interfaces selected — primary and secondary — and enable the Bonding (two simultaneous connections) option:

Network Setup
Select your network interfaces for failover protection.
Primary Interface (preferred)
Ethernet (192.168.0.159)
Secondary Interface (backup)
Mobile USB (10.177.16.214)
Bonding (two simultaneous connections) i
Sends game traffic through both interfaces at the same time: the fastest copy wins and losing one of them doesn't drop the game.
⚠ Bonding duplicates game traffic over the secondary. On metered 4G, watch the per-interface total.

Done. The next time you connect, the tunnel comes up in bonding mode and both connections start carrying the game together. The mode lasts the whole session: once connected, it heals itself underneath, without ever reconnecting the tunnel (which would drop the game). Prefer the usual passive mode — one connection at a time, data cap untouched? Just leave the option off; nothing changes.

In the end, it’s the game that doesn’t drop

Those are the edges — rare, honest, and always with a way around them. But they’re not the main story. The main story is what happens day to day: your two connections carrying the game together, the fastest copy winning every race, and that hiccup of switching connections simply ceasing to exist.

It’s the same philosophy as PingArmor’s other features: protecting your game above all, and being transparent about how. Passive failover already handled one connection dropping; bonding raises the bar — instead of switching after it drops, it never lets it run short.

Any questions about this? Check the FAQ or reach out at [email protected]. And if you don’t use two connections yet, this guide shows how to start.


Protect your connection now

Try PingArmor free for 3 days. No credit card required.

Try free for 3 days