<p>errors like this happen "always",.. ((we did talk about this last week in mq (-;) so - to be honest - your mail made me grin a bit)</p><p>the reasons behin:</p><p>it`s only a matter of time till olsr-routing table and kernel routing table aren`t identical any more,.. (because of olsr beeing not the only one changing the kernel table, and imho because of some still unfound bugs in olsrd )-;<br>
</p><p>errors like "file exists" usually just mean, that olsr tries to insert a route which is already there (usually because olsr inserted it himself and forgot about it, mostly because olsrd crashed/got killed by user and restartet in the meantime, or the kernel deleted routes in reaction of an interrface being removed/going down, but sometimes also without such obviuos reasons)</p>
<p>same with no such process (olsr want to delete a route which isn`t here anymore)</p><p>the annoying part is that this error will happen very often/and maybe forever (if your topo is completely stable), as olsr will never give up, on inserting an route that already exists,. </p>
<p>using an own rttable (and/or rtproto) for oslr helps a bit on this issue<br>because it prevents you or other routing daemons from interfering, and because it`s easier doing following:<br>flush this table/proto always before starting olsr!!! (#ip route flush [table olsr] proto olsr)</p>
<p>regards Markus</p><p>p.s. if this really bothers you may use the patch (which i postet on olsr-dev last month? (you looked shortly in mq on it)), which changes handling of add/delete route kernel warnings which is imho more suited to real-world usage of the olsrd, </p>
<p>but as infact no more periodic errors occure (but a single warning on first attempt (is still possible) and imho this is exactly enough!) it may be not so well suited to find the remaining olsrd-bugs mentioned above,..</p>
<br><div class="gmail_quote">On Sun, Jan 11, 2009 at 1:41 AM, L. Aaron Kaplan <span dir="ltr"><<a href="mailto:aaron@lo-res.org">aaron@lo-res.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I regularly get these messages:<br>
<br>
Source IP addr Dest IP addr LQ ILQ ETX<br>
192.168.100.1 192.168.100.101 1.000 1.000 1.00<br>
192.168.100.101 192.168.100.1 1.000 1.000 1.00<br>
Processing TC from 192.168.100.1, seq 0x001b<br>
Processing TC from 192.168.100.1, seq 0x001b<br>
KERN: ERROR adding <a href="http://192.168.100.1/32" target="_blank">192.168.100.1/32</a> from 192.168.100.1 via<br>
192.168.100.1, etx 1.000, metric 1, v 18: File exists<br>
KERN: ERROR adding <a href="http://0.0.0.0/0" target="_blank">0.0.0.0/0</a> from 192.168.100.1 via 192.168.100.1, etx<br>
1.000, metric 1, v 18: File exists<br>
<br>
seems like adding routes is not that graceful yet on the linux/android<br>
G1.<br>
Would have to look more into that.<br>
And I still don't have a fix for the Mac OS X lack of installing<br>
kernel route entries.<br>
More work needed there.<br>
<br>
a.<br>
<font color="#888888"><br>
<br>
--<br>
Olsr-dev mailing list<br>
<a href="mailto:Olsr-dev@lists.olsr.org">Olsr-dev@lists.olsr.org</a><br>
<a href="http://lists.olsr.org/mailman/listinfo/olsr-dev" target="_blank">http://lists.olsr.org/mailman/listinfo/olsr-dev</a><br>
<br>
</font></blockquote></div><br>