[Olsr-users] OLSRv2: routing table contains only direct neighbours

Henning Rogge (spam-protected)
Fri Mar 4 08:10:32 CET 2016

On Fri, Mar 4, 2016 at 2:56 AM, Lars Kruse <(spam-protected)> wrote:
> Hi,
> I am running OLSRDv2 on openwrt:
>  oonf-init-scripts - 0.9.1-r3
>  oonf-olsrd2 - 0.9.2
> Currently five nodes are connected:
>   A
>    \
>     B---C---D
>    /
>   E
> Here is the routing table of node B:
> (spam-protected):~# ip route show table olsrd2
> via dev wlan0  proto 100  src
> via dev eth1.10  proto 100  src
> via dev eth0.10 proto 100  src
> The above target routes belong to A, C and E - the direct neighbors of B.
> The route for node D is missing in the routing table.
> The same goes for the routing tables of all other nodes: only the direct
> neighbors are visible.
> Nevertheless node B is aware of node D, as seen in the telnet interface:
>   echo /nhdpinfo link_twohop | nc localhost 2009

Could be that the connection between C and D is not symmetric...

could you post the output of the "/nhdpinfo link" command for node B and C?

> I am slightly confused that the route to node D is not visible in the routing
> table. I am used to the behaviour of OLSRDv1: here all routes for all known
> nodes independent of their distance are visible in the routing table.
> Was the concept for populating routing tables changed somehow between OLSRv1 and
> v2?

Its practically the same as with OLSRv1.

What you are seeing is (most likely) a route generated by the NHDP
(Hello) part of OLSRd2, without the OLSRv2 (TC) part.


More information about the Olsr-users mailing list