[Users] Venet's ips disappearing...

[Dariush Pietrzak]

Hello, 
 I noticed that some of ips are sometimes disappearing from my host,
on HN it looks like this:

devamd:# vzlist
     VPSID      NPROC STATUS  IP_ADDR         HOSTNAME
      1002          4 running 192.168.89.106  -
      1003          4 running 192.168.89.107  etchdev386
      1004          4 running 192.168.89.108  etchdevamd64

but those ips are unavailable, ping doesn't work, so I check the routing:

devamd:# ip r
192.168.89.0/24 dev eth3  proto kernel  scope link  src 192.168.89.105
default via 192.168.89.1 dev eth3

I think it shouldn't look like this, so I try such sequence:

	devamd:~# vzctl set 1004 --ipadd 192.168.89.108
	Adding IP address(es): 192.168.89.108
	Unable to add IP 192.168.89.108: Address already in use

strange, if it's in use then where can I see that?.. so:


	devamd:# vzctl set 1003 --ipdel 192.168.89.107
	Deleting IP address(es): 192.168.89.107
	vps-net_del WARNING: Function proxy_arp for eth3 is set to 0. Enable with 'sysctl -w net.ipv4.conf.eth3.proxy_arp=1'. See /usr/share/doc/vzctl/README.Debian.
WARNING: Settings were not saved and will be resetted to original values on next start (use --save flag)

	devamd:# vzctl set 1003 --ipadd 192.168.89.107
	Adding IP address(es): 192.168.89.107
	vps-net_add WARNING: Function proxy_arp for eth3 is set to 0. Enable with 'sysctl -w net.ipv4.conf.eth3.proxy_arp=1'. See /usr/share/doc/vzctl/README.Debian.
WARNING: Settings were not saved and will be resetted to original values on next start (use --save flag)

and then it looks like this:

devamd:# ip r
192.168.89.107 dev venet0  scope link  src 192.168.89.105
192.168.89.0/24 dev eth3  proto kernel  scope link  src 192.168.89.105
default via 192.168.89.1 dev eth3


is there a reason why such disappearing act should happen? (I'm running 
fairly minimal debian etch on HN, there's only vzctl and few things like
mtr, screen installed, nothing should be touching networking)

 this is my only amd64 machine using venet, on i386s with almost identical
setup I haven't noticed anything similiar
-- 
Key fingerprint = 40D0 9FFB 9939 7320 8294  05E0 BCC7 02C4 75CC 50D9
 Total Existance Failure