3 Jan
2015
3 Jan
'15
8:45 p.m.
Ah, <forehead slap>, of course. A true Homer Simpson "Doh!" moment.
But based on the fact that this has happened twice in the last few months,
it seems it might also be useful to add some other fault
detection/prevention options to ampr-ripd. For example, if the number of
routes received in the last update is smaller by some value X than the
number of existing routes, then there's likely something wrong. Don't take
that as a specific suggestion. It would take some thought to figure out
how/what to detect and also what to do about it once detected (ignore the
new update, send an email, etc.). Again, just some ideas.
Michael
N6MEF
-----Original Message-----
There is a simple method for this.
Define your important routes as static routes and run ampr-ripd.
They won't be deleted if their RIP counterparts dissapear since ampr-ripd
is
able to delete only the routes set by itself (the ones that show up as
proto
44 under 'ip route list').
Marius, YO2LOJ