Talked to network people at the ISP, they indicate that they have changed something w.r.t. the routing via Eurorings. It should be researched and hopefully fixed.
In the meantime I am thinking about relaying the RIP packets from my own colo host to our gateway as an extra safeguard against things like this. I see that ampr-ripd has options -E and -F that should relay the raw packets to a specified address, good. That should work.
But I don't think it is possible to make ampr-ripd receive and act upon those relayed packets, isn't it? Should I NAT them at the receiving system so they again have 224.0.0.9 as destination? Has anyone tried such a setup and does it work without nasty issues? (normally all RIP packets will be received twice in this case)
Rob
Ampr-ripd can not use them. But a standard RIP daemon can :-)
On 02.04.2019 19:23, Rob Janssen wrote:
... In the meantime I am thinking about relaying the RIP packets from my own colo host to our gateway as an extra safeguard against things like this. I see that ampr-ripd has options -E and -F that should relay the raw packets to a specified address, good. That should work.
But I don't think it is possible to make ampr-ripd receive and act upon those relayed packets, isn't it? Should I NAT them at the receiving system so they again have 224.0.0.9 as destination? Has anyone tried such a setup and does it work without nasty issues? (normally all RIP packets will be received twice in this case)
Rob
-
Marius Petrescu -
Rob Janssen