[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190223.183651.798454146886527920.davem@davemloft.net>
Date: Sat, 23 Feb 2019 18:36:51 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: liuhangbin@...il.com
Cc: netdev@...r.kernel.org, nikolay@...ulusnetworks.com,
roopa@...ulusnetworks.com, bridge@...ts.linux-foundation.org,
yinxu@...hat.com, gregkh@...uxfoundation.org,
stable@...r.kernel.org, s.gottschall@...media-net.de,
linus.luessing@...3.blue
Subject: Re: [PATCH net] Revert "bridge: do not add port to router list
when receives query with source 0.0.0.0"
From: Hangbin Liu <liuhangbin@...il.com>
Date: Fri, 22 Feb 2019 21:22:32 +0800
> This reverts commit 5a2de63fd1a5 ("bridge: do not add port to router list
> when receives query with source 0.0.0.0") and commit 0fe5119e267f ("net:
> bridge: remove ipv6 zero address check in mcast queries")
>
> The reason is RFC 4541 is not a standard but suggestive. Currently we
> will elect 0.0.0.0 as Querier if there is no ip address configured on
> bridge. If we do not add the port which recives query with source
> 0.0.0.0 to router list, the IGMP reports will not be about to forward
> to Querier, IGMP data will also not be able to forward to dest.
>
> As Nikolay suggested, revert this change first and add a boolopt api
> to disable none-zero election in future if needed.
>
> Reported-by: Linus Lüssing <linus.luessing@...3.blue>
> Reported-by: Sebastian Gottschall <s.gottschall@...media-net.de>
> Fixes: 5a2de63fd1a5 ("bridge: do not add port to router list when receives query with source 0.0.0.0")
> Fixes: 0fe5119e267f ("net: bridge: remove ipv6 zero address check in mcast queries")
> Signed-off-by: Hangbin Liu <liuhangbin@...il.com>
Applied and queued up for -stable, thanks.
Powered by blists - more mailing lists