[Olsr-dev] Idea for small OLSR improvement

[Mitar]

Hi!

On Sat, Apr 24, 2010 at 11:39 PM, Markus Kittenberger
<(spam-protected)> wrote:
> with the vtimes in txtinfo u can now check if "everywhere" all entries have
> acceptable high vtimes all the time *G
> e.g. never reach below originators.validitytime/2

This should we be checking on all nodes of the mesh or it is enough
just to check it on one node?

If I understand correctly it is normal to have some of this warnings
from time to time on bad links? So we run your patch and we have
something like this:

1158128: vtime of tc entry from 10.254.128.193 was already down at
67%! (old: 173657 new: 256000)
1585849: vtime of tc entry from 10.254.132.225 was already down at
76%! (old: 122686 new: 160000)
1770809: vtime of tc entry from 10.254.129.1 was already down at 55%!
(old: 89122 new: 160000)
2972004: vtime of tc entry from 10.254.129.1 was already down at 77%!
(old: 123352 new: 160000)
3467226: vtime of tc entry from 10.254.128.193 was already down at
68%! (old: 175549 new: 256000)
4029024: vtime of tc entry from 10.254.128.193 was already down at
56%! (old: 145259 new: 256000)

So there are not many of them and for those there are are some with
bad links. So it seems we have a valid OLSR configuration for our mesh
size/topology?



Mitar