Both the ampr-ripd and amprd expire the routes after 15 minutes, only, and only if they get RIP updates via the tunnel. If no RIP messages are arriving, the routes are persistent, including a restart of the daemons, behaving as if you have a static encap file.
Basically it is like having a munge script with an auto-updater.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: Wednesday, August 07, 2013 06:01 To: 44net@hamradio.ucsd.edu Subject: Re: [44net] Why rip44d?
(Please trim inclusions from previous messages) _______________________________________________ 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?
Unless replaced by a newer route for the same subnet, of course.
That way if the rip sender (amprgw) should happen to go away for a while, things will still function. And you'd have time to switch over to using the encap file if the outage were to be prolonged.
There's no harm in having a dormant route in your table for a while when a gateway permanently goes away.
What's the maximum rip44 route expiration time setting?
You could, of course, decide to NEVER expire them. With daemon modification, they could be persistent across reboots and only purged when manually selected. - Brian _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html