From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Paul Congdon \(UC Davis\)" Subject: Re: [evb] Re: [PATCH][RFC] net/bridge: add basic VEPA support Date: Fri, 7 Aug 2009 12:44:06 -0700 Message-ID: <005101ca1797$70dcf5b0$5296e110$@edu> References: <0199E0D51A61344794750DC57738F58E67D2DCECBB@GVW1118EXC.americas.hpqcorp.net> <20090806210002.75beb7c6@nehalam> <200908071329.44437.arnd@arndb.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6106794152065959331==" Cc: "'Fischer, Anna'" , netdev@vger.kernel.org, bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, "'Or Gerlitz'" , adobriyan@gmail.com, davem@davemloft.net To: , "'Stephen Hemminger'" Return-path: In-Reply-To: <200908071329.44437.arnd@arndb.de> Content-Language: en-us List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: bridge-bounces@lists.linux-foundation.org Errors-To: bridge-bounces@lists.linux-foundation.org List-Id: netdev.vger.kernel.org This is a multipart message in MIME format. --===============6106794152065959331== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0052_01CA175C.C47E1DB0" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_0052_01CA175C.C47E1DB0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. ------=_NextPart_000_0052_01CA175C.C47E1DB0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 =3D=3D=3D 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.

 

------=_NextPart_000_0052_01CA175C.C47E1DB0-- --===============6106794152065959331== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bridge mailing list Bridge@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/bridge --===============6106794152065959331==--