|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] 802.1Q VLAN vs xenbr0
Hello guy's,
I have used vlans in my virtual environment with success but I needed
to change the network-bridge script to make this set up to work
because the original network-bridge not work with vlan. This is my
network-script changed:
http://msinhore.xen-br.org/scripts/network-bridge
I also created a new xen script called network-bridge-multi to create
multi bridges up bonded interfaces with vlan tag:
#! /bin/bash
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=2 netdev=bond0.2 bridge=vlanbr2
"$dir/network-bridge" "$@" vifnum=3 netdev=bond0.3 bridge=vlanbr3
"$dir/network-bridge" "$@" vifnum=4 netdev=bond0.4 bridge=vlanbr4
"$dir/network-bridge" "$@" vifnum=5 netdev=bond0.5 bridge=vlanbr5
In this example, I have used the bridge name 'vlanbr' + tag_id. You
can change it to xenbr0 in another interface tagged. Example:
dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0.272 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=1 netdev=eth0.273 bridge=xenbr1
[...]
To use this set up you need change the network-script var in
/etc/xen/xend-config.sxp file to:
(network-script network-bridge-multi)
Now, if you need only one interface, change only the 'network-script' to:
(network-script 'network-bridge netdev=eth0.272 bridge=xenbr0')
Remember, the original network-script do not work with vlan.
Regards,
--
Marco Sinhoreli
On Mon, Mar 10, 2008 at 3:55 PM, Luciano Rocha <strange@xxxxxxxxxxxxx> wrote:
> On Mon, Mar 10, 2008 at 06:48:12PM +0000, Luciano Rocha wrote:
> > On Mon, Mar 10, 2008 at 03:24:45PM -0300, Tiago Cruz wrote:
> > > Hello!
> > >
> > > On Thu, 2008-03-06 at 09:38 +0100, Dariusz Malec wrote:
> > >
> > > > What does it mean "you lost your vlan"? if you have assign an ip addres
> > > > to eth0.260 interface you will lost a communication when you add this
> > > > interface to the bridge.
> > >
> > > Yep. I was using ssh to manage one remote computer, and I lost this
> > > connection when I've added the bridge.
> > >
> > >
> > > > Try to configure eth0.260 with no ip addr assigned, add this interface
> > > > to the bridge and assign ip address to the xenbr0 interface. You should
> > > > be able to ping your hosts in vlan260 from dom0.
> > >
> > > I've tried a lot of combination, and my final solution was:
> > >
> > > - Does not use any IP/Alias on bridge interface
> > > - Use another VLAN (TAG 272 on my example) to management
> > >
> > > Some like this:
> > > http://wiki.xen-br.org/images/4/4b/Xen.png
> > >
> >
> > I use the attached script for managing the bridges. Note that I use the
> > format VLAN_PLUS_VID_NO_PAD for the vlan interfaces (eg: vlan272).
> <snip>
>
> I'm getting forgetful in my old age.
>
> Files now really attached.
>
> --
> lfr
> 0/0
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
--
Marco Sinhoreli
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|