# Bonding, failover and load balancing.

Three ways to use more than one internet line. They differ most in what happens to the things you already had open when a line goes.

## The same cut, three ways.

Two lines, fibre and 5G. A call is on, and a big download is running. Then the fibre is cut.

The same cut played three ways. Failover: the call and the download are on the fibre; when it is cut both break and start again on the 5G, from a new address. Load balancing: the call is on the fibre and the download on the 5G; the call breaks and rejoins, the download carries on. Bonding: both use both links; when the fibre is cut both carry on over the 5G, from the same address.

Made-up values, to show how it works. Switch the fibre back to see the moment before. Say the fibre gives 100 Mbps and the 5G 60\. Bonded, a download gets close to the two together, less a little for the tunnel. After the cut, every approach has only the 5G.

## What each one is

The first two are quoted from the pfSense documentation, a router system that does both: [Multi-WAN concepts](https://docs.netgate.com/pfsense/en/latest/multiwan/concepts.html). Checked on 22 Nov 2026.

**Failover**

“The ability to switch from one or more WANs to an alternate set…”. One line carries everything, and the next takes over when it fails.

**Load balancing**

It “distributes connections over multiple WAN connections in a round-robin fashion”, and it “operates on a per-connection basis, not a per-packet basis”.

**Bonding**

In our words: every connection is spread over every link, piece by piece, and put back together at a server at the far end. That server is what websites see.

## Situation by situation

| Situation                   | Failover                                           | Load balancing                                         | Bonding                                                         |
| --------------------------- | -------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------------------------- |
| Many people browsing        | Fine, on one line.                                 | Good. Their connections are shared out over the lines. | Good. Every connection can use every link.                      |
| One big download            | One line.                                          | One line. A connection stays where it was put.         | Every link at once.                                             |
| A line dies during a call   | The call drops and rejoins from a new address.     | It drops if it was on that line.                       | It carries on. Its copy was already on another link.            |
| A line slows but stays up   | Often nothing happens: the line still looks alive. | Connections on it stay on it.                          | Its traffic moves when it goes quiet with data waiting.         |
| The address websites see    | Changes when the line does.                        | Differs from one connection to the next.               | Always your server’s.                                           |
| What you have to run        | A dual-WAN router. Nothing else.                   | A dual-WAN router. Nothing else.                       | A server at the far end as well.                                |
| The road your traffic takes | Straight out.                                      | Straight out.                                          | By way of your server: a detour, small when the server is near. |
| Data used                   | What you use.                                      | What you use.                                          | A little more. Copies of calls travel twice.                    |
| Every line fails at once    | Offline until one returns.                         | Offline until one returns.                             | Offline until one returns. Then it reconnects by itself.        |

## Why the address matters

A website knows you by the address you come from. With failover it first sees your fibre’s address and then, after the switch, your 5G’s. To the website those are two strangers, so the call, the game and the download all break and have to start again.

With bonding the website only ever sees **your server’s** address, and that does not change when a link drops. That is why connections that were already open carry on.

[How it works, step by step](https://fenris.network/how-it-works)

## Which to choose

- **Failover, if you only need to get back online.** A whole home or shop is back in a moment, with no server to run. What was open starts again.
- **Load balancing, if many people share the lines.** An office of browsers and mailboxes uses both lines well. No single download or call gets more than one.
- **Bonding, if what is open has to carry on.** A call, a class, a long upload. It costs a small server at the far end, and a detour through it. [Ask for early access](https://fenris.network/early-access)
