OpenVZ Forum - RDF feed
type: channel
items: Migration with bridged tagged vlan interfaces?
items: Re: Migration with bridged tagged vlan interfaces?

Migration with bridged tagged vlan interfaces?
type: item
description: We're using bridged interfaces with veth. It seems our bridge configuration isn't carrying over the bridge config. The way I'm doing this on the originating machine is with a Red Hat style networking config file: [root@fvmp-ovz0000 network-scripts]# cat ifcfg-veth4.0 DEVICE=veth4.0 ONBOOT=yes STARTMODE=onboot BRIDGE=br3.1632 which ensures the veth interface is associated with the right vlan bridge interface. But this doesn't seem to carry over...well, the veth4.0 interface is created, but this interface isn't associated with the correct bridge vlan interface. Is there another way to accomplish this elegantly? I have a feeling I'm going about this the hard way perhaps. Thanks
creator: xxedgexx
date: 2010-06-11T19:34:54-00:00

Re: Migration with bridged tagged vlan interfaces?
type: item
description: Hi, I think new versions of OpenVZ might have some improvements; in my case I am using an old version (from Debian Lenny) and I did it with scripts (can be found in the wiki): 1.) config file NETIF="ifname=eth0,mac=00:18:51:C5:33:F8,host_ifname=veth200.0,host_mac=00:18:51:0D:89:B9" CONFIG_CUSTOMIZED="yes" VZHOSTBR="br-lan" CONFIG_CUSTOMIZED tells OpenVZ to execute a script (see below) and VZHOSTBR tells the script to which bridge the device should be assigned. The script is configured in vz.conf via: EXTERNAL_SCRIPT="/usr/local/sbin/vznetaddbr" If you need more details on this please let me know! The VLANs itself are assigned to the VLANs directly on the host. In my case in Debian: iface br-wan inet manual bridge_ports eth0.3 bridge_maxwait 0 iface br-lan inet static address 192.168.200.1 netmask 255.255.255.0 gateway 192.168.200.120 bridge_ports eth0.2 bridge_maxwait 0 iface br-stfg inet manual bridge_ports eth0.4 bridge_maxwait 0 iface vlan1 inet static vlan-raw-device eth0 address 10.7.1.10 netmask 255.255.255.0 As you can see, VLAN 3 and VLAN 4 do not have an interface on the host but are just used to "export" these interfaces to some OpenVZ guests. This way I have WAN and internal guests together. Regards, divB
creator: divB
date: 2010-06-24T18:39:56-00:00