Your message dated Mon, 6 Jun 2011 07:21:56 +0200
with message-id <[email protected]>
and subject line Samba seems to set IPV6_V6ONLY since 3.6.0pre1
has caused the Debian Bug report #562644,
regarding samba: Does not set IPV6_V6ONLY
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.)
--
562644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562644
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:3.4.3-1
Hi,
It seems samba does not call setsockopt() with IPV6_V6ONLY. It's
really recommended that you do this.
Note that netbase has just changed the default from 0 to 1, so you
get that behaviour now by default. It doesn't seem to break
anything, you now have 2 sockets open instead of just 1.
Kurt
--- End Message ---
--- Begin Message ---
Version: 2:3.6.0~pre1-1
In 3.6.0pre1 util_sock.c:
#ifdef HAVE_IPV6
/*
* As IPV6_V6ONLY is the default on some systems,
* we better try to be consistent and always use it.
*
* This also avoids using IPv4 via AF_INET6 sockets
* and makes sure %I never resolves to a '::ffff:192.168.0.1'
* string.
*/
if (sock.ss_family == AF_INET6) {
int val = 1;
int ret;
ret = setsockopt(res, IPPROTO_IPV6, IPV6_V6ONLY,
(const void *)&val, sizeof(val));
Relevant commit log:
commit a3a38ee90ab4ab2be68ac71d9c581daa6b9ee189
Author: Stefan Metzmacher <[email protected]>
Date: Sat Apr 23 11:29:51 2011 +0200
s3:lib/util_sock: listen on IPv6 addresses with IPV6_ONLY (bug #7383)
This avoids getting IPv4 addresses as mapped IPv6 addresses
(e.g. ::ffff:192.168.0.1).
Before the bahavior was inconsistent between operating system
and distributions. Some system have IPV6_ONLY as default.
Now we consistently get AF_INET for IPv4 addresses and AF_INET6
for IPv6 addresses.
It also makes it possible to listen only on IPv6 now
as "::" doesn't imply "0.0.0.0" anymore. Which also
avoids confusing log messages that we were not able to
bind to "0.0.0.0".
metze
So, this is fixed in 3.6.* releases (currently in experimental).
--
signature.asc
Description: Digital signature
--- End Message ---
