<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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> <mailto:xen-devel@lists.xensource.com> I''ve done this script to bringup> the vlans when Xen is starting the networking scripts, this must beused> 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 vlaninterface.> 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@lists.xensource.com http://lists.xensource.com/xen-devel