[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJieiUhrOjMiy3zwURD4A4t9K7P4AWPnK5-Ua7E9ZUHGW7Etbg@mail.gmail.com>
Date: Fri, 26 Oct 2018 09:27:34 -0700
From: Roopa Prabhu <roopa@...ulusnetworks.com>
To: Hangbin Liu <liuhangbin@...il.com>
Cc: netdev <netdev@...r.kernel.org>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
Jiri Pirko <jiri@...lanox.com>,
Linus Lüssing <linus.luessing@...3.blue>,
David Miller <davem@...emloft.net>
Subject: Re: [PATCH net] bridge: do not add port to router list when receives
query with source 0.0.0.0
On Thu, Oct 25, 2018 at 7:29 PM Hangbin Liu <liuhangbin@...il.com> wrote:
>
> Based on RFC 4541, 2.1.1. IGMP Forwarding Rules
>
> The switch supporting IGMP snooping must maintain a list of
> multicast routers and the ports on which they are attached. This
> list can be constructed in any combination of the following ways:
>
> a) This list should be built by the snooping switch sending
> Multicast Router Solicitation messages as described in IGMP
> Multicast Router Discovery [MRDISC]. It may also snoop
> Multicast Router Advertisement messages sent by and to other
> nodes.
>
> b) The arrival port for IGMP Queries (sent by multicast routers)
> where the source address is not 0.0.0.0.
>
> We should not add the port to router list when receives query with source
> 0.0.0.0.
>
> Reported-by: Ying Xu <yinxu@...hat.com>
> Signed-off-by: Hangbin Liu <liuhangbin@...il.com>
> ---
Acked-by: Roopa Prabhu <roopa@...ulusnetworks.com>
Powered by blists - more mailing lists