<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
It is interesting that the gateway node stops transmitting OLSR packets
all together.<br>
In an older version (we're talking 0.5.6 I think) there was an old
timer bug where the system call times() return value goes negative and
then the timers wouldn't work anymore until you reboot. I find it
interesting that this problem happens and upon restarting OLSRd it
still won't work and you have to resort to reboot so uptime of the OS
is zeroed. Does it seem to be uptime related?<br>
<br>
Try running OLSR interactively with any debug turned up and I think it
will show timers firing on one of the debug levels (if it is still the
same since a long time ago when I was debugging OLSR :) and see if the
timers stop working when your gateway node stops transmitting OLSRd
packets... I'm guessing timers are what make the OLSR packets get
transmitted periodically.<br>
<br>
This may be a longshot, but it sounded quite familiar to that old timer
issue -- if you search the mailing list you will find posts by me from
a long time ago if you want to know about the old issue...<br>
<br>
Good luck!<br>
<br>
-Eric Malkowski<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:olsr-users-request@lists.olsr.org">olsr-users-request@lists.olsr.org</a> wrote:
<blockquote
cite="mid:mailman.1.1406541602.21792.olsr-users@lists.olsr.org"
type="cite">
<pre wrap="">Send Olsr-users mailing list submissions to
<a class="moz-txt-link-abbreviated" href="mailto:olsr-users@lists.olsr.org">olsr-users@lists.olsr.org</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a class="moz-txt-link-freetext" href="https://lists.olsr.org/mailman/listinfo/olsr-users">https://lists.olsr.org/mailman/listinfo/olsr-users</a>
or, via email, send a message with subject or body 'help' to
<a class="moz-txt-link-abbreviated" href="mailto:olsr-users-request@lists.olsr.org">olsr-users-request@lists.olsr.org</a>
You can reach the person managing the list at
<a class="moz-txt-link-abbreviated" href="mailto:olsr-users-owner@lists.olsr.org">olsr-users-owner@lists.olsr.org</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Olsr-users digest..."
Today's Topics:
1. Re: INFINITE cost in all links (Henning Rogge)
----------------------------------------------------------------------
Message: 1
Date: Mon, 28 Jul 2014 08:07:48 +0200
From: Henning Rogge <a class="moz-txt-link-rfc2396E" href="mailto:hrogge@gmail.com"><hrogge@gmail.com></a>
To: Antonio Anselmi <a class="moz-txt-link-rfc2396E" href="mailto:tony.anselmi@gmail.com"><tony.anselmi@gmail.com></a>
Cc: olsr users mailing list <a class="moz-txt-link-rfc2396E" href="mailto:olsr-users@lists.olsr.org"><olsr-users@lists.olsr.org></a>
Subject: Re: [Olsr-users] INFINITE cost in all links
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:CAGnRvupU5Ah8Kq17QH7atH65RXSioC-+e=yHyRRAThuJqkWbLA@mail.gmail.com"><CAGnRvupU5Ah8Kq17QH7atH65RXSioC-+e=yHyRRAThuJqkWbLA@mail.gmail.com></a>
Content-Type: text/plain; charset=UTF-8
On Fri, Jul 25, 2014 at 12:11 PM, Antonio Anselmi
<a class="moz-txt-link-rfc2396E" href="mailto:tony.anselmi@gmail.com"><tony.anselmi@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
I'm facing an odd problem that recurs randomly, without any user
intervention, at different times on a single-gateway network.
Suddenly, all the links of the gateway node have their NLQ values equal to
zero and the respective LQ values greather than zero, so every link has an
INFINITE cost -> olsrd route table is empty -> ip main route table is empty.
Just because all NLQ values are zero, it seems that the nodes do not
receive/hear olsrd packets from the gateway, but , at the same time, the
gateway itself continues to receive and process packets sent by the other
node (LQ values change in time).
In this situation, I logged to the gateway node and run the command 'tcpdump
-vv -ni wlan0-1 port 698' (wlan0-1 is the adhoc interface) to inspect the
way olsrd was working.
As supposed:
1) the gateway had stopped transmitting olsrd packets but continued to
receive and process olsrd packets sent by the other nodes
2) olsrd route table and ip main route table were empty and the gateway does
not ping any other node
3) the topology seen by the gateway have no node reachable
4) at layer2 the neighbors are all associated (iw dev wlan0-1 station dump)
so adHoc beacons travel
Stopping and restarting olsrd does not fix the stalemate as well as manually
populating the ip main route table. Obviuosly, rebooting the node all goes
right ...untill the next olsrd stale.
I'm wondering:
1) Why all links go to INFINITE cost? (A loop caused by LQ mechanism?)
2) may be the case that the gateway try to transmit olsrd packets, but since
its route table is empty, no packet reach the adHoc interface
(loop inside the gteway) ?
3) since the TC-LQ packets sent by the nodes (and received by the gateway)
do not show the gateway (NLQ = 0) why these packets reach the gateway? Nodes
should have no route to the gateway since they do not hear it!
4) and... the all_INFINITE_costs situation (as well as the empty routing
tables) is a "cause" or an "effect" ?
</pre>
</blockquote>
<pre wrap=""><!---->
NLQ infinite most likely means that the other side cannot hear you,
but you can hear the other side.
Can you check on the gateway with the txtinfo command?
Henning Rogge
------------------------------
Subject: Digest Footer
</pre>
</blockquote>
<br>
</body>
</html>