Works on awkward networks.
Hotel Wi-Fi that holds you at a sign-in page, and networks that block UDP. Fenris spots both, and gets each link through in the way that link allows.
Every deviceYour serverOn by default
A hotel room with three links
Hotel Wi-FiHeld by a captive portal until someone signs in
Hotel Wi-FiPast its captive portal
5GIn use
PhoneIn use
What happens
- A link that is up but stuck at a sign-in page is behind a captive portal. Fenris spots it and keeps that link out of the bond.
- On a router, one device gets through to the sign-in page. For up to 5 minutes, or until the link is online, that device’s lookups and new connections leave by that link.
- Meanwhile the other links carry everyone else. Once someone has signed in, the link joins.
- Where UDP gets no answer within 3 seconds, that link’s path runs as TLS on TCP 443. It is still part of the same bonded session, and UDP is tried again every 5 minutes.
- Give your server a name, and it gets and renews its own certificate. Anyone who connects without a device’s proof sees an ordinary website you choose.
What it costs
Getting through costs one small opening, and some speed.
- The sign-in
- For those few minutes, one device’s traffic leaves by that one link, outside the tunnel and in view of that network. It closes as soon as the link is online.
- Speed
- A path on TCP is slower and less even than one on UDP, more so on a link that loses packets. That is why UDP is tried again every 5 minutes.
- Being seen
- On TCP 443 your server completes a TLS handshake, so that port answers a scan. With a name, the name is public in certificate logs.
Turn it on
Both are on from the start. These take charge by hand.
| To | Command line | Router UI and app |
|---|---|---|
| Let one device sign in through a held link | fenris sign-in wlan0 --device 192.168.1.20 | Links, the link |
| Close the pass-through early | fenris sign-in wlan0 --close | Links, the link |
| Keep every link on TCP | fenris settings --transport tcp | Settings, Transport |
| Go back to trying UDP first | fenris settings --transport auto | Settings, Transport |
| Take TCP paths on your server | --tcp-fallback | Added to your server’s install command |
| Give your server a name and a website | --domain vpn.example.com --decoy-dir <directory> | Added to your server’s install command |
Where to find it
Router UIHome. Each link, and whether it is in the bond.
The appHome.
The trayOn a PC. Each link at a glance.
The productThree of its own screens, with example data.
What it keeps
Nothing about the sign-in: it goes straight out through that link, and your server never sees it. Each session is in the audit log for a year, as any other is.
Where it stops
- Not a disguise
- Fenris does not hide that it is a tunnel, and it is not built to get around censorship.
- Sign-in pages
- The pass-through is for routers and computers. A phone signs in to Wi-Fi the way it always has.
- Your server’s side
- A device can use TCP 443 only if your server takes it. That is set when the server is installed.
- A network that blocks both
- Where neither UDP nor TCP 443 reaches your server, that link stays out of the bond. The others carry on.