On Mon, 21 Feb 2005, Mark Brown wrote: > Putting "options inet6" into resolv.conf ought to do the trick. > Stricter checking on the results of gethostbyname() ought to do the > trick I'd imagine.
OK, this resolv.conf option is undocumented in resolv.conf, yields bogus results as given below: | newszilla6.xs4all.nl: connecting to port nntp... | warning: newszilla6.xs4all.nl: connection to 32.1.8.136 failed: Address family not supported by protocol | newszilla6.xs4all.nl: address list exhausted without establishing connection. | newszilla6.xs4all.nl: connection failed. and violates POSIX that specifies gethostbyname returns AF_INET. This is clearly a gethostbyname() and/or resolver bug. So this is my final ruling: 1. This behavior is not a leafnode bug. 2. No attempts to work around brokenness of gethostbyname() that returns AF_INET6 with nondefault configuration will be made. 3. leafnode-1.10 will not support IPv6 on the client side. 4. leafnode-2 already has client-side IPv6 support. -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
