[Olsr-dev] Idea for small OLSR improvement

Markus Kittenberger (spam-protected)
Sun Apr 25 10:17:10 CEST 2010

setting vtime to infinite will let you keep all rubbish forever, not only if
it the rubbish was the last link,..

as tcs are (luckily) somewhat different too mid/hnas, as they can actively
delete old links with a new tc,.. having infinite tc-vtimes is not that
combined with an broken/disabled mpr, and (some) olsrd only accepting links
with tc from both sides (making such rubbish link unreachable), this might
boil down to being currently practically identical,..

but as above olsr-limitations shall not stay forever, it is no good idea to
use infinite vtimes,.. and maybe there are even scenarious with actual olsrd
where they can make u problems

btw a mid/hna with an infinite vtime, will be around "forever" (ok this
means ~ 50 days), and might cause some heavy "confusions"


On Sun, Apr 25, 2010 at 9:49 AM, Mitar <(spam-protected)> wrote:

> Hi!
> On Sun, Apr 25, 2010 at 8:36 AM, Markus Kittenberger
> <(spam-protected)> wrote:
> > hmm maybe i will code something like this now *G
> OK. If you code this counters we can collect them and analyze. For
> this later part we already have system developed.
> But why would then those counters be written to syslog? If it is only
> for debugging if would be maybe useful to write them directly to some
> specified files? (I have in mind something like /proc files, but this
> can be a normal file OLSR manages.)
> > btw: setting vtime to infinite is not the same as having the last route
> > forever.
> And what is the difference?
> Mitar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100425/2096f1c6/attachment.html>

More information about the Olsr-dev mailing list