On 2006.01.23 12:31:53 +0100, Raimund Specht wrote: > Hi ! > > We have a very strange problem here with virtual IP addresses (various > up-to-date 2.6 kernels with vserver 2.0): > > Let eth0 have a normal IP address. Let v1 and v2 be two vservers with a > virtual IP on eth0 each. > > # vserver v1 start > # vserver v2 start > > ifconfig shows eth0, eth0:v1, and eth0:v2 as expected, everything works. > > # vserver v1 stop > > Now ifconfig shows that all virtual IPs have been removed although > vserver-stat shows that v2 is still running. Networking with v2 doesn't > work either. This only happens if the vserver, that was startet first, ist > stopped. Other orderings work fine. > > This problem is not vserver related, we can reproduce it on non-vserver > systems/kernels too. The following commands reproduce it on 90% of our > systems (Debian, Ubuntu, Gentoo, all with Linux 2.6): > > # ifconfig eth0:1 1.2.3.4 > # ifconfig eth0:2 1.2.3.5 > # ifconfig eth0:1 del 1.2.3.4 > > > Does anyone else have this problem? > Any workaround except defining an eth0:dummy interface outside any vserver?
Yep, that's default behaviour... :/ If you add the first address for a subnet, this becomes the 'primary' address for this subnet, all later added addresses becomes secondaries. Removing the primary address tears down all secondaries as well. The common workaround is to have a primary address for each used subnet on the host and only giving secondaries to the vservers. HTH Björn _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
