26 Aug
2021
26 Aug
'21
4:28 a.m.
On 26/08/2021 11:10, Chris Smith via 44Net wrote:
Actually, this broke thing since people insisted to use one of the
subnet's address as the GW. Using an extra public IP for the gateway
itself works flawless.
Also another issue is the default tunneling of not-announced IPs (all
the 44 space) by default via AMPR-GW which has become standard practice,
but breaks things.
Anyway, the current rip daemons and scripts support this type of
operation, too (but it seems to be buggy since it was never extensively
long term tested).
At the moment there is 5 systems configured like that:
44.94.17.128/27
and 44.130.104.0/24, 44.130.105.0/24, 44.130.106.0/24, 44.130.107.0/24
I don't know about the first one, but the last four are the system used
for testing the daemons and script and are not active anymore (it worked
as expected at that time).
73's! Marius, YO2LOJ
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!