Lynwood;
On Fri, 2015-01-09 at 19:52 -0500, lleachii@aol.com wrote:
This is something I mentioned was needed for us to do a while ago but was flamed for saying such.
Using Linux routing, I solved the problem by adding the 44 subnet to a special routing table, and adding the Public-facing gateway address to my Public-facing route table. Hence, these routes and rules ignore the "invalid" RIP44 gateway announcement.
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.