From: Dennis Roos (dennis_at_intouch.net)
Date: Wed 13 Jul 2005 - 12:30:36 BST
On Wed, 2005-07-13 at 12:46 +0200, Alberto Cammozzo wrote:
> I am setting up a vserver with vlans: each vserver one or
> more dot1q vlans.
So do I ;)
> Seems to work fine, except that the "vserver start" insists
> on giving the interface a fake 127.0.0.1 address,
> even if it has an interface configuration in
> and /etc/vservers/XX/interfaces/dev has "eth0.2" in it.
I recall having to set at least /etc/vservers/XX/interfaces/name as
well, however I am unsure if it is really necessary though. It creates
named aliases on the 802.1Q interfaces.
> To have it working properly I have to deconfigure and
> reconfigure by hand the interface from the host server
> after the vserver is started.
Try upgrading to a more recent version of the tools first. I
have had issues with 802.1Q vlans in older versions as well,
upgrading to a more recent version solved the problems I had.
> Seems like this is a known and correct (?) behavior since 2003:
ip addr list gives me:
7: eth1.1096: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether 00:80:3f:04:1b:59 brd ff:ff:ff:ff:ff:ff
inet 127.0.0.1/8 brd 127.255.255.255 scope host eth1.1096
inet xxx.xxx.xxx.21/28 brd 18.104.22.168 scope global eth1.1096:0VS1
inet xxx.xxx.xxx.22/28 brd 22.214.171.124 scope global secondary
> What do I have to do to give eth0.2 a different IP address?
> # vserver-info
> Kernel: 126.96.36.199+dm-1.00.21+evms-2.5.2+vs1.9.5
> VS-API: 0x00010025
> util-vserver: 0.30.204; May 24 2005, 22:22:03
I am using:
root # vserver-info
util-vserver: 0.30.205; May 11 2005, 10:54:16
Vserver mailing list