3 Feb
2017
3 Feb
'17
5:08 a.m.
(Please trim inclusions from previous messages)
_______________________________________________
Gateway 44.130.120.65 (Implementation Test YO2LOJ) is advertising for
network 44.130.120.0/24, which covers itself. That's not good, right?
I can't route to this network because it causes a routing loop when
tunneling.
-J
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
That's a test setup to see if we could actually do it :-)
The idea is to have a BGP announced subnet with a IPIP endpoint inside
that subnet, so that tunnel users could connect.
This issue was raised by the fact that there are situations when a IPv4
address is not available except the 44net space (e.g. IPv6 only nets).
The basic idea is to create a route for the tunnel endpoint via the
default gateway (44.130.120.65 via default in this case), and use that
tunnel for the rest of the subnet.
I already updated the Mikrotik script to support this.
Ampr-ripd is next (the current version will silently ignore this subnet).
Apart of the existence of that subnet, there are no services available, so
pleas just ignore it :-)
Marius, YO2LOJ