# How several links become one connection.

The long version, in thirteen short chapters. Each answers the problem the one before it raised, and each says where it stops. One packet of a download and one of a call run through all of it.

Follow one packet of a download and one packet of a call, in nine steps, from an app on your laptop, through Fenris on your router, over your links to your server, out to the site and back.

_**Example** A router with fibre and 5G. The names in mono are the product’s own; the address is an example._

01 

## One link at a time

Your phone, laptop or router has several ways online, but it sends everything down one of them and leaves the rest idle. Fenris uses all of them at once, so a download takes every link, and when one drops the others carry on.

Who carries a download 

Fibre _100 Mbps_

5G _Idle_

Together _100 Mbps_

Fibre _100 Mbps_

5G _60 Mbps_

Together _About 150 Mbps_

**Fig. 1 · Example** Say your fibre gives 100 Mbps and your 5G 60\. Today a download gets 100\. With Fenris it can use both: close to the two together, less a little for the tunnel.

**The limit.** Bonding cannot make one link faster. With a single link, Fenris is an encrypted tunnel to your server and nothing more.

02 

## Why not switch, or share?

A failover router waits for one line to die and then switches. Everything you had open starts again, because the address the world sees has changed: to a website, your fibre and your 5G are two strangers.

A load balancer puts each connection on one line. Many downloads share the lines, but any one download still gets one. Bonding splits even a single download, and keeps one address however the links come and go.

| Situation             | Failover                      | Load balancing                     | Bonding                            |
| --------------------- | ----------------------------- | ---------------------------------- | ---------------------------------- |
| Links in use          | One. The others wait.         | Several, each connection on one.   | All, every connection across them. |
| One big download      | One link.                     | One link.                          | Every link.                        |
| A link drops          | Everything open starts again. | The connections on it start again. | The others carry on.               |
| The address sites see | Changes with the line.        | Differs by connection.             | Always your server’s.              |
| What it needs         | A dual-WAN router.            | A dual-WAN router.                 | A server at the far end.           |

