[Olsr-users] OLSR disconnets all routes when a interface will be added or removed

[Henning Rogge]

Hi,

I am not sure, but I might have a hint what could go wrong.

While trying to replicate the problem on a couple of virtual machines
I run into something strange.

My arp-table suddenly contained the wrong mac address for the "next
hop", which meant that IP communication stopped over the link (even
when pinging next hop) until the arp timed out.

Could you maybe check your arp-table if the IPs of your direct
neighbors have the correct mac address?

Henning

On Mon, Dec 8, 2014 at 1:19 PM, Henning Rogge <(spam-protected)> wrote:
> Hi,
>
> just a question about the graphics you sent to the list...
>
> are they produced locally on the node or are they generated by a different node?
>
> Henning
>
> On Sun, Dec 7, 2014 at 8:57 PM, Henning Rogge <(spam-protected)> wrote:
>> On Sun, Dec 7, 2014 at 6:32 PM, Michael Rack
>> <(spam-protected)> wrote:
>>> Sure.
>>>
>>> It must be OLSR because the image that i've attached got its data from
>>> the txtinfo-plugin. You can see that at 18:19:32 the route were removed
>>> and comes up at
>>> 18:21:58, the routes were removed for 2 Minutes and 26 seconds.
>>
>> Which means something different is happening. There is nothing in
>> olsrd with a memory that long.
>>
>> If it really would just remove the routes (more likely the TC or the
>> Hello database), they would be up 10-30 seconds later.
>>
>>> The script relates to the section "LINKS" http://127.0.0.1:2001/links
>>> The script reads each line and send the data to an rrd-file.
>>>
>>> When the interface was removed, the txtinfo-plugin returned a empty
>>> "links"-Section.
>>>
>>> Sometimes i got nice stats like "OLSR Problem Remove Interface.png".
>>
>> That is showing a symptom, but not the cause.
>>
>> Henning Rogge