[Olsr-dev] Missing routes and unexpected routes reg.
Fri Jun 6 14:38:42 CEST 2014
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:
>> Exception: On R1, only eth1 included.
>> IP Addr: (pfa the complete output)
>> R1: eth0: 220.127.116.11/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
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
If you want me to post specific portions of the log files, please suggest.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Olsr-dev