[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Bridge Hopping


  • To: "Jonathan Tripathy" <jonnyt@xxxxxxxxxxx>, <Xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Jeff Sturm <jeff.sturm@xxxxxxxxxx>
  • Date: Wed, 14 Jul 2010 20:10:47 -0400
  • Cc:
  • Delivery-date: Wed, 14 Jul 2010 17:13:06 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: Acsjm4TeWtXtBetlRPyF5S2n59roCAAFgnBg
  • Thread-topic: [Xen-users] Bridge Hopping

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jonathan Tripathy
> Sent: Wednesday, July 14, 2010 5:22 PM
> To: Xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Bridge Hopping
> 
> Hi Everyone,
> 
> My Xen host has 3 bridge. 1 bridge has an ip, the other 2 do not. Am I
> correct in saying that since the 2 bridges don't have an IP address,
> DomUs which are connected to that bridge cannot "hop" from one bridge
to
> the other? It is important that traffic leaving the bridge (not
destined
> for another DomU on the same bridge) goes through the firewall DomU.

If any bridge device is connected to a physical interface (e.g. eth0),
packets could also traverse out that interface into another bridge or
switch on your network.

It's helpful for me to think of Linux bridge devices as virtual
switches, and diagram them exactly the same way.  Each interface
(virtual or physical) plumbed into the bridge device functions like a
switch port.

-Jeff



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.