On Mon, 5 Jan 2015, Rob Janssen wrote:
Brian Kantor wrote:
I agree that making the timeout much longer than
10 minutes is wise.
I am now running the latest ampr-ripd with 1 hour timeout, to see if there
are still problems.
My original perl implementation considers expiring old routes only after
receiving new routes. In other words, if it stops getting new routes,
it'll keep on running with the old ones forever (well, up to the next
reboot).
Just a suggestion. :)
- Hessu