23 Feb
2019
23 Feb
'19
11:38 a.m.
Regarding this topic, I have a "technical" proposal on it.
Wouldn't it make sense to advertise the BGP subnets in the RIP
broadcasts, too?
In light of the fact that the ampr gw forwards these routes anyway, if
those subnets would appear as 44.x.y.z/n via 169.228.34.84 (the ampr
gw) (and most gateways feature a default route to the ampr gw anyway),
then all current setups would work without any change.
This would also allow to easily find out all BGP routed networks using a
simple filter on the route list.
Announcing them with a routing distance of 16 (infinity) in the RIP
would also make sense since Ampr-ripd and Amprd ignores those routes.
Marius, YO2LOJ
On 23.02.2019 07:12, Steve L via 44Net wrote:
From time to time testing various setups I need to
determine if the
remote 44 host is IPIP or BGP so that I can verify everything is
working etc.
I used to grep this, but apparently this is not current?
http://thyme.rand.apnic.net/current/data-add-ARIN
Does anyone know of an up to date source?
I used to test new installs against hambook.de.ampr.org
(44.225.164.16) as I know this is not reachable via the normal
internet, but is via 44net. It used to be via an IPIP tunnel. I
don't see it in my routes, so it must be via BGP now, but I don't see
it from the above source.
Thanks
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net