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

[Xen-devel] Automated vlan startup script


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Luis Vinay" <luisvinay@xxxxxxxxx>
  • Date: Thu, 23 Nov 2006 14:36:05 -0300
  • Delivery-date: Fri, 24 Nov 2006 01:31:08 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=oY4S6YrK1MtR0ESXY+pMBNIjmvSD9vProNyBD2KwiRJTRAOoiYwc9d/8QNKAdXwDcWV9n/2kubnBe5kKkGfr7fgZmvhvAsf/UKBjSNdSfnmQng6l1EdsjgMwG3AzCMCUzdZAvqC7y2u2tAJLlayXpm5ARH/VgEjLymDbzhPd3PA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I've done this script to bring up the vlans when Xen is starting the networking scripts, this must be used instead of  /etc/xen/scripts/network-bridge, needs very minimal "configuration", and every thing is commented inside the script

for example:

if you set the variables like this inside the script:

VLANSLIST="41 101"
TRUNKDEVNUMS="0 2"

you will get the following peths devices

peth041, peth0101, peth241 and peth2101

this is because I removed the dot "." when vconfig adds the vlan interface.
And the following bridges to be used with the VMs:

xenbr041, xenbr0101, xenbr241 and xenbr2101

Regards,

Luis Vinay

Attachment: network-bridge-vlans
Description: Binary data

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

 


Rackspace

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