Kill switch from boot.
While Fenris is on, nothing from your device, or from the devices behind your router, leaves outside the tunnel. Not while it connects, not after a crash, not during an upgrade.
Every deviceOn by default
The tunnel can’t be reachedThe tunnel is up
Without a kill switchLeaves directly, from your home address
With FenrisHeld back until the tunnel is back
With FenrisThrough the tunnel, from your server’s address
What happens
- The block goes up before the network does. On a router or a PC it holds from early boot, before anything can send.
- Only the tunnel to your server is let out. Everything else waits behind it.
- If the tunnel can’t be reached, traffic waits, and the app says so. The tray reads Holding traffic.
- Name lookups are forced into the tunnel. IPv6 goes through it when your server has IPv6, and is refused at once otherwise, so it never leaks.
- A crash or an upgrade leaves the block in place. It comes down only when you turn Fenris off.
What it costs
No tunnel, no internet, until it is back.
- While your server is away
- Traffic waits. Nothing loads until your server answers, a second server takes over, or you turn Fenris off.
- One address
- Websites see your server’s address for everything. Some banks and streaming services distrust addresses that belong to a hosting provider.
- Going direct
- A site you set to go direct leaves outside the tunnel. It gets no bonding, and the network it leaves by can see it.
- Sign-in pages
- A hotel’s sign-in page can’t load through the block. One device is let through to it, for up to 5 minutes.
Turn it on
It is on from the start. These open it where you choose.
| To | Command line | Router UI and app |
|---|---|---|
| Turn the kill switch off | fenris settings --kill-switch off | Settings, When Fenris can’t connect |
| Let chosen sites go direct | fenris settings --direct-domains bank.example | Settings, Direct, outside the tunnel |
| Let a device at home go direct | fenris settings --direct-devices 192.168.1.40 | Settings, Direct, outside the tunnel |
| Go direct while only one link works | fenris settings --direct-when-alone on | Settings, Direct, outside the tunnel |
| Turn the tunnel off for now | fenris disconnect | Home, the switch |
| Check each step to your server | fenris check | Diagnostics |
Where to find it
Router UIHome. Protected, and through which server.
The appHome. On Android, the kill switch is the system’s own always-on VPN setting.
The trayConnected, Connecting, Holding traffic or Off.
The productThree of its own screens, with example data.
What it keeps
Nothing. The kill switch is a rule on your device. It records nothing and sends nothing.
Where it stops
- When Fenris is off
- Turn Fenris off and traffic leaves directly, as it did before. The app warns you when you do.
- Networks you trust
- On wired networks you list, traffic goes direct after 30 seconds without your server. Never on open Wi-Fi.
- Past your server
- It keeps traffic inside the tunnel. Past your server, traffic is as protected as the website makes it.
- On Android
- The kill switch there is Android’s always-on VPN setting, with “Block connections without VPN”. The app shows you where it is.