From: Tor Rune Skoglund (torrunes_at_datakompaniet.no)
Date: Thu 30 Oct 2003 - 22:06:18 GMT
torsdag 30. oktober 2003, 17:43, skrev Jacques Gelinas:
> You create a bunch of vserver, all using an IP (or more) address of the
> same IP network. This is fairly common (typical in fact). Say you have the
> following vservers
> A: 192.168.0.1/255.255.255.0
> B: 192.168.0.2/255.255.255.0
> C: ...
> D: ...
> Then you start all those vservers in the above order. Then you stop vserver
> A (or a restart). When you do stop a vserver, the corresponding IP aliases
> are removed. In the above example, the vserver script does
> ifconfig eth0:A down
> There is a catch here. eth0:A was the first IP aliases created by the
> kernel for the 192.168.0.0/255.255.255.0 network. It sets a flag telling
> this is the "main" IP number of this network. All the other IP aliases
> (created for B, C and D vservers) will have the opposite flag
> Whenever the kernel drop a "main" IP aliases, all the related (secondary)
> IP aliases (same network) are also dropped.
Might be a stupid question, but what if eth0 is configured in the same
network in the vserver host? I cannot see that this problem has occured on
my vservers yet, so maybe the fact that eth0 always is configured have
something to do with it? I don't know...
Tor Rune Skoglund
Vserver mailing list