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.
The downloadYour laptop asks a site for a large file. To the laptop it is one ordinary TCP connection.
The callYour call app sends a voice packet over UDP: small, and due on time.
The downloadOn the router, Fenris answers that connection itself, so the file becomes one stream it can spread.
The callThe packet is known as a call from its own marks, and sorted under calls and live video.
The downloadThis piece goes out on wan, the fibre. The next may go on wwan0, the 5G.
The callIt goes on the quickest link, wan. A copy goes on wwan0.
The downloadEach piece is sealed on the router, with keys only your server shares.
The callThe packet and its copy are sealed the same way.
The downloadYour fibre provider carries sealed traffic to 203.0.113.7, your server. It can read nothing else.
The callThe mobile network carries the copy, and sees the same.
The downloadPieces arrive from every link, on UDP 443, and only your server can open them.
The callThe first copy to arrive is used. The other is dropped.
The downloadThe pieces are put back in order, into the one stream the laptop started.
The callThe voice packet is passed on at once.
The downloadYour server makes the real connection to the site, from its own address.
The callThe call service sees your server’s address too, whichever link carried the packet.
The downloadThe file comes back the same way. Your server spreads it over your links, by the same plan.
The callThe other side’s voice returns on the quickest link, with a copy on a second.
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.
The limit. Bonding cannot make one link faster. With a single link, Fenris is an encrypted tunnel to your server and nothing more.
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 limit. If every link drops at once, the session is lost. It comes back on every link as soon as one returns.
The pieces have to meet somewhere
Packet · steps 6 to 8A 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
Without one
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.
Each kind of traffic, its own way
Packet · step 3A 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.
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.
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.
Copies for calls, repairs for video
Packet · steps 3 and 6A 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Nothing slips out around it
Packet · step 8While 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 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.
Sealed to your server
Packet · steps 4 and 5Everything 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.
The limit. It is encrypted from your device to your server. Past it, your traffic is as protected as the website makes it.
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.
What the networks in between seefrom your link’s address → to 203.0.113.7, your server
What only your server opensto the website’s address and port
What stays sealed past itthe page itself, where the site uses HTTPS
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.
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.
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.
Two links, one road
Both ride the same fibre behind the router.
Both go quiet together. Nothing is left.
Two links, two roads
They meet only at your server.
The 5G carries on with what was open.
In short
- A device uses one link at a time. Fenris uses every link at once.
- The pieces meet at a server you run, which talks to the internet as you.
- A download is spread over every link. A call keeps to the quickest one, with a copy on a second.
- A link that goes quiet hands its traffic to the others, and rejoins by itself.
- Metered links wait their turn and stop at your cap.
- Everything is sealed from your device to your server, and nothing leaves around the tunnel.
- One link alone is never made faster, and two links behind one router are one line.