[Olsr-users] Segmentation_fault:n

Henning Rogge (spam-protected)
Wed Mar 9 12:26:21 CET 2016

On Wed, Mar 9, 2016 at 11:42 AM, s-mtafel <(spam-protected)> wrote:
>> I guess if you revert this commit it will work:
>> http://olsr.org/git/?p=oonf.git;a=blobdiff;f=src-plugins/nhdp/nhdp/nhdp_reader.c;h=2f58fb38a8384864f8a2484e466e3138b0d13b8b;hp=485f8d1a85675d1bb0bac2cabec549250995b982;hb=0512c50a79ac239dd8ade9e3d3034c50d275be88;hpb=c250c2282a790960babe33c14b64bb5b92dc0f4b
> Yes, now everything is up and runnig. But am I missing standard conformity
> now? Am I running a valid behaviour.

The problem is twofold...

first there is a Linux kernel bug that has only recently been fixed
that allow multicast messages to arrive through unicast sockets...
this will get your weird behavior.

second, I would like the option to run NHDP on a point-2-point link
without multicast... which means that I just give it an unicast
address as the "multicast destination". That's why I removed the
"check for multicast" from NHDP reader.

What you see is what happens when an incoming Multicast also arrives
through the non-interface specific unicast socket... which means NHDP
cannot determine the interface. Which is not checked because it should
not happen.

Could you try the attached patch instead of the revert? It should also
fix the issue for you.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: nhdp_unicast.patch
Type: text/x-patch
Size: 621 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20160309/22905283/attachment.bin>

More information about the Olsr-users mailing list