On 26 Aug 2021, at 09:03, Rob PE1CHL via 44Net 44net@mailman.ampr.org wrote:
On 8/26/21 9:42 AM, Chris Smith via 44Net wrote:
On 26 Aug 2021, at 08:35, Rob PE1CHL via 44Net 44net@mailman.ampr.org wrote:
On 8/26/21 9:33 AM, Chris Smith via 44Net wrote:
Announcing a prefix yourself and joining the IPIP mesh are mutually exclusive.
Can you explain?
I mean that members either request a /24 (or larger) and announce it via BGP for their project, or they (typically) request a smaller prefix and join the IPIP mesh / AMPRNet.
Chris
But you can have a /24 or larger subnet announced on BGP and have the same subnet on the IPIP mesh as well. In fact this improves connectivity for hosts within AMPRnet that are not routing towards internet or do so with limitations (e.g. NAT).
This has been tried, but the routing setup gets very complicated and it is easy to get it wrong, a way back Brian got me to put code in the portal that disallows this after a few occasions when folk tried to do this and used their BGP announced 44 address as the IPIP gateway IP - it broke things badly!
When the IPIP mesh has been replaced with the new backbone, it would be the default situation to be on that backbone network and have that announce your subnet on BGP, as I see it. So it would still mean you can route from/towards internet via your BGP announcement, and towards other AMPRnet users via the backbone.
Yes, I agree. With a better replacement for the IPIP mesh that the backbone/POP system will bring, this will be possible and even preferred.
Chris
Rob _________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net