[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: luasocket unstable IPV6_V6ONLY undefined in mingw
- From: Ross Bencina <rossb-lists@...>
- Date: Tue, 09 Apr 2013 18:56:19 +1000
On 8/04/2013 7:02 AM, William Ahern wrote:
IPV6_V6ONLY is a socket option (setsockopt(3)) originating with the
Basic Socket Interface Extensions for IPv6 (RFC 3493).
http://tools.ietf.org/html/rfc3493.html#page-22
On BSDs the value of this option is `27'. Defining it to `1' is probably
wrong. It may do the right thing with #ifdef guarded code, but it may result
in weird things happening if the option is actually used.
Just to confirm, on Windows IPV6_V6ONLY is also 27. From Ws2ipdef.h in
the Windows SDK:
#define IPV6_V6ONLY 27 // Treat wildcard bind as AF_INET6-only.
Note that Windows XP doesn't support dual stack sockets, and this flag
has the opposite default than on most Unices.
http://msdn.microsoft.com/en-us/library/windows/desktop/ms738574(v=vs.85).aspx
See also the note here:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms737937(v=vs.85).aspx
http://stackoverflow.com/questions/2693709/what-was-the-motivation-for-adding-the-ipv6-v6only-flag
Not that I know more than that, but I was curious so looked it up.
Ross.