Re: [44net] 44 Network behind BGPed 44 Address

44.24.221.1 is not announced in the RIP broadcast, so it goes implicitely to default (and NATed to the local public IP) if the system is correctly configured.

In this case the tunnel endpoints are correctly defined, and 44.24.240/24 is sent via IPIP from the local public IP to 44.24.221.1, which, being BGP annonced, is directly reachable on regular internet. The only condition for this to work is NOT to have a default route to 44.0.0.0/8 via tunnel. The problem with 44.140 is that the gateway is in its own subnet. So we need to instate a higher priroity route for the gateway, to avoid the tunnel, on the local system or on a potential connected router which gets RIP forwarding. And we need a way to differentiate between a misconfigured situation and a legitimate setup. That is why I proposed the GW 0.0.0.0 approach, meaning no gateway. This will solve the local routing issue on the gateway, but will not work on RIP forwarding, and a manual intervention is still required on any connected router. Because receiving the RIP route for the gateway will cause a routing loop, dropping it will also create another routing loop, since standard RIP sets the gateway for a route to the interface on which it received the routing info. But it could be a first step. Or just drop the route alltogether, and rely on the fact that the whole subnet is BGP announced, as it happens on ampr-ripd 1.13. This leads to a correct working setup, the only limitation being that the destination system can not differentiate between ampr/non-ampr traffic, since NAT to a public IP is needed. I think modifying ampr-gw to accept forwarding to such host is out of the question, since it would increase the load on that system. If acceptable, the default route via tunnel for 44.0.0.0/8 destinations would cover this situation, provided that ampr-gw accepts forwarding to BGPed 44net destinations.. Marius, YO2LOJ -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Jann Traschewski Sent: Saturday, January 10, 2015 11:17 To: AMPRNet working group Subject: Re: [44net] 44 Network behind BGPed 44 Address ( ... Good idea! There is a another gateway which could be fixed this way: 44.24.221.1/32 via 0.0.0.0 44.24.240.0/20 via 44.24.221.1 Currently I need to setup this type of gateway manually on my system... ... 73, Jann _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net