All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jens Osterkamp <jens@linux.vnet.ibm.com>,
	virtualization@linux-foundation.com,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Arnd Bergmann <arnd@arndb.de>, Fischer <anna.fischer@hp.com>,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	David Miller <davem@davemloft.net>,
	Gerhard Stenzel <gerhard.stenzel@de.ibm.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Patrick, Mullaney <pmullaney@novell.com>,
	Edge Virtual Bridging <evb@yahoogroups.com>,
	Anna
Subject: Re: [Bridge] [PATCH, resend] iproute2/iplink: add macvlan options for bridge mode
Date: Sat, 26 Dec 2009 11:24:11 -0800	[thread overview]
Message-ID: <20091226112411.0ab90bd4@nehalam> (raw)
In-Reply-To: <200911271157.25748.linux-kernel-owner@vger.kernel.org>

On Fri, 27 Nov 2009 10:57:25 +0000
Arnd Bergmann <arnd@arndb.de> wrote:

> Macvlan can now optionally support forwarding between its
> ports, if they are in "bridge" mode. This adds support
> for this option to "ip link add", "ip link set" and "ip
> -d link show".
> 
> The default mode in the kernel is now "vepa" mode, meaning
> "virtual ethernet port aggregator". This mode is used
> together with the "hairpin" mode of an ethernet bridge
> that the parent of the macvlan device is connected to.
> All frames still get sent out to the external interface,
> but the adjacent bridge is able to send them back on
> the same wire in hairpin mode, so the macvlan ports
> are able to see each other, which the bridge can be
> configured to monitor and control traffic between
> all macvlan instances. Multicast traffic coming in
> from the external interface is checked for the source
> MAC address and only delivered to ports that have not
> yet seen it.
> 
> In bridge mode, macvlan will send all multicast traffic
> to other interfaces that are also in bridge mode but
> not to those in vepa mode, which get them on the way
> back from the hairpin.
> 
> The third supported mode is "private", which prevents
> communication between macvlans even if the adjacent
> bridge is in hairpin mode. This behavior is closer to
> the original implementation of macvlan but stricly
> maintains isolation.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Okay, applied for next version

-- 

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <shemminger@vyatta.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Patrick McHardy <kaber@trash.net>,
	Patrick Mullaney <pmullaney@novell.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Edge Virtual Bridging <evb@yahoogroups.com>,
	Anna Fischer <anna.fischer@hp.com>,
	bridge@lists.linux-foundation.org,
	virtualization@linux-foundation.com,
	Jens Osterkamp <jens@linux.vnet.ibm.com>,
	Gerhard Stenzel <gerhard.stenzel@de.ibm.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH, resend] iproute2/iplink: add macvlan options for bridge mode
Date: Sat, 26 Dec 2009 11:24:11 -0800	[thread overview]
Message-ID: <20091226112411.0ab90bd4@nehalam> (raw)
In-Reply-To: <200911271157.25748.linux-kernel-owner@vger.kernel.org>

On Fri, 27 Nov 2009 10:57:25 +0000
Arnd Bergmann <arnd@arndb.de> wrote:

> Macvlan can now optionally support forwarding between its
> ports, if they are in "bridge" mode. This adds support
> for this option to "ip link add", "ip link set" and "ip
> -d link show".
> 
> The default mode in the kernel is now "vepa" mode, meaning
> "virtual ethernet port aggregator". This mode is used
> together with the "hairpin" mode of an ethernet bridge
> that the parent of the macvlan device is connected to.
> All frames still get sent out to the external interface,
> but the adjacent bridge is able to send them back on
> the same wire in hairpin mode, so the macvlan ports
> are able to see each other, which the bridge can be
> configured to monitor and control traffic between
> all macvlan instances. Multicast traffic coming in
> from the external interface is checked for the source
> MAC address and only delivered to ports that have not
> yet seen it.
> 
> In bridge mode, macvlan will send all multicast traffic
> to other interfaces that are also in bridge mode but
> not to those in vepa mode, which get them on the way
> back from the hairpin.
> 
> The third supported mode is "private", which prevents
> communication between macvlans even if the adjacent
> bridge is in hairpin mode. This behavior is closer to
> the original implementation of macvlan but stricly
> maintains isolation.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Okay, applied for next version

