>> actually, if we have bind(2) ordering constraint in the kernel,
>> the order of return value from getaddrinfo(3) has to be carefully
>> designed - in your case, I bet you need to return AF_INET6 first on
>> AI_PASSIVE getaddrinfo lookup.
>I am not sure what you mean here exactly. Since the above failures occur
>regardless of order I don't see why it would make any difference in which
>order the addresses were returned from getaddrinfo.
assuming that you do RFC2553-inbound,
- if you bind(2) to AF_INET6 before AF_INET, (a) AF_INET bind fails,
but (b) you will accept both IPv4 and IPv6 traffic into AF_INET6
socket.
- if you bind(2) to AF_INET before AF_INET6, (a) AF_INET6 bind fails,
and (b) you will accept IPv4 traffic only, into AF_INET socket.
itojun
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
