From: Yan Wang <gg_wangyan@hotmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fwd: bridge should flood non-IPv4-multicast ethernet frames
Date: Thu, 9 Feb 2012 20:38:53 +0000 (UTC) [thread overview]
Message-ID: <loom.20120209T210111-420@post.gmane.org> (raw)
In-Reply-To: <CAA93jw5q-UET1NH3Cu15UbH6T_kqNCUdW_-yzYqPPu5nre+xTA@mail.gmail.com>
Dave Taht <dave.taht@...> writes:
> 2. Check that the Ethertype is 0x800 (IPv4), and if it is not, always
> flood the frame so we don't break non-IPv6-multicast frames being
> bridged.
>
> 3. Do both of the above, the key point being that IPv6 multicast
> frames (33:33:xx:xx:xx:xx), along with any other ethernet multicast
> frames that aren't supported by the current bridge snooping code,
> should always be flooded unconditionally. IS-IS for example uses
> 01:80:C2:00:00:14 and 01:80:C2:00:00:15.
Hi,
I applied your patch to kernel 3.2.0.
The test result indicated that bridge didn't flood IPv6-multicast ethernet
frames.
I set up 2 UML, they can communicated via host bridge.
I appiled the patch in the host.
But I still can't see IPv6 multicast package coming from other UML.
Thanks,
Yan
prev parent reply other threads:[~2012-02-09 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110913200027.GQ28007@angus.ind.WPI.EDU>
2011-09-13 21:51 ` Dave Taht
2012-02-09 20:38 ` Yan Wang [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120209T210111-420@post.gmane.org \
--to=gg_wangyan@hotmail.com \
--cc=bloat@lists.bufferbloat.net \
/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