[Olsr-users] OLSR running but not updating routing table

[Adam Longwill]

We just found out it's due to the subnet being set incorrectly afterall.
The intern has been thoroughly flogged for this.

Thank you for that piece of information though!

On Fri, Sep 30, 2016 at 4:51 PM, Lars Kruse <(spam-protected)> wrote:

> Hello Adam,
>
>
> Am Fri, 30 Sep 2016 15:20:54 -0400
> schrieb Adam Longwill <(spam-protected)>:
>
> > [..]
> > But if you look at the IP of the Main Router in the neighbors list, the
> ETX
> > value is 0.0 which... I have never seen before.
>
> The ETX value is derived from LQ (link quality) and NLQ (neighbor link
> quality):
>  ETX = 1 / (LQ * NLQ)
>
> In your case NLQ is zero - thus ETX is infinite/undefined, which is
> visualized
> by OLSRD as zero (i.e. there is no route).
>
> You will need to find the reason for your NLQ being zero.
>
> In general it means that the neighbor does not receive locally generated
> OLSR
> packets. Your screenshot shows the perspective of your Ubiquiti router
> towards
> your Main Router.
>
> I guess, that your Main Router does not receive the OLSR packets from your
> Ubiquiti router. Maybe firewall rules or something similar are in their
> way.
> I would recommend the following approach:
> * run "tcpdump -npi INTERFACE port 698" on your Main Router - you should
> see
>   the OLSR announcements between the Main Router and the Ubiquiti router
> * verify the LQ/NLQ numbers on your Main Router
>   (e.g. "echo /links | nc localhost 2006" or visit
> http://MAIN_ROUTER:8080/)
>   This requires the txtinfo or httpinfo plugin on the Main Router.
>
> Cheers,
> Lars
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20160930/2ba2aa98/attachment.html>