[OLSR-users] recovery from broken link

[Bing]

I just tested with LQ level 0. It worked, and I can see the quick change of 
topology, without affecting other nodes. Thank you for your solution.
I have another problem.  It took a long time to ping two hop nodes. It 
usually took 2ms to one hop node, two-hop node over 10 seconds! I block mac 
address to fake multihops. Does this matter?
thanks.

Bing

----- Original Message ----- 
From: "Andreas Tønnesen" <(spam-protected)>
To: "OLSR discussion and development" <(spam-protected)>
Sent: Tuesday, November 29, 2005 3:03 PM
Subject: Re: [OLSR-users] recovery from broken link


>
> Does the same happen using LQ level 0? Olsrd is supposed to
> detect link loss and it should happen rather rapid with your
> configuration.
> And then you need to verify the findings against 0.4.9/CVS.
>
> - Andreas
>
> Bing wrote:
>> Hi Andreas,
>>
>> Thank you for your quick reply. My config file (olsrd.conf) is the 
>> default, that is, almost everything is commented except LQ is on as 
>> follows:
>> UseHysteresis no
>> Link quality level 2
>> LinkQualityWinsize 10
>>
>> In Interface part, only two options:
>> HelloInterval 0.2
>> HelloValidityTime 5.0
>>
>> My command is : olsrd -d 2
>>
>> Thanks.
>>
>> Bing
>>
>> ----- Original Message ----- From: "Andreas Tønnesen" <(spam-protected)>
>> To: "OLSR discussion and development" <(spam-protected)>
>> Sent: Tuesday, November 29, 2005 2:13 PM
>> Subject: Re: [OLSR-users] recovery from broken link
>>
>>
>>> Hi Bing,
>>>
>>> That is some strange behaviour... Could you test using 0.4.9 or
>>> better yet, current CVS?
>>> Also the configuration used is needed. Please post the config 
>>> file/command line options.
>>>
>>> Thanks.
>>>
>>> - Andreas
>>>
>>> Bing wrote:
>>>
>>>> Hello all,
>>>>  I am testing olsrd 4.8. I wanted to test node moving in and out of the 
>>>> network.
>>>> For movement out of the area, I  simply powered off that node. It 
>>>> seemed olsrd could never recover by itself. OLSRD in the other nodes 
>>>> also stopped working. After over 20 minutes, I had to manually stop 
>>>> olsrd by "Ctrl C", and restart olsrd.   For movement in, it was good, 
>>>> olsrd could automatically detect the new node without affecting other 
>>>> nodes.
>>>> What's wrong with this? Is the way it is or some bugs?
>>>>  Thanks.
>>>>  Bing
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> olsr-users mailing list
>>>> (spam-protected)
>>>> https://www.olsr.org/mailman/listinfo/olsr-users
>>>
>>>
>>>
>>> _______________________________________________
>>> olsr-users mailing list
>>> (spam-protected)
>>> https://www.olsr.org/mailman/listinfo/olsr-users
>>
>>
>>
>> _______________________________________________
>> olsr-users mailing list
>> (spam-protected)
>> https://www.olsr.org/mailman/listinfo/olsr-users
>
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users