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

This will break RIP forwarding to other routers, but is manageable. But what I don't get is the following: Why isn't 44.140.0.1 announced to use tunneling via its public IP (192.16.126.18 I think)? Or why announce it at all in the RIP if it the whole subnet is is BGPed? Is it pure ambition just to break existing working things? -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Marius Petrescu Sent: Saturday, January 10, 2015 08:53 To: 'AMPRNet working group' Subject: Re: [44net] 44 Network behind BGPed 44 Address (Please trim inclusions from previous messages) _______________________________________________ I would propose to add another announce type: Announce bgp gateways with its own gateway set to 0.0.0.0: So in this case: 44.140.0.1/32 via 0.0.0.0 44.140.0.0/24 via 44.140.0.1 The daemon shall be modified to add routes to addresses which have gw 0.0.0.0 to be routed via default. This will give a functional setup, with 44.140.0.1 reachable direct, and 44.140.0.0/24 IPIP encapsulated and sent to 44.140.0.1. BTW: Could anyone tell me a IP inside that network, except that gateway, which should be reachable for testing purposes? Marius, YO2LOJ