-- 

  reply	other threads:[~2009-12-26 19:24 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 22:39 [Bridge] [PATCH 0/3] macvlan: add vepa and bridge mode Arnd Bergmann
2009-11-17 22:39 ` Arnd Bergmann
2009-11-17 22:39 ` [Bridge] [PATCH 1/3] macvlan: Reflect macvlan packets meant for other macvlan devices Arnd Bergmann
2009-11-17 22:39   ` Arnd Bergmann
2009-11-18  6:30   ` [Bridge] " Eric Dumazet
2009-11-18  6:30     ` Eric Dumazet
2009-11-18  9:47     ` [Bridge] " Arnd Bergmann
2009-11-18  9:47       ` Arnd Bergmann
2009-11-18 14:37       ` [Bridge] " Eric W. Biederman
2009-11-18 14:37         ` Eric W. Biederman
2009-11-18 14:44         ` Arnd Bergmann
2009-11-18 14:44         ` [Bridge] " Arnd Bergmann
2009-11-18 14:44           ` Arnd Bergmann
2009-11-18 23:32         ` [Bridge] " Arnd Bergmann
2009-11-18 23:32           ` Arnd Bergmann
2009-11-18 23:55           ` [Bridge] " Eric W. Biederman
2009-11-18 23:55             ` Eric W. Biederman
2009-11-19 11:44             ` [Bridge] " Arnd Bergmann
2009-11-19 11:44               ` Arnd Bergmann
2009-11-19 14:47               ` [Bridge] " Patrick McHardy
2009-11-19 14:47                 ` Patrick McHardy
2009-11-18 10:00   ` [Bridge] " roel kluin
2009-11-18 10:00     ` roel kluin
2009-11-18 10:00     ` roel kluin
2009-11-17 22:39 ` [Bridge] [PATCH 2/3] macvlan: implement VEPA and private mode Arnd Bergmann
2009-11-17 22:39   ` Arnd Bergmann
2009-11-18  6:42   ` [Bridge] " Eric Dumazet
2009-11-18  6:42     ` Eric Dumazet
2009-11-18  9:48     ` [Bridge] " Arnd Bergmann
2009-11-18  9:48       ` Arnd Bergmann
2009-11-17 22:39 ` [Bridge] [PATCH 3/3] macvlan: export macvlan mode through netlink Arnd Bergmann
2009-11-17 22:39   ` Arnd Bergmann
2009-11-18  6:48   ` [Bridge] " Eric Dumazet
2009-11-18  6:48     ` Eric Dumazet
2009-11-18  9:59     ` [Bridge] " Arnd Bergmann
2009-11-18  9:59       ` Arnd Bergmann
2009-11-19 14:38       ` Patrick McHardy
2009-11-19 14:38       ` [Bridge] " Patrick McHardy
2009-11-19 14:38         ` Patrick McHardy
2009-11-19 14:47         ` Arnd Bergmann
2009-11-19 14:47         ` [Bridge] " Arnd Bergmann
2009-11-19 14:47           ` Arnd Bergmann
2009-11-18  9:59     ` Arnd Bergmann
2009-11-17 22:39 ` [Bridge] [PATCH] iplink: add macvlan options for bridge mode Arnd Bergmann
2009-11-17 22:39   ` Arnd Bergmann
2009-12-18 13:45   ` [Bridge] " Arnd Bergmann
2009-12-18 13:45     ` Arnd Bergmann
2009-12-18 17:25     ` [Bridge] " Stephen Hemminger
2009-12-18 17:25       ` Stephen Hemminger
2009-12-18 17:37       ` [Bridge] " Arnd Bergmann
2009-12-18 17:37         ` Arnd Bergmann
2009-11-17 22:56 ` [Bridge] [PATCH 0/3] macvlan: add vepa and " Arnd Bergmann
2009-11-17 22:56   ` Arnd Bergmann
2009-11-17 22:56 ` Arnd Bergmann
2009-11-18  9:01 ` [Bridge] " Mark Smith
2009-11-18  9:01   ` Mark Smith
2009-11-27 10:57 ` [Bridge] [PATCH, resend] iproute2/iplink: add macvlan options for " Arnd Bergmann
2009-11-27 10:57   ` Arnd Bergmann
2009-12-26 19:24   ` Stephen Hemminger [this message]
2009-12-26 19:24     ` Stephen Hemminger

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=20091226112411.0ab90bd4@nehalam \
    --to=shemminger@vyatta.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=gerhard.stenzel@de.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jens@linux.vnet.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pmullaney@novell.com \
    --cc=virtualization@linux-foundation.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 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.