On Wed, Aug 7, 2013 at 6:00 AM, Brian Kantor Brian@ucsd.edu wrote:
Seems to me that encap routes learned by rip44 should be fairly persistant - I'd say they shouldn't expire for a day or three or more. Perhaps a week?
My rip44d times out old routes only after 7 days. It's intentionally on the safe side. The downside is that if a longer prefix, let's say 44.255.255.0/24 is removed from the routing table, and a shorter prefix of 44.255.254.0/23 is added to replace it, the more specific route will sit in the table for 7 days. The code could be easily improved to time out removed prefixes falling within another prefix
The expiration code runs *only* after it has received a new routing update, so if amprgw stops broadcasting new routes, the routes will not time out at all. Here's the relevant few lines of code:
https://github.com/hessu/rip44d/blob/master/rip44d#L75 https://github.com/hessu/rip44d/blob/master/rip44d#L527
It's also pretty easy to set up a new rip sender in case amprgw would go away - maybe a backup setup could be prepared at another site in advance.
You could, of course, decide to NEVER expire them. With daemon modification, they could be persistent across reboots and only purged when manually selected.
Yup, I think the C version already writes them on disk and loads from there after a reboot.
- Hessu