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

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 -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Brian Sent: Saturday, January 10, 2015 05:32 To: AMPRNet working group Subject: Re: [44net] 44 Network behind BGPed 44 Address (Please trim inclusions from previous messages) _______________________________________________ Lynwood; On Fri, 2015-01-09 at 19:52 -0500, lleachii(a)aol.com wrote: This is something I mentioned was needed for us to do a while ago but was flamed for saying such. n The unfortunate part of this is for ALL BGP based 44-net subnets this is required. My suggestion took this a bit further in which the RIP broadcaster might send these BGP based 44-net subnets with a flag ampr-ripd or Hessu's perl can see and add these specialized rules without manual intervention as would be needed now. The question at hand is whether or not this is possible to do at both the RIP server and rip daemons. For linux admins to have to manually maintain route rules for those subnets, for which routing should be fully automatic, is a major step backward IMHO... especially when this system has worked for us all for decades. I just don't understand how it's "broken" overnight. -- To falter a protocol for the actions of a human is in reality the human failing to take responsibility for their own actions. 73 de Brian Rogers - N1URO email: <n1uro(a)n1uro.ampr.org> Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont. _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net