WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Network-bridge script with bonding and vlan

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Network-bridge script with bonding and vlan
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Thu, 20 Oct 2005 12:48:42 +0100
Delivery-date: Thu, 20 Oct 2005 11:45:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <002c01c5d56a$4260d8a0$0100a8c0@balls>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <002c01c5d56a$4260d8a0$0100a8c0@balls>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Oct 21, 2005 at 12:34:40AM +1300, Greg Brackley wrote:

> I'm trying to get the latest x86_64 development release running with eth0 & 
> eth1 bonded (using 802.3ad) with VLAN support.  I am trying to get a VLAN 
> support running with the intention of putting each domU on its own VLAN. 
> Given that the dom0 machine won't have an IP address on any of the domU 
> VLAN's, there should be reasonable network isolation between the domains.
> 
> I can get the bonding/vlan configuration working on a machine without Xen. 
> However I am having troubles getting the VLAN interfaces bridged correctly 
> to the xen0 and xenU domains vif interfaces. I'm unsure as to which 
> interfaces should have what MAC address, and/or how to do that.

Firstly, I would wait for the new network-bridge script to be pushed, or at
the very least use the one that Kurt Garloff posted to the list yesterday.

The topology we use is, in domain 0:

eth0 in dom0, virtual device, good IP address and physical device's MAC
|
(loopback)
|
vif0.0, virtual device bound to bridge, no IP, fake MAC
|
xenbr0, bridge interface, no IP, fake MAC
|
peth0, physical device, no IP, fake MAC

and for the guest domains

eth0, virtual device in guest domain, good IP address, and random MAC
|
(interdomain connection)
|
vif<domain id>.<device id>, in domain 0, bound to bridge, no IP, fake MAC
|
xenbr0, peth0 as above.

The physical device starts of as eth0, and then is renamed to peth0 by the
network-bridge script.

All the routing points at the interface with a good IP address.

The fake MAC address we use is FE:FF:FF:FF:FF:FF, which is this value for
reasons of compatibility with STP, but I don't understand this, I just do as
I'm told ;-)

HTH,

Ewan.

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