New subject: Tunnel mesh is (mostly) down

5 Jan 2015

44net-request(a)hamradio.ucsd.edu wrote:
...
  Subject:
 Re: [44net] Tunnel mesh is (mostly) down
 From:
 "Marius Petrescu" &lt;marius(a)yo2loj.ro&gt;
 Date:
 01/05/2015 07:30 AM

 To:
 "'AMPRNet working group'" &lt;44net(a)hamradio.ucsd.edu&gt;

 Hello,

 I don't think that increasing the route timeout the would have any bad side
 effects (I think 7200 would be a good value). 
I have recompiled with 3600 before I read that.   However, I'll keep a watch on it for
some
time to see if strange things still happen.

It could be that the latest version that I now downloaded hides that problem with
44.140.0.1
but I can easily see if other routes are appearing/disappearing regularly.

...

 But maybe there is another mechanism that could be added to the ampr gateway
 (And which is already implemented in ampr-ripd):
 The daemon is capable of force exipring routes if they are received with
 metric 15.
 So adding the sending of deleted subnets with metric 15 fore a given time
 AND increasing normal expire time to higher values (e.g. 10800 - 3 hours, or
 even more) would make the system more stable.

 Marius, YO2LOJ

 That sounds like a good idea, in that case there could be a much longer timeout,
but
maybe it should then (as Brian suggested) log when it receives less packets than normal.
E.g. count the received packets in a single burst and syslog a message when it is 2-3
less
than in the previous burst.
When we fix the problem that routes disappear too soon, but then nobody notices anything
and 24 hours later we still have a problem because the routes are suddenly deleted, not
much has improved.  When there is some alert I can watch it in our nagios monitoring.

Rob