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-users

Re: [Xen-users] Bridging and VLANs 802.1Q trunk

To: Javier Guerra <javier@xxxxxxxxxxx>
Subject: Re: [Xen-users] Bridging and VLANs 802.1Q trunk
From: Timo Virtaneva <timo@xxxxxxxxxxxx>
Date: Thu, 9 Mar 2006 06:13:55 +0200 (EET)
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 09 Mar 2006 12:56:18 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi

It does not work. You can get the VLAN tagging working with standard network 
sripts. Greg has  made some good examples.


http://lists.xensource.com/archives/html/xen-devel/2005-10/msg01174.html
http://lists.xensource.com/archives/html/xen-devel/2006-01/msg00562.html

However the traffic does not go through without the patch for the ethtool. I 
hope that someone would put the modifications to standard package. I never 
managed to create rpm-package with required modifications.

-- Timo 

----- Alkuperäinen viesti -----
From: Javier Guerra <javier@xxxxxxxxxxx>
To: xen-users@xxxxxxxxxxxxxxxxxxx
Lähetetyt: 9. maaliskuuta 2006 0:45:14 GMT+0200
Aihe: Re: [Xen-users] Bridging and VLANs 802.1Q trunk

On Wednesday 08 March 2006 5:38 pm, Brian Wong wrote:
> This doesnt seem to work because the script brings down the 'netdev'
> and when that device is 'eth0.X' where X is the vlan, it totally
> removes it. Then the script later tries to rename it to peth0.X but
> the 'eth0.X' no longer exists.

i believe (can be wrong) that the xen scripts have two main parts: one for 
initial setup, and one for adding each domU to the right bridges.

try to totally disable the initial setup script.  don't let it confuse 
anything.  then write your own script that sets all the VLAN devices, and all 
needed bridges.  try to make it set all you need, ready to receive the domU's 
vifs.  then the second part of the Xen scripts should work with little or no 
modifications.

after you get it working, it might be wise to add some of the usual xen 
renaming scheme to your initial script, and replace the Xen provided with 
yours.


-- 
Javier


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