# A link drops, the others carry it.

Each link is watched in both directions, all the time. When one goes quiet, its traffic moves to the others, and what was open carries on.

_Every device · Your server · On by default_ 

Ten minutes on three links 

In speed mode: the 5G goes quiet for a while and the other links carry its traffic. Later it keeps dropping and is held back a while. The connection never breaks.

In redundant mode: every packet goes on every good link, so the same drop costs nothing, at about one link’s speed.

Speed, the default, uses every link at once. The phone joins only while the others are busy.

Redundant sends every packet on every good link, both ways. Losing a link costs nothing, at about one link’s speed.

**Fig. 1 · Example** The words in the lanes are the ones the product’s activity log uses.

## What happens

1. Fenris checks every link all the time, in both directions. A link that looks connected but carries nothing is found the same way as one that is unplugged.
2. When a link goes quiet with data waiting, its traffic moves to the others. What was open carries on, because the address the world sees is your server’s, and that has not changed.
3. The link rejoins by itself once it carries again.
4. A link that keeps flickering is held back a while. It is tried again, and returns when it stays up.
5. Each drop the other links absorbed is counted. The app and the console show the count.

## What it costs

While one link is away, the others carry everything.

**Speed**

You have what the remaining links carry. Say your fibre gives 100 Mbps and your 5G 60: with the fibre quiet, about 60\. _Example:_ 

**Data**

If the link that is left is metered, its plan carries everything meanwhile. A cap stops it there, and a backup link is kept for exactly this.

**Redundant mode**

It sends every packet on every good link, so a drop costs nothing at all. It runs at about one link’s speed, and uses each link’s data.

**What was in flight**

Packets already on the quiet link are sent again on another. A call’s copy is there already.

## Turn it on

It is on from the start. These change what stands ready.

| To                                   | Command line                                                            | Router UI and app     |
| ------------------------------------ | ----------------------------------------------------------------------- | --------------------- |
| Keep a link for when the others fail | fenris link usb0 \--role backup                                         | Links, the link, Edit |
| Send everything on every good link   | fenris mode redundant                                                   | Home, Mode, Redundant |
| See what went quiet, and when        | fenris activity                                                         | Activity              |
| Check each step to your server       | fenris check                                                            | Diagnostics           |
| List a second server                 | fenris-client join \--state /etc/fenris/state \--backup '<invite link>' | Servers               |

### Where to find it

**Router UI** Home. Link drops absorbed, and each link’s state.

The router’s own page, Home, with example data: connected, two of three links up, the speed over both as one, and each link with its share.

**The app** Home.

The Android app’s Home screen, with example data: protected, two links up, and each link’s share of the traffic.

**The console** A device’s page. Each drop the other links absorbed is counted.

The console’s page for one device, with example data: its state, its throughput, the drops its links absorbed, and each link side by side.

**The product** Three of its own screens, with example data.

## What it keeps

How each link is doing, for 24 hours, in memory, and each session in the audit log for a year. The count of drops belongs to the session. Nothing is kept about what the links were carrying.

[Everything your server keeps](https://fenris.network/privacy#kept)

## Where it stops

**Every link at once**

If every link drops together, the session is lost. It comes back on every link as soon as one returns.

**The same cause**

Links that fail for the same reason fail together: two SIMs on one tower, or Wi-Fi and Ethernet to one router.

**Your server**

If your server stops answering, no link can reach it. With a second server listed, devices move to it after 10 seconds, and open connections end at the change.

**A count, not a promise**

The console counts each drop the other links absorbed. It is a count of what happened, not a promise that nothing ever drops.

## Related
