The same happens in ampr-ripd. If no new routes are received, the old ones will persist and will be used. @Hessu: I implemented that idea from your perl script, too, since the first version was actually almost a 1 to 1 clone . The initial goal was to get rid of perl for low resource systems...
Marius.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Heikki Hannikainen Sent: Tuesday, January 06, 2015 23:53 To: AMPRNet working group Subject: Re: [44net] Tunnel mesh is (mostly) down
(Please trim inclusions from previous messages) _______________________________________________ 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
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net