[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150813160626.GF32484@lunn.ch>
Date: Thu, 13 Aug 2015 18:06:26 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Philip Downey <pdowney@...cade.com>
Cc: David Miller <davem@...emloft.net>,
"kuznet@....inr.ac.ru" <kuznet@....inr.ac.ru>,
"jmorris@...ei.org" <jmorris@...ei.org>,
"yoshfuji@...ux-ipv6.org" <yoshfuji@...ux-ipv6.org>,
"kaber@...sh.net" <kaber@...sh.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] IGMP: Inhibit reports for local multicast groups
On Thu, Aug 13, 2015 at 02:48:23PM +0000, Philip Downey wrote:
> Hi David
> Thanks for taking the time to review and comment.
> This is my first upstream request so please forgive any ignorance on my part. I have added a new proposed commit wording below with a view to agreeing the content before resubmitting the patch.
> I hope it is sufficient to address your concerns.
>
> IGMP: Inhibit reports for local multicast groups
>
> The range of addresses between 224.0.0.0 and 224.0.0.255
> inclusive, is reserved for the use of routing protocols and other
> low-level topology discovery or maintenance protocols, such as
> gateway discovery and group membership reporting. Multicast
> routers should not forward any multicast datagram with destination
> addresses in this range, regardless of its TTL.
>
> Currently, IGMP reports are generated for this reserved range of
> addresses even though a router will ignore this information since
> it has no purpose.
Hi Philip
What about switches which are doing IGMP snooping?
Andrew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists