Re: [Xen-users] network-bridge with vlan and problems ...

[christian gattermair <christian.gattermair@xxxxxxx>]

hi janko!

your script works perfect for me - thanks :-)

with friendly greetings,

christian

Am Dienstag, 18. September 2007 schrieb Janko Harej:
> Hi,
>
> I don't know if this is the right way, but I've created my own script to
> create bridges. I leave /etc/xen/script/network-bridge to create default
> bridge and use skript create_bridge to create bridge for each vlan
>
> #!/bin/sh
> # usage: ./create_bridge vlan_number
>
> bridge=$1
> bridge="xenbr${bridge}"
> vlan=$1
> vlan="vlan${vlan}"
> echo createing ${bridge}
> brctl addbr ${bridge}
> brctl stp ${bridge} off
> brctl setfd ${bridge} 0
> brctl addif ${bridge} ${vlan}
> ip link set ${bridge} up
>
> Script is for suse. I guess you must change line vlan=... to
> vlan=eth0.${vlan} for Debian? Like I sad, I don't know if this is the right
> way...
>
> bye
>
> 2007/9/18, christian gattermair <christian.gattermair@xxxxxxx>:
> > hi!
> >
> > i try to set up my xen enviroment to a vlan bridge ...
> >
> > /etc/xen/scripts/network-bridge start netdev=eth4.850 bridge=xen-br850
> > antispoof=no
> >
> > Link veth4.850 is missing.
> > This may be because you have reached the limit of the number of
> > interfaces that the loopback driver supports.  If the loopback driver is
> > a module, you
> > may raise this limit by passing it as a parameter (nloopbacks=<N>); if
> > the driver is compiled statically into the kernel, then you may set the
> > parameter
> > using netloop.nloopbacks=<N> on the domain 0 kernel command line.
> >
> > ip link show | grep veth
> > 3: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 5: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 7: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 9: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 11: veth4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 13: veth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 15: veth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 17: veth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 19: veth8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 21: veth9: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 23: veth10: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 25: veth11: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 27: veth12: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 29: veth13: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 31: veth14: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> > 33: veth15: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
> >
> > my debian networking config:
> >
> > iface xen-br850 inet manual
> >         up ifconfig eth4 up
> >         up vconfig add eth4 850
> >         up /sbin/ifconfig eth4.850 up
> >         up ifconfig eth4.850 192.168.1.15 netmask 255.255.255.192
> >         up route add default gw 192.168.1.1
> >         up /etc/xen/scripts/network-bridge start netdev=eth4.850
> > bridge=xen-br850 antispoof=no
> >         down /etc/xen/scripts/network-bridge stop netdev=eth4.850
> > bridge=xen-br850 antispoof=no
> >         down vconfig rem eth4.850
> >
> > how can i create veth4.850???
> >
> > eth4.850 (the vlan interface) is up and runs.
> >
> > thanks for any hint!
> >
> > with friendly greetings,
> >
> > christian
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users



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