[The same cut, played three ways](https://fenris.network/compare/bonding-failover-load-balancing)

**The limit.** If every link drops at once, the session is lost. It comes back on every link as soon as one returns.

03 

## The pieces have to meet somewhere

Packet · steps 6 to 8

A website talks to one address. If a download leaves in pieces over two links, something has to put the pieces back together before they reach the site, and the site has to see a single sender.

That something is your Fenris server. Your devices send every link’s share to it, and it talks to the internet as you. Think of a parcel sent in pieces by two couriers: it needs one sorting office that hands over a single parcel.

With a far end

Your router sends pieces over the fibre and the 5G to your server, which hands the website one stream from one address.

Without one

Without a far end, the same pieces reach the website from two addresses, and it accepts neither half.

**Fig. 2 · Example** One download, in pieces over two links. The address is an example.

**The limit.** Without a server, separate downloads can still take separate links. Bonding every app, calls included, and keeping what is open through a drop, need the far end.

04 

## Each kind of traffic, its own way

Packet · step 3

A download wants as much as it can get, while a call or a game wants every packet on time. Fenris treats each connection on its own terms: downloads spread across every link, and calls and games keep to the quickest link.

Five connections, three links

**A game update** cdn.example.net

_Spread over every link_

**A video call** meet.example.com

_The quickest link, a copy on a second_

**A match** game.example.net

_The quickest link_

**A live stream, going up** ingest.example.com

_The quickest link, repair data on a second_

**A photo backup** backup.example.com

_Behind the rest, never on the metered phone_

While the call is on, busy links keep a shorter queue, so the call waits less behind the download.

No call is on. The download takes all it can get.

**Fig. 3 · Example** The names are examples. Fenris sorts by what a connection does, not by its app.

**The limit.** The sorting happens on your device. Your server is told the plan, so what comes back follows it; it never inspects your traffic.

05 

## Copies for calls, repairs for video

Packet · steps 3 and 6

A call is a small stream of voice packets, so Fenris sends each one twice, on two links, and the first to arrive wins. That is a copy: a hiccup on one link is covered by the other.

Video is too big to send twice. It gets a little repair data on a second link, from which a lost packet is rebuilt without asking for it again.

A voice call rides the fibre with a copy of every packet on the 5G. A video call rides the fibre with repair data on the 5G.

**Fig. 4** Solid is the call. Short marks are copies; sparse marks are repair data.

[Calls that keep going, and what they cost](https://fenris.network/features/calls)

**The limit.** A copy uses data. On a metered link, copies and repairs stay off unless you allow them, and stop at a daily allowance you set.

06 

## When a link goes quiet

Links rarely just switch off. More often they slow, stall or start losing packets while still looking connected. Fenris checks every link all the time, in both directions.

When one goes quiet with data waiting, its traffic moves to the others. The link rejoins once it carries again, and one that keeps flickering is held back a while.

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. 5 · Example** The words in the lanes are the ones the product’s activity log uses.

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

07 

## A dish with a beat

A Starlink dish changes satellites on a fixed 15-second beat, and at each change its delay can jump for a moment. That is enough to stutter a call.

Fenris finds that beat from the link’s own round trips, never from a label. Calls, games and name lookups then step onto another link just before each jump, and back just after. Both ends learn it.

One minute on a dish and a 5G link 

The dish’s round trip jumps at seconds 12, 27, 42 and 57 of each minute. Once the beat is learned, a call steps onto the 5G around each jump.

At first Fenris only watches. Three beats in a row, and the pattern is known.

The call steps onto the 5G around each jump. A download stays on the dish, and losses inside a jump do not slow it.

**Fig. 6 · Example** The beat is to scale and comes from published measurements of Starlink (arXiv 2310.09242, RIPE Labs). The jumps’ height and the steps’ width are illustrative.

**The limit.** A tree, a sail or a mast in the way causes drops that are not on the beat. Those are handled like any link that goes quiet.

08 

## Links that cost money

Your phone’s data costs money and runs out. Phones and cellular modems are treated as metered by themselves: they help with downloads when the others are busy, get no copies or repairs unless you allow it, and stay quiet when idle.

Give a link a monthly cap and the day its plan renews. Fenris counts everything that crosses the link, through Fenris or not, and at the cap it turns the link off, or keeps a trickle if you choose.

Say the phone’s plan gives a month, and at the cap the link should 

A month on three links. The fibre and the 5G carry all month. The phone is used when the others are busy, until it reaches its cap; then it turns off or keeps a trickle until the plan renews.

**Fig. 7 · Example** Made-up values: a phone that carries about a gigabyte on a busy day. 1 Mbit/s is the setting’s own figure.

**The limit.** The cap is counted by the billing month. For a plan with a daily allowance, set the phone as a backup, used only when nothing else works.

09 

## Wi-Fi that asks you to sign in

Hotel, airport and café Wi-Fi often hold you at a sign-in page before they let anything through. To a router, that looks like a link that is up but carries nothing. That is a captive portal.

Fenris spots it and keeps that link out of the bond. On a router, one device gets through to the sign-in page, for up to 5 minutes, while the other links carry everyone else. Then the link joins.

A hotel room with three links

Hotel Wi-Fi _Held by a captive portal until someone signs in_

Hotel Wi-Fi _Past its captive portal_

5G _In use_

Phone _In use_

**Fig. 8** The sign-in goes straight out through that one link, for that one device. It closes as soon as the link is online.

Some networks block UDP instead. On a link where UDP gets no answer within 3 seconds, that link’s path runs as TLS on TCP 443, still part of the same bonded session, and UDP is tried again every 5 minutes.

**The limit.** Fenris does not hide that it is a tunnel, and it is not built to get around censorship.

10 

## Nothing slips out around it

Packet · step 8

While Fenris is on, nothing from your router or the devices behind it leaves outside the tunnel: not while it connects, not after a crash, not while the router boots. If the tunnel can’t be reached, traffic waits, and the app says so. That is the kill switch.

Your server is where your traffic meets the internet, so websites see its address, not your home’s or your phone’s. It stays the same whichever link carried the traffic, which is what keeps calls and downloads alive through a drop.

The tunnel can’t be reached The tunnel is up

Without a kill switch _Leaves directly, from your home address_

With Fenris _Held back until the tunnel is back_

With Fenris _Through the tunnel, from your server’s address_

**Fig. 9** On wired networks you list, traffic can go direct instead, after 30 seconds without your server. Never on open Wi-Fi.

**The limit.** One address that is yours alone is less anonymous than a shared VPN’s. And some banks and streaming services distrust cloud addresses: such a site can be set to go direct, and then it gets no bonding.

11 

## Sealed to your server

Packet · steps 4 and 5

Everything your devices send is sealed on the device and opened only on your server. The networks in between carry it without being able to read it or change it. The keys are made on your devices and on your server, and no company holds a copy.

Each link’s network carries sealed traffic to your server and can read nothing in it. Past your server, traffic is as protected as the website makes it.

**Fig. 10** TLS 1.3 inside QUIC. The keys are agreed with a post-quantum exchange, X25519MLKEM768, and replaced every 2 minutes or every gigabyte.

[What is encrypted, and how](https://fenris.network/security#encryption)

**The limit.** It is encrypted from your device to your server. Past it, your traffic is as protected as the website makes it.

12 

## What your server sees

Your server has to read where each packet is going, its address and port, to pass it on. It never writes down the sites you visit or the names you look up, and it never looks inside your traffic.

An envelope inside an envelope. The networks in between see only that traffic goes from your link’s address to your server. Your server opens that and reads the website’s address and port. What is inside stays sealed by the website’s own HTTPS.

**Fig. 11** An envelope in an envelope. The address is an example.

What it does keep, it keeps for a stated time: that a device is enrolled, its links, each session in the audit log for a year, the data used each day for about 400 days, and link health for 24 hours, in memory.

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

**The limit.** Whoever hosts your server can see what leaves it, as an internet provider does today. No company sits in the path, but that is not the same as nobody being able to look.

13 

## Two links, one road

Your laptop’s Wi-Fi and its Ethernet cable look like two links. If both go to the same router, they share the one line behind it, so together they add no speed and they fail together.

Bonding helps when links reach the internet by different roads: fibre and 5G, a home line and a phone, two providers in an office.

The same cut, twice

Two links, one road

Wi-Fi _To the router_

Ethernet _To the router_

Wi-Fi _Quiet_

Ethernet _Quiet_

Both ride the same fibre behind the router.

Both go quiet together. Nothing is left.

Two links, two roads

Fibre _To your server_

5G _To your server_

Fibre _Quiet_

5G _Carries on_

They meet only at your server.

The 5G carries on with what was open.

**Fig. 12** Two different Wi-Fi networks, or two providers into one office, are two roads. Where two links share one upstream, Fenris says so.

## In short

1. A device uses one link at a time. Fenris uses every link at once.
2. The pieces meet at a server you run, which talks to the internet as you.
3. A download is spread over every link. A call keeps to the quickest one, with a copy on a second.
4. A link that goes quiet hands its traffic to the others, and rejoins by itself.
5. Metered links wait their turn and stop at your cap.
6. Everything is sealed from your device to your server, and nothing leaves around the tunnel.
7. One link alone is never made faster, and two links behind one router are one line.

[Every capability, in one list](https://fenris.network/features)[Security](https://fenris.network/security)[Questions and answers](https://fenris.network/faq)
