[Olsr-dev] Idea for small OLSR improvement

[Markus Kittenberger]

On Sun, Apr 25, 2010 at 9:49 AM, Mitar <(spam-protected)> wrote:
But why would then those counters be written to syslog?
as i plan to keep/push this code inside stable olsrd (with a quite low
OLSR_TC_VTIME_WARN_PERC value)

for my own debugging i use the printf and /* the syslog*/, feel free to use
fprintf to you file of choice, or use stdout like me,..

Markus

p.s. the reason for the bug i found in my mesh, looks quite much like
duplicate (originator) ips, sending tcs with different vtimes,..

07907: vtime of tc entry from 78.41.112.149 was reduced by new tc, duplicate
ips? or just reconfigured node? (old: 474312 new: 368000)
10062: vtime of tc entry from 78.41.112.149 was already down at 70%! (old:
349828 new: 496000)
10414: vtime of tc entry from 78.41.112.149 was reduced by new tc, duplicate
ips? or just reconfigured node? (old: 474060 new: 368000)

btw. i again attached the patch doing above output,..
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100425/c5c8bc12/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tc_vtime_warn.patch
Type: application/octet-stream
Size: 3476 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100425/c5c8bc12/attachment.obj>