# Fenris, on what you have.

Put it on the router and the whole home or office is bonded. Or put it on a device and that device bonds its own links. Either way it joins a server you run, with a one-time link.

## For a router

Every link the router has is bonded, for every device behind it. The kill switch holds from early boot.

**OpenWrt**

25.12 or newer, on aarch64 or x86\_64. A package, with a page in LuCI.

**Or Linux**

5.15 or newer with systemd and nftables, such as a Raspberry Pi.

**Links**

Two or more, each with its own default route.

On OpenWrt, add the package, then join

fenris-client join --state /etc/fenris/state '<invite link>'

On a Linux box, one command

curl -fsSL https://dl.fenris.network/get.sh | sh -s -- '<invite link>'

[Bond a router running OpenWrt](https://fenris.network/docs/router-openwrt)[Bond a Linux router](https://fenris.network/docs/router-linux)[Will my router work?](#routers)

## For Android

Wi-Fi and mobile data bonded at once. Join by scanning the QR code your server shows.

**Android**

10 or newer.

**Kill switch**

Android’s own always-on VPN setting.

Get the app

[Google Play](#play)[F-Droid](#fdroid)[The file, from your server](#apk)

From a store, the store updates it. From your server, your server does.

## For Windows

A service and a tray. The PC’s own links are bonded, and it can share the tunnel through its Mobile Hotspot.

**Windows**

10 or 11, 64-bit.

**Kill switch**

From boot, before you sign in.

Get the app

[The installer](#win)[winget](#winget)

It updates through your server, at a quiet moment.

## For a Mac

Wi-Fi with an iPhone over USB or its hotspot, bonded. As an app, or from the command line.

**Kill switch**

From boot. Connect and disconnect without a password.

The command line, in Terminal

curl -fsSL https://dl.fenris.network/get.sh | sh

[The app](#mac)[Homebrew](#brew)

## For a Linux PC

Ethernet, Wi-Fi and a tethered phone, bonded. An app, a tray and the fenris command.

**Desktop**

Ubuntu 22.04, Debian 12 or Fedora, and newer, with systemd.

**Processor**

x86\_64 or aarch64.

Debian and Ubuntu

sudo apt install ./fenris-desktop_amd64.deb

Fedora

sudo dnf install ./fenris-desktop.x86_64.rpm

[Bond a Linux PC](https://fenris.network/docs/desktop-linux)

## For your server

The far end of every link, and yours alone. It also holds the console, and the release your devices update from.

**System**

Linux 5.15 or newer, with systemd and nftables.

**Network**

A public address, with UDP 443 open.

One command

curl -fsSL https://dl.fenris.network/get.sh | sh -s -- --address <public IP>:443 --admin <your name>

[What size of server?](#server)[Run a Fenris server](https://fenris.network/docs/server)

Every release is signed. The installer checks each file against keys built into it before anything runs.

[Check a download yourself](https://fenris.network/security#verify)

## Every platform, and what it needs

| Platform        | Needs                                                                          | Installs as                                      | Updates from              |
| --------------- | ------------------------------------------------------------------------------ | ------------------------------------------------ | ------------------------- |
| Router, OpenWrt | OpenWrt 25.12 or newer, on aarch64 or x86\_64\. Two or more WANs.              | A package, with a LuCI page                      | Your server               |
| Router, Linux   | Linux 5.15 or newer with systemd and nftables, on aarch64 or x86\_64.          | One command                                      | Your server               |
| Android         | Android 10 or newer.                                                           | An app, from Google Play, F-Droid or your server | The store, or your server |
| Windows         | Windows 10 or 11, 64-bit.                                                      | An installer, or winget                          | Your server               |
| Mac             | A second link, such as an iPhone over USB.                                     | An app, one line in Terminal, or Homebrew        | Your server, or Homebrew  |
| Linux           | Ubuntu 22.04, Debian 12 or Fedora, and newer. x86\_64 or aarch64.              | A deb or rpm package                             | Your package manager      |
| Server          | Linux 5.15 or newer with systemd and nftables. A public address, UDP 443 open. | One command, or a container image                | A release you fetch       |

**On the router** Its own page, on your LAN.

The router’s own page, Home, with example data: connected, two of three links up, the speed over both as one, and each link with its share.

**On Android** The app.

The Android app’s Home screen, with example data: protected, two links up, and each link’s share of the traffic.

**On a PC** The tray.

The tray on a PC, with example data: connected through one server over three links, and each link’s round trip and share.

**The product** Three of its own screens, with example data.

## Will my router work?

Pick what you have. Some answers are no, and say why.

1. **Yes.**  
OpenWrt 25.12 or newer, on a 64-bit ARM or x86 router.  
With the OpenWrt package. Every WAN you have set up is bonded, and settings survive a sysupgrade. To see the chip, run cat /etc/apk/arch on the router.
2. **Upgrade first.**  
An OpenWrt older than 25.12.  
Fenris needs the releases that use apk. Upgrade OpenWrt first, if your router’s chip is 64-bit ARM or x86.
3. **Yes.**  
A Raspberry Pi, a mini PC, any 64-bit Linux box.  
As a Linux router: Linux 5.15 or newer with systemd and nftables. It bonds every interface that has a default route, for the LAN behind it.
4. **No.**  
A router with a MIPS or 32-bit ARM chip.  
Fenris is built for 64-bit ARM and x86\. Keep that router for its Wi-Fi, and put a supported one between it and your links.
5. **Keep it.**  
The box your provider gave you, locked.  
It can’t run Fenris, and it doesn’t need to. Plug it into a Fenris router, and it becomes one of that router’s links.
6. **No need.**  
No router of your own.  
Run Fenris on the device itself. A laptop on Wi-Fi with a tethered phone, or an Android phone on Wi-Fi and mobile data, bonds its own links.

## Run your server

Bonding needs a far end, and it is yours. It is like setting up any small cloud server: make a machine, open a port, run the installer.

If you have never used SSH, follow the guide, or ask a friend who has.

[Run a Fenris server](https://fenris.network/docs/server)

It is for 

It runs on 

**Processor and memory**

1 vCPU and 1 GB of memory are enough. Start from 1 vCPU and 1 GB. The console’s Server page shows the processor, memory and disk, and an alert tells you when they run short. Start from 1 vCPU and 1 GB, and grow by what the console’s Server page shows. An alert tells you when the processor or disk runs short.

**System**

Linux 5.15 or newer, with systemd and nftables. Ubuntu 24.04 is a good choice.

**Network**

A public IPv4 address with UDP 443 open to everyone, and TCP 443 for devices on networks that block UDP. IPv6 too, if you can. A public address of its own, with UDP 443 open. Behind a provider’s shared address it can’t be reached. And if its line is the one that drops, your server drops with it.

**Data**

Everything you download leaves your server towards you. Pick a plan whose included transfer covers your whole month. Your whole month’s traffic crosses its line, in and out. Give it a line without a tight cap.

**Place**

The region nearest you. For most of India, that is Mumbai or Hyderabad. The region nearest the office. The region nearest most of your devices. Wherever it has power and a steady line. Every device’s traffic goes there first.

**A backup**

List a second server. Devices move to it once the first hasn’t answered for 10 seconds, and back when it answers again.

**A backup**

List a second server. Devices move to it once the first hasn’t answered for 10 seconds, and back when it answers again.

These are minimums, not capacities. No prices here: they change, and the choice of provider is yours.
