I used the guide available at: http://this.is/promazin/?p=page&ID=1 and it worked wonders for me. The only thing "not covered" (not implying that the guide should) is that Cisco uses VLAN1 for management and that VLAN should therefore not be tagged. I use VLAN1 for data (because of legacy reasons) and therefore had to change the config examples provided from:

auto lo
iface lo inet loopback

auto eth0 vlan2 vlan10 vlan20

# iface eth has to be up with no ip number

iface eth0 inet static
        address 0.0.0.0
        netmask 0.0.0.0
        vlan_raw_device eth0

iface vlan2 inet static
        address 172.201.221.17
        netmask 255.255.255.224
        gateway 172.201.221.17
        vlan_raw_device eth0
...
--
to
--
auto lo
iface lo inet loopback

auto eth0 vlan2 vlan10 vlan20

# iface eth has to be up with no ip number

iface eth0 inet static
        address 0.0.0.0
        netmask 0.0.0.0
        vlan_raw_device eth0

iface vlan2 inet static
        address 172.201.221.17
        netmask 255.255.255.224
        gateway 172.201.221.17
        vlan_raw_device eth0

iface vlan10 inet static
        address 172.201.222.4
        netmask 255.255.254.0
        gateway 172.201.222.1
        vlan_raw_device eth0

iface vlan20 inet static
        address 192.168.1.254
        netmask 255.255.255.0
        gateway 192.168.1.1
        vlan_raw_device eth0

---

to

--
auto lo
iface lo inet loopback

auto eth0 vlan2 vlan10 vlan20

# iface eth has to be up with no ip number

iface eth0 inet static
        address 172.201.221.17
        netmask 255.255.255.224
        gateway 172.201.221.17

iface vlan10 inet static
        address 172.201.222.4
        netmask 255.255.254.0
        gateway 172.201.222.1
        vlan_raw_device eth0

iface vlan20 inet static
        address 192.168.1.254
        netmask 255.255.255.0
        gateway 192.168.1.1
        vlan_raw_device eth0
--

and it worked wonderfully!
Basically what this does is to define eth0 as a regular interface and the VLANx interfaces as VLANs on a raw_device...

HTH

A.

On 28.3.2006, at 13:59, Chuck wrote:

is there any in-depth guide/documentation to fully explain construction of
vlans with respect to vservers?

my boss now wants to change our "unique port" network vlan structure to
multiple vlans on a single port.


--

Chuck




_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver

_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to