Bond a router running OpenWrt
Fenris on an OpenWrt router bonds every WAN it has up (fibre, cable, a USB modem or tethered phone, a second Wi-Fi network) into one tunnel to your server, for every device on the LAN.
What it needs
- OpenWrt 25.12 or newer (the releases that use
apk), on anaarch64orx86_64router. - Two or more WANs set up in OpenWrt, each with its own default route.
- A Fenris server and a one-time invite link from it (see Run a Fenris server).
Install
On the router, find its architecture:
cat /etc/apk/arch
From the release (https://releases.fenris.network/<version>/), fetch
fenris-<version>-r1-<architecture>.apk and, for the web page in LuCI,
luci-app-fenris-<version>-r1.apk, then:
apk add --allow-untrusted ./fenris-<version>-r1-<architecture>.apk ./luci-app-fenris-<version>-r1.apk fenris-client join --state /etc/fenris/state '<invite link>' /etc/init.d/fenris start
--allow-untrusted because Fenris packages carry Fenris’s own signatures
rather than an OpenWrt feed’s: the first install trusts the HTTPS download,
and every update after it is checked against Fenris’s release keys before it
is installed.
The package puts its settings in /etc/fenris/client.toml with br-lan as
the LAN, adds a firewall zone for the tunnel, holds the kill switch from early
boot and keeps /etc/fenris through a sysupgrade.
Use it
LuCI’s Services → Fenris shows whether the tunnel carries traffic and why not, each WAN by its OpenWrt name with its delay, speed and data this period, how each is used (always, when the others are busy, only if they fail, never), the mode, and an on/off switch. From a shell:
fenris status # the tunnel and each link fenris top # the same, live fenris link eth1 --role backup # use a WAN (its interface, as fenris status lists it) only when the others fail fenris disconnect # turn the tunnel off; traffic leaves directly
While the tunnel is on, nothing from the LAN or the router leaves outside it,
also while connecting and after a crash, until fenris disconnect.
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.
Remove it
apk del fenris luci-app-fenris removes it and lifts the kill switch.
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.