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

RE: [Xen-devel] Automated vlan startup script


  • To: "Luis Vinay" <luisvinay@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Fri, 24 Nov 2006 10:44:13 -0000
  • Delivery-date: Fri, 24 Nov 2006 02:44:59 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccPq2zr7drT/fZPQYmN26bLRwpcAwACV9lw
  • Thread-topic: [Xen-devel] Automated vlan startup script

> <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx> 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:

Out of interest, why remove the dots?

I wander whether we'd be better off modifying the bridge script to take
netdevs that may include vlans that should be created e.g.
network-bridge netdev=eth0.41 bridge=xenbr0.41

Thanks,
Ian







_______________________________________________
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®.