[Olsr-dev] Local attached network info not getting populated

[Vigneswaran R]

Hi,

One observation with the recent commits (on 22nd Jul)...

I am trying to advertise gateway for the following two networks, from 
'vm1'. All the routers got route to 21.0.0.0/24 network, however not to 
the 0.0.0.0/0 network (default gateway). Any suggestions?

lan 0.0.0.0/0
lan 21.0.0.0/24

Topology:
=========

vm1----------vm2---------vm3
| \                      |
|  \______               |
|         \              |
|          \             |
vm4----------vm5---------vm6

Main IPs (on 'lo' devices)
========

vm1 - 10.1.1.1/32
vm2 - 10.1.2.1/32
vm3 - 10.1.3.1/32
vm4 - 10.1.4.1/32
vm5 - 10.1.5.1/32
vm6 - 10.1.6.1/32


Regards,
Vignesh


On 07/22/2014 03:07 PM, Vigneswaran R wrote:
> On 07/22/2014 02:02 PM, Henning Rogge wrote:
>> Hi,
>>
>> I guess I had a bug in the host/network-byteorder handling of some
>> metric flags... I reworked this part and I can see the attached
>> networks now spreading.
>>
>> Can you give the latest commit a test?
>
> Yes, it's working. Thanks.
>
> vignesh
>
>> On Mon, Jul 21, 2014 at 2:25 PM, Vigneswaran R <(spam-protected)> 
>> wrote:
>>> Hello,
>>>
>>> In a simple (two nodes) olsrv2 topology, I am advertising gateway for
>>> 0.0.0.0/0 from one node. However, the corresponding route is not 
>>> getting
>>> reflected in the neighbor.
>>>
>>> This problem was not there with v0.5.0 commit. So, I did a git 
>>> bisect and
>>> found that the following commit introduced the problem. Could you 
>>> please
>>> help in resolving it?
>>>
>>> dda9ae431332fd51726cd373eb1f9664370e062d is the first bad commit
>>> commit dda9ae431332fd51726cd373eb1f9664370e062d
>>> Author: Henning Rogge <(spam-protected)>
>>> Date:   Wed Jul 2 08:13:20 2014 +0200
>>>
>>>      Small fixes for OLSRv2 parsing/generation
>>>
>>>
>>> Regards,
>>> Vignesh
>>>
>>> -- 
>>> Olsr-dev mailing list
>>> (spam-protected)
>>> https://lists.olsr.org/mailman/listinfo/olsr-dev
>
>