[Bridge] net: Export IGMP/MLD message validation code
tobias.powalowski at googlemail.com
Tue Sep 8 12:47:06 UTC 2015
Am 08.09.2015 um 13:22 schrieb Linus Lüssing:
> Hi Tobias,
> On Tue, Sep 08, 2015 at 08:36:02AM +0200, Tobias Powalowski wrote:
>> Am 08.09.2015 um 04:24 schrieb Linus Lüssing:
>>> Hi tpowa,
>>> Thanks for your feedback.
>>> On Mon, Sep 07, 2015 at 02:46:27PM +0200, Tobias Powalowski wrote:
>>>> This commit introduces a weird behaviour on my dlna server.
>>> Did you experience this on the released 4.2 kernel or on a 4.2 release
>> This was on 4.2 final release.
>>>> This commit was merged into 4.2 series, which makes my dlna services
>>>> disappear real soon after starting from discovering from other clients.
>>>> Localhost seems not to be affected but every external discovery is broken.
>>>> The dlna services run on a bridge device. Mythtv and Minidlna both
>>>> disappear after some minutes of running.
>>>> Git bisect shows first commit as reason, trying now a 4.2 with those 3
>>>> patches reverted:
>>>> Do you need any more information to get this really weird bug fixed?
>>> If you have this issue with the vanilla, released 4.2 kernel, then
>>> a "tcpdump -i br0 'icmp6 or ip6 proto 0'" for about five minutes and
>>> a "bridge mdb show" would be helpful.
>> Here comes the next interesting thing:
>> If I run
>> tcpdump -i br0 'ip6 proto 0'
>> all is working fine.
> This rings a bell. Somebody told me about such weird behaviour
> back in March already on IRC, so way before 4.2 or any commits you've
> cited. Unfortunately I wasn't able to reproduce it back then and
> didn't hear from him on this issue anymore - I'll try to get an update
> from him.
> br_multicast.c has no knowledge about promiscious mode. Maybe
> someone else from the bridge mailinglist might have an idea how
> prom. mode on the bridge interface could affect things?
>> If I stop this task it stops showing the dlna services.
>> promiscious mode enabled doesn't make it fail.
>> [ 1212.138260] device br0 entered promiscuous mode
>> [ 1246.908027] device br0 left promiscuous mode
>> does not work
>> bridge mdb show
>> dev br0 port enp2s0 grp 184.108.40.206 temp
>> dev br0 port enp2s0 grp 220.127.116.11 temp
>>> Also which distros are the dlna server and dlna client running,
>>> how are they connected?
>> I have only archlinux environments, all external connections are affected.
>> My Panasonic TV is not working and my Sony Xperia Z1 compact mobile
>> phones are also not working.
>> VLC on Windows 7 shows the same. So this is a generic issue I guess.
> Just to check two (sometimes too) "obvious" points: No ebtables or iptables
> on the device with the bridge? DLNA server isn't bound to enp2s0
> and is either unbound (binds to 0.0.0.0) or binds to br0?
DLNA is not bound to any interface ebtables is not installed and
iptables don't show any active rule.
Any output of a network command which might help?
Thanks for investigation on this bug.
Archlinux Developer & Package Maintainer (tpowa)
tpowa at archlinux.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: OpenPGP digital signature
More information about the Bridge