Hmmm. Given a 1 hour timeout, then any error would need to be detected and corrected within that hour, or else routes will still be lost. Correct?
It would seem that a timeout of something more like 24 hours would be more practical. I wouldn't think that holding on to old, stale routes (the other end is gone) for 24 hours would not be any significant problem. The problem case is if a longer (more specific) prefix is replaced with a shorter (less specific) prefix to a different location. The longer prefix would still win until it eventually times out. But maybe some ability to poison withdrawn routes (as Marius suggested) could be added to eliminate that problem, too?
Michael N6MEF
-----Original Message----- I am now running the latest ampr-ripd with 1 hour timeout, to see if there are still problems. (I can see some of the symptoms in the firewall log and the updated filter list)
Rob