[Olsr-dev] Poor routing performance
Tue Nov 9 07:32:46 CET 2010
According to the routing table, there should be a direct route from .62 (my
laptop) to .81:
192.168.1.81 0.000 1.000/1.000 1.000
However, when I do a route get .81, it says that it goes through .61.
Pinging .81 fails (no packets get sent), after I stop OLSR and flush the
routing table, I get 100% link quality to .81. I wonder if somehow some of
the routes do not get updated properly. The strange error "Cannot write to
routing socket: (rtm_errno= 0x0) (last error message: File exists)" may be
an indication that is happening, though I do not know enough about OLSR to
say for sure.
On Mon, Nov 8, 2010 at 10:23 PM, Mitar <(spam-protected)> wrote:
> On Tue, Nov 9, 2010 at 1:56 AM, Octav Chipara <(spam-protected)> wrote:
> > I was expecting to have a direct link to .81, however, it looks
> > like for whatever reason according to ping -R my route goes through .81.
> I do not understand. Why "direct link to .81" is not the same as "my
> route goes through .81"? Or why the first is better than the other?
> For next (and first) hop to go through .81 you need a direct link to
> .81. That is the same thing. And OLSR finds that (ETX being 1.0) and
> uses it.
> Maybe you are confused because OLSR adds routes for every node in the
> mesh, even peering/neighbors/1-hop nodes?
> Route through .81 to node .81 does mean it is a direct link.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Olsr-dev