[Olsr-dev] slight bug in the android port

[Markus Kittenberger]

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)

the reasons behin:

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 )-;

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)

same with no such process (olsr want to delete a route which isn`t here
anymore)

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,.

using an own rttable (and/or rtproto) for oslr helps a bit on this issue
because it prevents you or other routing daemons from interfering, and
because it`s easier doing following:
flush this table/proto always before starting olsr!!! (#ip route flush
[table olsr] proto olsr)

regards Markus

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,

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,..

On Sun, Jan 11, 2009 at 1:41 AM, L. Aaron Kaplan <(spam-protected)> wrote:

> I regularly get these messages:
>
> Source IP addr  Dest IP addr    LQ     ILQ    ETX
> 192.168.100.1   192.168.100.101  1.000  1.000  1.00
> 192.168.100.101 192.168.100.1    1.000  1.000  1.00
> Processing TC from 192.168.100.1, seq 0x001b
> Processing TC from 192.168.100.1, seq 0x001b
> KERN: ERROR adding 192.168.100.1/32 from 192.168.100.1 via
> 192.168.100.1, etx 1.000, metric 1, v 18: File exists
> KERN: ERROR adding 0.0.0.0/0 from 192.168.100.1 via 192.168.100.1, etx
> 1.000, metric 1, v 18: File exists
>
> seems like adding routes is not that graceful yet on the linux/android
> G1.
> Would have to look more into that.
> And I still don't have a fix for the Mac OS X lack of installing
> kernel route entries.
> More work needed there.
>
> a.
>
>
> --
> Olsr-dev mailing list
> (spam-protected)
> http://lists.olsr.org/mailman/listinfo/olsr-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20090112/4af7cc48/attachment.html>