Skip to the page
FenrisEarly access

Bond a Linux router

Last updated 17 Nov 2026Applies to 0.1

Fenris turns a Linux machine with two or more internet links, such as a Raspberry Pi with Ethernet, Wi-Fi and a tethered phone, into a router that bonds them into one tunnel to your server, for itself and the devices on its LAN.

What it needs

  • Linux 5.15 or newer with systemd and nftables, on aarch64 or x86_64: Raspberry Pi OS, Debian or Ubuntu.
  • Two or more links with a default route each, IPv4 or, on a link that has no IPv4 (some cellular modems and fibre lines), IPv6. Fenris finds them, and follows them as they come and go.
  • A LAN interface for the devices behind it (or none, to bond only the machine’s own traffic).
  • A Fenris server and a one-time invite link from it (see Run a Fenris server).

Install

curl -fsSLO https://releases.fenris.network/<version>/install.sh
sudo sh install.sh --client --from https://releases.fenris.network/<version>/ \
  --join '<invite link>' --lan eth1

--lan names the LAN interfaces (eth1,wlan1 for two). Add --ui <LAN address>:8484 for the router’s web page.

The installer checks every file against Fenris’s release keys, installs the client, joins your server with the link (the router makes its own keys, which never leave it), and starts it. Its settings are in /etc/fenris/client.toml.

Use it

fenris status                     # the tunnel and each link
fenris top                        # the same, live
fenris link usb0 --role backup    # use a link only when the others fail
fenris link usb0 --metered yes --cap 20000   # a phone: count it, stop at 20 GB
fenris mode redundant             # every packet on every good link
fenris disconnect                 # turn the tunnel off

While the tunnel is on, nothing from the LAN or the router leaves outside it, also while connecting, after a crash and from boot, until fenris disconnect.

The web page, if you turned it on, is at https://<LAN address>:8484. Check the certificate fingerprint fenris ui prints against the browser’s, and sign in with a token from sudo fenris ui token create --tier connect --name <who> (tiers: read, connect, settings).

Updates

The router updates itself from your server: when the server holds a newer release, the router fetches it through the tunnel, installs it once the network is quiet, and goes back to the version before if the new one cannot reach the server. updates = "notify" or "off" in /etc/fenris/client.toml changes that; fenris status says what updating is doing.

When something is wrong

fenris check checks each step to the server and says what to do about the one that fails. fenris diagnostics writes one file with the router’s account of itself, its addresses and names replaced, to look at or send for help. If the client cannot run, sudo fenris-client uninstall removes its rules so traffic flows directly.