Use cases/Shops and small offices
Both lines working, every day.
Most shops and offices already pay for a second line that does nothing until the first one dies. Fenris uses both all day. When one fails, the calls and the screens people had open carry on over the other.
The links you probably have
- The first lineused all the time
- The second lineused all the time
- A 4G donglea backup, used only when nothing else works
The words on the right are the roles Fenris gives a link. You choose them.
One day, as it plays out.
A pharmacy with a small office behind it: two broadband lines from different operators, and a 4G dongle. A billing computer, a card machine on the shop’s Wi-Fi, and calls to suppliers. Two things go wrong today.
The shop opens. Last night’s accounts are still on their way up to the cloud.
Everything rides the first line. The second, paid for every month, carries nothing.
Both lines carry traffic all day. The upload is spread over the two, and a call to a supplier goes on the quickest.
- Line 1used all the time
- Line 2used all the time
- 4Ga backup, used only when nothing else works
Road work cuts the first line in the middle of the morning rush. It stays out for nearly three hours.
A failover router waits to be sure, then switches. Calls drop, the billing screen signs out, and the queue at the counter waits.
Both lines were already carrying traffic, so everything behind the router carries on over the second. The outside world only ever saw your server’s address, so nothing signs out.
- 11:20Line 1 went quiet. The other links carried its traffic.
- 14:10Line 1 carries traffic again.
The second line goes quiet for three quarters of an hour, while the day’s accounts are sent.
Nobody notices, because it was idle. You find out on the day the first line fails.
The first line carries everything. If a line stays missing, the console raises an alert that names it, by email or webhook.
- 19:40Line 2 went quiet. The other links carried its traffic.
- 20:25Line 2 carries traffic again.
What Fenris does here
Each is a feature with its own page, where it says what it costs.
- Every link at once
- Both lines carry traffic every day, as one connection to your server.
- A link drops, the others carry it
- When a line goes quiet its traffic moves to the other, and open connections carry on.
- Calls that keep going
- A call’s packets also go out on the second line, and whichever arrives first is used.
- The whole home from one router
- Fenris runs on the router, so every computer and card machine behind it is covered with nothing to install.
- A console that shows each link
- Each device’s links side by side, and an alert that names a missing line.
- A way in from outside
- Open a port on your server to the camera recorder in the shop. It sees each caller’s own address.
What you need
- At the shop
- A router running OpenWrt or Linux, with both lines plugged in. Everything behind it is covered.
- A server
- A small Linux server in a cloud region near you, or a machine on your premises with a public address.
- Someone to run it
- A server is one more thing to look after. Whoever looks after the shop’s computers can, with the guide.
Where it stops
- The customer’s phone is theirs.In a UPI payment the customer’s phone pays over its own network. Fenris keeps the shop’s side online, and a soundbox with its own SIM never used the shop’s network.
- A site distrusts your server.Some bank and government sites distrust addresses that belong to a hosting provider. Set such a site to go direct, outside the tunnel. It then gets no bonding.
- Both lines share one road.Two lines in the same duct are cut by the same digger. Pick operators whose cables come in by different roads, or keep the 4G.
- Your server stops.List a second server, and devices move to it once the first has not answered for 10 seconds. Open connections end at the change.
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.