[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190122.171832.1199555290239452595.davem@davemloft.net>
Date: Tue, 22 Jan 2019 17:18:32 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: linus.luessing@...3.blue
Cc: netdev@...r.kernel.org, roopa@...ulusnetworks.com,
nikolay@...ulusnetworks.com, kuznet@....inr.ac.ru,
yoshfuji@...ux-ipv6.org, bridge@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/4] bridge: implement Multicast Router
Discovery (RFC4286)
From: Linus Lüssing <linus.luessing@...3.blue>
Date: Mon, 21 Jan 2019 07:26:24 +0100
> This patchset adds initial Multicast Router Discovery support to
> the Linux bridge (RFC4286). With MRD it is possible to detect multicast
> routers and mark bridge ports and forward multicast packets to such routers
> accordingly.
>
> So far, multicast routers are detected via IGMP/MLD queries and PIM
> messages in the Linux bridge. As there is only one active, selected
> querier at a time RFC4541 ("Considerations for Internet Group Management
> Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping
> Switches") section 2.1.1.a) recommends snooping Multicast Router
> Advertisements as provided by MRD (RFC4286).
>
>
> The first two patches are refactoring some existing code which is reused
> for parsing the Multicast Router Advertisements later in the fourth
> patch. The third patch lets the bridge join the all-snoopers multicast
> address to be able to reliably receive the Multicast Router
> Advertisements.
...
Series applied, thanks!
Powered by blists - more mailing lists