Use cases/Travel
Hotel Wi-Fi and your phone, as one.
Hotel and airport Wi-Fi comes with a sign-in page, a crowd, and sometimes a block on anything but web pages. Fenris on your laptop uses it together with your phone, and keeps it out of the way until it works.
The links you probably have
- The Wi-Fiused all the time
- Your phoneused when the others are busy
The words on the right are the roles Fenris gives a link. You choose them.
One day, as it plays out.
A work trip with a laptop, and a phone on a USB cable: a conference hall in the morning, the hotel from midday. Two things go wrong today.
The Wi-Fi in the conference hall lets web pages through and blocks most other traffic.
Most tunnels can’t connect here at all. You work without one, on a network anyone in the hall can join.
On that link Fenris runs as TLS on TCP 443 instead, still part of the same connection, with the phone beside it.
- Wi-Fiused all the time
- Phoneused when the others are busy
You check in and open the laptop for a call. The hotel Wi-Fi holds every page until someone signs in, and you get to that when the calls are done.
The laptop shows a full Wi-Fi signal and loads nothing. The call starts late, from the phone in your hand.
The Wi-Fi is found to be behind a sign-in page and kept out of the bond, and the phone carries the call. You sign in afterwards, and the Wi-Fi joins.
- 12:40Wi-Fi is held by a captive portal until someone signs in.
- 15:30Wi-Fi is past its captive portal.
Every room is watching something, and the hotel Wi-Fi drops for three quarters of an hour.
The film stops, and the day’s files start to upload again from the beginning.
The phone was already part of the connection, so both carry on over it, more slowly. The Wi-Fi rejoins by itself.
- 21:30Wi-Fi went quiet. The other links carried its traffic.
- 22:15Wi-Fi carries traffic again.
What Fenris does here
Each is a feature with its own page, where it says what it costs.
- Works on awkward networks
- Wi-Fi stuck at a sign-in page is found and kept out of the bond until someone signs in. A link whose UDP gets no answer in 3 seconds runs as TLS on TCP 443 instead.
- Link roles
- A phone is treated as metered by itself: it joins only when the others are busy, and stays quiet when idle.
- A link drops, the others carry it
- When the Wi-Fi goes quiet its traffic moves to the phone, and it rejoins by itself when it returns.
- Kill switch from boot
- While Fenris is on, nothing leaves outside the tunnel: not while it connects, and not after a crash.
- No company in the middle
- Your traffic goes to a server you own, not to a VPN company’s.
What you need
- On the laptop
- The Fenris app for Windows, a Mac or Linux, with the Wi-Fi and your phone on a USB cable as its two links.
- A server
- A small Linux server near where you usually are. Websites see its address wherever you travel.
- Data on the phone
- A plan with room for the hours the Wi-Fi fails. Set the phone as a backup, and it is used only then.
Where it stops
- The Wi-Fi is all you have.With one link, Fenris is an encrypted tunnel to your server and nothing more. One link can’t be made faster.
- Your server is far away.Your traffic goes home first. From another continent that is delay bonding can’t remove.
- A site distrusts your server.Some banks and streaming services distrust addresses that belong to a hosting provider. Set such a site to go direct, outside the tunnel. It then gets no bonding.
- The phone’s data runs out.Fenris counts a link against a monthly cap, and at the cap it turns off.
Try it on your own links
Tell us which links you have, and we’ll write when a build for your links is ready. Free during early access.