Your message dated Sat, 11 Sep 2010 20:37:06 +0000
with message-id <[email protected]>
and subject line Bug#574522: fixed in vzctl 3.0.24-5
has caused the Debian Bug report #574522,
regarding clarification of proxy_arp settings
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
574522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574522
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vzctl
Version: 3.0.23-8
There seems to be confusion about the setting of the sysctl proxy_arp key.
On one hand, http://wiki.openvz.org/Quick_installation has
net.ipv4.conf.default.proxy_arp = 0
But when starting a VE with vzctl, I get the error message
vps-net_add WARNING: Function proxy_arp for eth0 is set to 0. See
/usr/share/doc/vzctl/README.Debian
Indeed, README.Debian is also ambiguous on this point. Both variants are used.
"If you want network access for the virtual server then you need to
enable IP forwarding.
...
proxy_arp=0
...
If you want the virtual server to directly access the network you need to
enable proxy_arp...
proxy_arp=1
Does perhaps "directly access" refer to veth rather than venet devices? In that
case this whole think might make sense.
However, after setting up a second server on the same network I get "address in
use" errors:
Starting container ...
Container is mounted
Adding IP address(es): 10.158.117.145
arpsend: 10.158.117.145 is detected on another computer : 00:18:fe:fb:32:02
The .145 is not configured on the other host, but rather the proxy_arp setting
causes it to reply to the arp query.
This will cause problems unless there is only one server on the subnet.
But maybe the bug is elsewhere. Why would openvz proxy requests for addresses
that are not configured? Maybe the semantic of "proxy_arp" has changed between
kernel versions?
Regards,
Stefan
--- End Message ---
--- Begin Message ---
Source: vzctl
Source-Version: 3.0.24-5
We believe that the bug you reported is fixed in the latest version of
vzctl, which is due to be installed in the Debian FTP archive:
vzctl_3.0.24-5.diff.gz
to main/v/vzctl/vzctl_3.0.24-5.diff.gz
vzctl_3.0.24-5.dsc
to main/v/vzctl/vzctl_3.0.24-5.dsc
vzctl_3.0.24-5_i386.deb
to main/v/vzctl/vzctl_3.0.24-5_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ola Lundqvist <[email protected]> (supplier of updated vzctl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 10 Sep 2010 18:56:42 +0200
Source: vzctl
Binary: vzctl
Architecture: source i386
Version: 3.0.24-5
Distribution: unstable
Urgency: medium
Maintainer: Ola Lundqvist <[email protected]>
Changed-By: Ola Lundqvist <[email protected]>
Description:
vzctl - server virtualization solution - control tools
Closes: 50086 574522
Changes:
vzctl (3.0.24-5) unstable; urgency=medium
.
* Make sure vzeventd can read options from /etc/default/vzeventd.
This is a correction of the backported solution for #576227 in last upload.
Documented this functionality as well.
* Changed the README.Debian file so that it documents how to install squeeze
instead of how to install lenny. In a addition a number of language
corrections was made. Also clarification on network configuration was done.
Closes: #574522.
* Documented in the README.Debian file that /etc/mailname should be changed
when creating the container. Closes: #50086.
* Changed the package description so it do not refer to the kernel patch
package as it do no longer exist.
Checksums-Sha1:
21e450f7ec35911af9a703507160b3cc7ac08ddf 966 vzctl_3.0.24-5.dsc
98291182f37e0496bcd2223d5bb68050c6fd857f 446829 vzctl_3.0.24-5.diff.gz
8f301995994048e335c20cb3413f3e7f2cb726a3 208340 vzctl_3.0.24-5_i386.deb
Checksums-Sha256:
3fd23b9536540a0a0d1e9a8fe71ff3cf01d798719089f905a83301031ce61f52 966
vzctl_3.0.24-5.dsc
cdbf442647a5c3a914419a6d33d46f3a3b63f41d1c38904b0607caecf35ffeaf 446829
vzctl_3.0.24-5.diff.gz
06fb4b9341589ee7f30a3e2bf2c19f65f8b67439cecb2fe15284ca411bd405db 208340
vzctl_3.0.24-5_i386.deb
Files:
6e7049d6d254078323496fe40ddbada6 966 admin optional vzctl_3.0.24-5.dsc
b7ebb063d794e66137c262189485ff84 446829 admin optional vzctl_3.0.24-5.diff.gz
3411af1b8bc11b5179872bd59447173a 208340 admin optional vzctl_3.0.24-5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkyL4xUACgkQGKGxzw/lPdkKIwCeJURFcGJZpykCWc9FLLZEk4vJ
vMkAn21Jvj9chsUOrLpbFQRt34oyV1AB
=FVI1
-----END PGP SIGNATURE-----
--- End Message ---
