[Olsr-users] OLSRv2: routing only for one hop neighbors

[Henning Rogge]

On Thu, Apr 7, 2016 at 10:53 PM, Martin Garbe
<(spam-protected)> wrote:
> On 04/07/2016 09:11 AM, Henning Rogge wrote:
>> Okay,
>>
>> something really strange is going on here...
>>
>> could you show the output of the following two commands to the list?
>>
>> echo /nhdpinfo link_twohop | nc 127.0.0.1 2009'
>> echo /olsrv2info edge | nc 127.0.0.1 2009
>
> Node A:
> $ echo /nhdpinfo link_twohop | nc 127.0.0.1 2009
> eth0    192.168.21.3    192.168.21.3    192.168.230.2   false   19      ff_dat_metric
> 136.533 Mbit/s  15      120.47 Mbit/s   17
>
> $ echo /olsrv2info edge | nc 127.0.0.1 2009
>  (empty string returned)
>
>
> Node B:
> # echo /nhdpinfo link_twohop | nc 127.0.0.1 2009
>  (empty string returned)
>
> # echo /olsrv2info edge | nc 127.0.0.1 2009
> 192.168.99.1    192.168.21.3    56445   0       ff_dat_metric   1020  bit/s     2105088
>
>
> Node C:
> # echo /nhdpinfo link_twohop | nc 127.0.0.1 2009
> wlan0   192.168.21.2    192.168.21.3    192.168.99.1    false   18      ff_dat_metric
> 1020  bit/s     2105088 1020  bit/s     2105088
>
> # echo /olsrv2info edge | nc 127.0.0.1 2009
>  (empty string returned)

WTF??

This looks like the central node neither produces nor forwards TCs...

give me a few days, I have too look into this issue more deeply. Thank
you for spending all the time for debugging this with me.

Henning