From: Cong Wang <amwang@redhat.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
"David S. Miller" <davem@davemloft.net>,
Adam Baker <linux@baker-net.org.uk>
Subject: Re: [Bridge] [Patch net] bridge: do not expire mdb entry when bridge still uses it
Date: Mon, 11 Mar 2013 09:44:11 +0800 [thread overview]
Message-ID: <1362966251.17872.2.camel@cr0> (raw)
In-Reply-To: <20130308112438.GA29924@gondor.apana.org.au>
On Fri, 2013-03-08 at 19:24 +0800, Herbert Xu wrote:
> On Fri, Mar 08, 2013 at 03:26:21PM +0800, Cong Wang wrote:
> >
> > Hmm, what the user experiences is the multicast traffic between the
> > bridge and some port is broken. Isn't this expected to work by default?
>
> Oh I'm not arguing that this isn't a bug. I'm trying to ensure
> that we come up with the right fix.
Do you have any idea of a better fix?
>
> > Or we can just change the default value of br->multicast_router to 2?
>
> No because that will cause all sorts of stuff to be thrown at
> the host.
>
OK.
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Cong Wang <amwang@redhat.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
"David S. Miller" <davem@davemloft.net>,
Adam Baker <linux@baker-net.org.uk>
Subject: Re: [Patch net] bridge: do not expire mdb entry when bridge still uses it
Date: Mon, 11 Mar 2013 09:44:11 +0800 [thread overview]
Message-ID: <1362966251.17872.2.camel@cr0> (raw)
In-Reply-To: <20130308112438.GA29924@gondor.apana.org.au>
On Fri, 2013-03-08 at 19:24 +0800, Herbert Xu wrote:
> On Fri, Mar 08, 2013 at 03:26:21PM +0800, Cong Wang wrote:
> >
> > Hmm, what the user experiences is the multicast traffic between the
> > bridge and some port is broken. Isn't this expected to work by default?
>
> Oh I'm not arguing that this isn't a bug. I'm trying to ensure
> that we come up with the right fix.
Do you have any idea of a better fix?
>
> > Or we can just change the default value of br->multicast_router to 2?
>
> No because that will cause all sorts of stuff to be thrown at
> the host.
>
OK.
Thanks!
next prev parent reply other threads:[~2013-03-11 1:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 2:07 [Bridge] [Patch net] bridge: do not expire mdb entry when bridge still uses it Cong Wang
2013-03-08 2:07 ` Cong Wang
2013-03-08 2:31 ` [Bridge] " Herbert Xu
2013-03-08 2:31 ` Herbert Xu
2013-03-08 2:44 ` [Bridge] " Cong Wang
2013-03-08 2:44 ` Cong Wang
2013-03-08 2:47 ` [Bridge] " Herbert Xu
2013-03-08 2:47 ` Herbert Xu
2013-03-08 4:06 ` [Bridge] " Cong Wang
2013-03-08 4:06 ` Cong Wang
2013-03-08 4:08 ` [Bridge] " Herbert Xu
2013-03-08 4:08 ` Herbert Xu
2013-03-08 7:26 ` [Bridge] " Cong Wang
2013-03-08 7:26 ` Cong Wang
2013-03-08 11:24 ` [Bridge] " Herbert Xu
2013-03-08 11:24 ` Herbert Xu
2013-03-11 1:44 ` Cong Wang [this message]
2013-03-11 1:44 ` Cong Wang
2013-03-19 1:12 ` [Bridge] " Cong Wang
2013-03-19 1:12 ` Cong Wang
2013-03-09 22:46 ` [Bridge] " Adam Baker
2013-03-09 22:46 ` Adam Baker
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=1362966251.17872.2.camel@cr0 \
--to=amwang@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=linux@baker-net.org.uk \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.