From: "Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu>
To: "'Fischer, Anna'" <anna.fischer@hp.com>,
"'Arnd Bergmann'" <arnd@arndb.de>
Cc: "'Stephen Hemminger'" <shemminger@linux-foundation.org>,
<bridge@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
<evb@yahoogroups.com>, <davem@davemloft.net>, <kaber@trash.net>,
<adobriyan@gmail.com>, "'Eric Biederman'" <ebiederm@xmission.com>
Subject: RE: [PATCH][RFC] net/bridge: add basic VEPA support
Date: Tue, 11 Aug 2009 07:55:04 -0700 [thread overview]
Message-ID: <001001ca1a93$b6e50ee0$24af2ca0$@edu> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E6D6AE99C53@GVW1118EXC.americas.hpqcorp.net>
> >
> > The patch from Eric Biederman to allow macvlan to bridge between
> > its slave ports is at
> >
> > http://kerneltrap.org/mailarchive/linux-netdev/2009/3/9/5125774
>
> Looking through the discussions here, it does not seem as if a decision
> was made to integrate those patches, because they would make the
> macvlan
> interface behave too much like a bridge. Also, it seems as if there was
> still a problem with doing multicast/broadcast delivery when enabling
> local VM-to-VM communication. Is that solved by now?
>
Also, is there a solution, or plans for a solution, to address macvtap
interfaces that are set to 'promiscuous' mode? It would seem fairly easy to
support this for interfaces that are simply trying to listen to the port
(e.g. Wireshark). If the port was being used by something like a firewall
then the VEPA filtering doesn't work too well.
Paul
next prev parent reply other threads:[~2009-08-11 14:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 17:33 [PATCH][RFC] net/bridge: add basic VEPA support Fischer, Anna
2009-08-07 4:00 ` Stephen Hemminger
2009-08-07 11:29 ` Arnd Bergmann
2009-08-07 19:44 ` [evb] " Paul Congdon (UC Davis)
2009-08-10 15:23 ` Arnd Bergmann
2009-08-10 15:59 ` Fischer, Anna
2009-08-10 16:16 ` Arnd Bergmann
2009-08-07 18:58 ` Paul Congdon (UC Davis)
2009-08-08 9:49 ` Arnd Bergmann
2009-08-10 13:16 ` Fischer, Anna
2009-08-10 15:06 ` Arnd Bergmann
2009-08-10 15:07 ` Arnd Bergmann
2009-08-11 14:30 ` Fischer, Anna
2009-08-11 14:55 ` Paul Congdon (UC Davis) [this message]
2009-08-12 13:19 ` Arnd Bergmann
2009-08-12 14:32 ` Fischer, Anna
2009-08-12 16:27 ` Arnd Bergmann
2009-08-13 22:11 ` Fischer, Anna
2009-08-13 22:24 ` Fischer, Anna
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='001001ca1a93$b6e50ee0$24af2ca0$@edu' \
--to=ptcongdon@ucdavis.edu \
--cc=adobriyan@gmail.com \
--cc=anna.fischer@hp.com \
--cc=arnd@arndb.de \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=evb@yahoogroups.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=virtualization@lists.linux-foundation.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 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).