One download over every link.
A single download is split over all your links and put back together at your server. It gets close to what the links carry together, not what one of them does.
Every deviceYour serverOn by default
A load balancer puts each connection on one link. One download gets one link.
Bonding splits the one download over both links, and your server puts it back together.
What happens
- Your device answers the download’s connection itself. To the app it is one ordinary connection, and nothing in the app changes.
- The data becomes one stream that Fenris can split. Pieces go out on every link, more of them on the links that carry more.
- Your server puts the pieces back in order.
- Your server makes the real connection to the site, from its own address. The site sees one sender, whichever links the pieces took.
- What comes back is spread over your links the same way. Your server schedules what it sends with the same care as your device does.
What it costs
The pieces have to meet somewhere, and that is one more stop.
- Speed
- Less than the sum. Say your fibre gives 100 Mbps and your 5G 60: one download gets about 150, not 160. The tunnel takes the rest.Example
- Delay
- Every piece goes by way of your server. Put it near you.
- Data
- A download uses whichever links are up, metered ones too when the others are busy. A role or a cap keeps a metered link out.
- Your server’s plan
- Everything you download leaves your server towards you. Pick a plan whose included transfer covers your month.
Turn it on
It is on from the start. These change how a download is spread.
| To | Command line | Router UI and app |
|---|---|---|
| Let secondary links carry downloads at once | fenris settings --profile max-speed | Rules, Profile, Max speed |
| Keep downloads off one link | fenris link usb0 --downloads no | Links, the link, Edit |
| Hold a link to a download speed | fenris link usb0 --down-limit 20 | Links, the link, Edit |
| Spread video sites that use HTTP/3 | fenris settings --steer-http3 on | Rules, Spreading |
| Put a backup behind everything else | fenris rules add --ports 8443 --class background | Rules, Add rule |
| See each connection, busiest first | fenris flows | Rules, Kinds of traffic |
Where to find it
Router UIRules. Spreading, and how each kind of traffic is handled.
The appSettings, Rules.
The consoleA device’s page. Each link’s share of the bonded total.
The productThree of its own screens, with example data.
What it keeps
Nothing about the download. Your server never records the sites you visit or what is inside your traffic. The bytes are added to that device’s daily total, kept for about 400 days.
Where it stops
- One link
- One link alone can’t be made faster. Splitting needs at least two.
- The far side
- A download is never faster than the site sends it, or than your server’s own line carries it.
- A small processor
- Each piece is sealed on your device. A small router’s processor can set the ceiling before the links do.
- The same road
- Two links behind one router are one line. Splitting a download over them gains nothing.