Re: [evb] Re: [PATCH][RFC] net/bridge: add basic VEPA support

From: "Paul Congdon \(UC Davis\)" <ptcongdon@ucdavis.edu>
To: <evb@yahoogroups.com>,
	"'Stephen Hemminger'" <shemminger@linux-foundation.org>
Cc: "'Fischer, Anna'" <anna.fischer@hp.com>,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	"'Or Gerlitz'" <ogerlitz@voltaire.com>,
	adobriyan@gmail.com, davem@davemloft.net
Subject: Re: [evb] Re: [PATCH][RFC] net/bridge: add basic VEPA support
Date: Fri, 7 Aug 2009 12:44:06 -0700	[thread overview]
Message-ID: <005101ca1797$70dcf5b0$5296e110$@edu> (raw)
In-Reply-To: <200908071329.44437.arnd@arndb.de>

[-- Attachment #1.1: Type: text/plain, Size: 862 bytes --]

Arnd,

I don't think your scheme works too well because broadcast packet coming
from other interfaces on br0 would get replicated and sent across the wire
to ethB multiple times.

Paul

That way you should be able to do something
like:

Host A Host B

/- nalvcam0 -\ /- macvlan0 - 192.168.1.1
br0 -| |- ethA === ethB -|
\- nalvcam1 -/ \- macvlan1 - 192.168.1.2

Now assuming that macvlan0 and macvlan1 are in different
network namespaces or belong to different KVM guests, these
guests would be able to communicate with each other through
the bridge on host A, which can set the policy (using ebtables)
for this communication and get interface statistics on its
nalvcam interfaces. Also, instead of having the br0, Host A could
assign an IP addresses to the two nalvcam interfaces that host
B has, and use IP forwarding between the guests of host B.

[-- Attachment #1.2: Type: text/html, Size: 9293 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Bridge mailing list
Bridge@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/bridge