New subject: New ampr-ripd 1.16 and amprd 1.5 released

4 Apr 2017

...
  If the daemon encounters a 44 gateway in the RIP data,
it creates a host
 route to that specific host via the default gateway of the system. 
I was thinking about one specific issue: when we run this code on our gateway, which is
BGP-routed for our 44.137.0.0/16 network and is on the IPIP network as well and runs
ampr-ripd,
and some portal user who does not understand the system well, they could add a gateway
with an
endpoint address inside the 44.137.0.0/16 network and we would add a circular route for
that
address to our table.

Of course users should not do that.  But they have done so, in the past.

Maybe we would need an option to specify a (list of) subnet(s) where this new mode of
operation
would not be performed.  Then a gateway can set that to the BGP routed network(s) it
serves.
(similar to the -a option)

Rob

Re: [44net] New ampr-ripd 1.16 and amprd 1.5 released