>> Attached is the changes I made to Linux 2.6.29 to port the IP_MULTICAST_ALL
>> socket option from 2.6.31.
> Out of curiosity - why didn't you just use the 2.6.31 kernel? (It presumably
> has other fixes/improvements that you would find useful.)
The ARM SOC that I'm developing for was provide
> Attached is the changes I made to Linux 2.6.29 to port the IP_MULTICAST_ALL
> socket option from 2.6.31.
Out of curiosity - why didn't you just use the 2.6.31 kernel? (It presumably
has other fixes/improvements that you would find useful.)
Ross.
>> It seems that kernel maintainers chose to keep the backward
compatibility with a default that cause receiving data from all
multicast groups and not only from joined multicast group.
>> But they add since kernel 2.6.31 an option that allow to avoid this.
> That's good to hear. (I guess this
> It seems that kernel maintainers chose to keep the backward compatibility
> with a default that cause receiving data from all multicast groups and not
> only from joined multicast group.
> But they add since kernel 2.6.31 an option that allow to avoid this.
That's good to hear. (I guess this
Hi Ross,
We discussed several times about this subject and I would like to share what I
understood from exchanges with RedHat support.
It seems that kernel maintainers chose to keep the backward compatibility with
a default that cause receiving data from all multicast groups and not
