From: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org,
Hayato Kakuta <kakuta.hayato@oss.ntt.co.jp>
Subject: Re: IGMP snooping: set mrouters_only flag for IPv4 traffic properly
Date: Wed, 15 Jun 2011 14:09:45 +0900 [thread overview]
Message-ID: <1308114585.4256.1.camel@nexus.oss.ntt.co.jp> (raw)
In-Reply-To: <20110614132212.2ac83c6c@s6510.ftrdhcpuser.net>
On Tue, 2011-06-14 at 13:22 -0400, Stephen Hemminger wrote:
> On Mon, 13 Jun 2011 12:02:43 +0900
> Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp> wrote:
>
> > Upon reception of a IGMP/IGMPv2 membership report the kernel sets the
> > mrouters_only flag in a skb that may be a clone of the original skb, which
> > means that sometimes the bridge loses track of membership report packets (cb
> > buffers are tied to a specifici skb and not shared) and it ends up forwading
> > join requests to the bridge interface.
> >
> > This can cause unexpected membership timeouts and intermitent/permanent loss of connectivity as described in RFC 4541 [2.1.1. IGMP Forwarding Rules]:
> >
> > A snooping switch should forward IGMP Membership Reports only to
> > those ports where multicast routers are attached.
> > [...]
> > Sending membership reports to other hosts can result, for IGMPv1
> > and IGMPv2, in unintentionally preventing a host from joining a
> > specific multicast group.
> >
> >
> > Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp>
> > Tested-by: Hayato Kakuta <kakuta.hayato@oss.ntt.co.jp>
> > ---
> >
> > diff -urNp linux-3.0-rc2-orig/net/bridge/br_multicast.c linux-3.0-rc2/net/bridge/br_multicast.c
> > --- linux-3.0-rc2-orig/net/bridge/br_multicast.c 2011-06-09 13:34:04.164261031 +0900
> > +++ linux-3.0-rc2/net/bridge/br_multicast.c 2011-06-09 20:04:23.473930447 +0900
> > @@ -1424,7 +1424,7 @@ static int br_multicast_ipv4_rcv(struct
> > switch (ih->type) {
> > case IGMP_HOST_MEMBERSHIP_REPORT:
> > case IGMPV2_HOST_MEMBERSHIP_REPORT:
> > - BR_INPUT_SKB_CB(skb2)->mrouters_only = 1;
> > + BR_INPUT_SKB_CB(skb)->mrouters_only = 1;
> > err = br_ip4_multicast_add_group(br, port, ih->group);
> > break;
> > case IGMPV3_HOST_MEMBERSHIP_REPORT:
>
> Acked-by: Stephen Hemminger <shemminger@vyatta.com>
Can I take that as an acked-by for the IPv6 patch too?
Thanks,
Fernando
next prev parent reply other threads:[~2011-06-15 5:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 2:59 [PATCH 0/2] IGMP snooping: set mrouters_only flag properly Fernando Luis Vazquez Cao
2011-06-13 3:02 ` IGMP snooping: set mrouters_only flag for IPv4 traffic properly Fernando Luis Vazquez Cao
2011-06-14 17:22 ` Stephen Hemminger
2011-06-15 5:09 ` Fernando Luis Vázquez Cao [this message]
2011-06-13 3:21 ` [PATCH 2/2] IGMP snooping: set mrouters_only flag for IPv6 " Fernando Luis Vazquez Cao
2011-06-14 1:01 ` [PATCH 0/2] IGMP snooping: set mrouters_only flag properly Fernando Luis Vázquez Cao
2011-06-14 1:04 ` [PATCH 1/2] IGMP snooping: set mrouters_only flag for IPv4 traffic properly Fernando Luis Vázquez Cao
2011-06-17 3:14 ` David Miller
2011-06-17 4:39 ` Fernando Luis Vazquez Cao
2011-06-14 1:06 ` [PATCH 2/2] IGMP snooping: set mrouters_only flag for IPv6 " Fernando Luis Vázquez Cao
2011-06-17 3:14 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1308114585.4256.1.camel@nexus.oss.ntt.co.jp \
--to=fernando@oss.ntt.co.jp \
--cc=herbert@gondor.apana.org.au \
--cc=kakuta.hayato@oss.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).