Skip to the page
FenrisEarly access

A console that shows each link.

Every device by name, its links side by side under the bonded total, alerts that name the missing link, and a record of who did what. It runs on your server, and only your devices reach it.

The consoleYour server

One device’s links, side by side

An alert names the link that is missing: the phone.

One link is all this device has. Nothing is bonded, and the tunnel still protects it.

The van has been offline longer than 5 minutes, so an alert is open.

Fig. 1 · ExampleThe same example devices as in the screens below.

What happens

  1. Each device tells your server its links as it connects. Their names, their kind, and how each is doing.
  2. The console lists every device by name. What it runs, where it connects from, and how many of its usual links are up.
  3. A device’s page draws its links side by side, under the bonded total. Second by second, and over the last day or week.
  4. An alert is raised when a device stays offline, or runs short of its usual links. It names the link that is missing, and goes out by webhook or email.
  5. Everything done in the console is written to the audit log. What happened, who did it, from which address, and what changed.

What it costs

To show it, your server has to keep it.

What it keeps
Each device’s links, a day of link health in memory, a year of sessions and about 400 days of daily usage. All of it stays on your server.
Reach
The console listens only on your server and through the tunnel. To open it you need a device that has joined, or SSH to the server.
A door to guard
Whoever signs in can revoke devices and forward ports. Sign-in is by passkey or authenticator code, and five wrong codes pause it for 15 minutes.

Turn it on

It comes with your server. On a device that has joined, open your server’s name, or https://10.77.0.1/admin.

ToCommand lineThe console
Make an adminfenris-server admin create --state /var/lib/fenris-server --name <name>Access, Admins
Make a read-only token for a scriptfenris-server token create --state /var/lib/fenris-server --name <name> --tier readAccess, API tokens
List every devicefenris-server devices --state /var/lib/fenris-serverDevices
Add a devicefenris-server invite --state /var/lib/fenris-server --address <public IP>:443Add a device
Cut a device offfenris-server revoke --state /var/lib/fenris-server --device <id>Devices, the device

Where to find it

The consoleDevices. Every device by name, with its links, its throughput and its version.

On a phoneAlerts. The missing link is named.

The consoleAudit log. What happened, who did it, and from where.

The productThree of its own screens, with example data.

What it keeps

The console shows what your server keeps, and adds a record of its own: sign-ins and changes, with the admin and the address they came from, for a year.

Where it stops

Not from the internet
The console is never open to the internet. Without a device that has joined, reach it through SSH.
What it can’t show
It shows how much each device used, never which sites or apps. Your server does not know them.
Passkeys
A passkey needs your server to have a name of its own. Without one, sign in with an authenticator code.
Alerts
An alert reaches you by webhook or email only while your server itself is up.