It's not about bending anything to anything.
The main issue is to separate regular users from a backbone infrastructure. What is done in the infrastructure and how it is interconnected is not important to the end user. It can be mesh, direct routing, whatever. But the user needs to be able to connect his subnet to the backbone via a (local) point of presence (POP) using a easy to use way, a way that is supported by regular, or at least some commercial routers out of the box or regular operating systems, without scripts and custom code running on them.
There are a lot of tunneling protocols supporting P2P connections, starting with the classic IPIP, GRE, PPTP, L2TP and now IPSEC, SSTP and others, even 4in6 since the time has come...
From my point of view, It should be the choice of the operator of the POP to decide what user access protocol they choose. For example L2TP is still supported on many devices and is a good candidate, and even the old PPTP will do.
There is no need to find a single universal solution for everything. If the backbone works (and the current mesh could be the base of this backbone, with simple users just opting out as other connection options become available).
Greetings, Marius, YO2LOJ
On 29.12.2020 12:35, Pierre Emeriaud via 44Net wrote:
Hi Chris
Le mar. 29 déc. 2020 à 10:56, G1FEF via 44Net 44net@mailman.ampr.org a écrit :
This is exactly the sort of thing we would like to have the TAC get together for. Why don’t any interested parties email me and maybe we can finally get this going. If we’re going to do this properly it will needs some structure and the extra noise it will generate should be moved to a separate list.
I'd like to be part of this too.
I'm a bit frustrated by the current situation with rip or static mappings. what would be nice if we found a way to bend BGP to our needs and set up some redundant route-servers to replace rip, or just a plain bgp mesh overlay a la dn42.
-- 73 de f4inu
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net