[Olsr-dev] Missing routes and unexpected routes reg.

[Henning Rogge]

Just a thought I had,

did you try to use the "MPR plugin" ? I ask because its quite new and
needs a lot more testing.

Henning

On Sat, Jun 7, 2014 at 4:02 AM, vignesh <(spam-protected)> wrote:
> On 2014-06-06 18:41, Henning Rogge wrote:
>>
>> Hi,
>>
>> just to make sure, you can see all four nodes producing TC messages?
>
>
> I remember only R2 and R3 produced TC. However, I will recheck the logs on
> Monday.
> (I have under the impression that only ROUTING MPRs will generate TC, and in
> this topology, R2, R3 may be the MPRs for its neighbours).
>
>
>> Maybe I have to replicate this setup when I am back at work on
>> Tuesday, I have no clue what is going on.
>
>
> Ok. At this point what I suspect is, R3 is not selecting R2 as MPR. So, the
> TC message generated by R3 (which contains information about R4 also) is not
> reaching R1. So, R1 is not getting route for R4. Could you please tell how
> to verify the above from the logs? Esp. how to see information about MPRs?
>
>
> R1 <---> R2 <---> R3 <---> R4
>
> If you would like to look into the logs I can compress the logs and send
> you. Thanks.
>
> Regards,
> Vignesh
>
>
>>
>> Henning
>>
>> On Fri, Jun 6, 2014 at 2:38 PM, Vigneswaran R <(spam-protected)> wrote:
>>>
>>> On 06/06/2014 02:58 PM, Vigneswaran R wrote:
>>>
>>> On 06/06/2014 02:23 PM, Vigneswaran R wrote:
>>>
>>> On 06/06/2014 01:01 PM, Henning Rogge wrote:
>>>
>>> On Fri, Jun 6, 2014 at 9:39 AM, Bastian Bittorf <(spam-protected)>
>>> wrote:
>>>
>>> * Vigneswaran R <(spam-protected)> [06.06.2014 09:37]:
>>>
>>> Could you please help in debugging these problems? Thanks.
>>>
>>> can you show is you commandline or config? bye, bastian
>>>
>>> The output of "ip addr" on every node would also help.
>>>
>>>
>>> Command Line:
>>>
>>>     ./olsrd2 -l olsrd2.conf
>>>
>>> Configuration file contents:
>>>
>>> [interface=eth0]
>>> [interface=eth1]
>>>
>>> Exception: On R1, only eth1 included.
>>>
>>> IP Addr: (pfa the complete output)
>>>
>>> R1: eth0: 1.0.0.2/24 (non-olsr), eth1: 10.1.1.1/32
>>> R2: eth0: 10.1.2.1/32, eth1: 10.1.2.2/32
>>> R3: eth0: 10.1.3.1/32, eth1: 10.1.3.2/32
>>> R4: eth0: 10.1.4.1/32, eth1: 10.1.4.2/32
>>>
>>> (I am using /32 mask for testing. However, I got the same problem with /8
>>> mask also).
>>>
>>> Please let me know if any other information is required.
>>>
>>>
>>> PFA the output of the following command on all the nodes. Please see
>>> whether
>>> this helps.
>>>
>>> echo "nhdp neighlink" | nc 127.0.0.1 2009
>>>
>>>
>>> Restarted olsrd2 with debug=all and observed the following from the
>>> collected logs,
>>>
>>> 1. R1 received TC messages originated from R2 (10.1.2.1) only.
>>>   -- Shouldn't it get TC from 10.1.3.1 also? I think, this is the reason
>>> why
>>> R1 is not getting route for R4.
>>>
>>> 2. R2 received TC messages originated from R3 (10.1.3.1) only.
>>>   -- I think, this is fine for the 4 nodes topology.
>>>
>>> 3. R3 received TC messages originated from R2 (10.1.2.1) only.
>>>   -- this is also fine for the same reason.
>>>
>>> 4. R4 received TC messages originated from both R2 (10.1.2.1) and R3
>>> (10.1.3.1).
>>>
>>> If you want me to post specific portions of the log files, please
>>> suggest.
>>>
>>> Regards,
>>> Vignesh
>>>
>>>
>>>
>>> Regards,
>>> Vignesh
>>>
>>>
>>>
>>>
>>> --
>>> Olsr-dev mailing list
>>> (spam-protected)
>>> https://lists.olsr.org/mailman/listinfo/olsr-dev