That sort of thing can be accomplished with routing protocols like BGP, of course.
Along these lines, I might be interested in participating in a 44net network built to use
a routed topology. Maybe it’s something like, we use iBGP among ourselves, and those with
access to PoPs (like via Vultr etc), can manage access to the public internet on our
behalf.
Someday maybe anyway
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: John D. Hays via 44net <44net(a)mailman.ampr.org>
Sent: Thursday, May 26, 2022 6:02:34 PM
To: Rob PE1CHL <44net(a)pe1chl.nl>
Cc: 44net(a)mailman.ampr.org <44net(a)mailman.ampr.org>
Subject: [44net] Re: 44Net Assessment Kickoff - Survey!
Another approach would be auto-failover between PoPs in client routers.
On Thu, May 26, 2022 at 10:59 AM Rob PE1CHL via 44net
<44net@mailman.ampr.org<mailto:44net@mailman.ampr.org>> wrote:
Yes, that is also part of my design. An entry-level user can connect to a single PoP and
get "their subnet" routed to them, and route all other Net44 space towards that
PoP. Simple, static routing.
A more advanced user can make multiple PoP connections and use BGP to send and receive
individual subnet routes, and let their local router decide to which of the PoPs to send
each packet. That would also cover the case where a PoP is down and all traffic is routed
via the remaining one(s).
These users can also have cross-connections to other users (via radio or direct tunnels)
and the routing remains correct.
--
John D. Hays
Kingston, WA
K7VE / WRJT-215