[Bug libc/12377] getaddrinfo() should disregard link-local IPv6 addresses for AI_ADDRCONFIG purposes

["rick.jones2 at hp dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12377

rick jones <rick.jones2 at hp dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rick.jones2 at hp dot com

--- Comment #2 from rick jones <rick.jones2 at hp dot com> 2011-07-06 20:29:54 UTC ---
(In reply to comment #0)
> While it does not mention link-local (or loopback) addresses specifically, it
> is obvious that its intended use is to allow an application to avoid getting
> addresses returned that cannot be used for communication.  In that regard
> link-local addresses are very similar to loopback addresses, in the sense that
> they're automatically configured on all hosts regardless of any external
> connectivity, and can not be used when communicating with the outside world. 

How does getaddrinfo() know that the name to be looked-up isn't supposed to map
to a link-local IPv6 address that will be reachable?

Interestingly enough, I seem to have the opposite problem - it appears that for
2.12, as shipped with Maverick anyway, that the presence of a link-local IPv6
address is not sufficient to allow "::1" (or other IPv6 addresses, for example
" fe80::21c:c4ff:fe47:d3f9" which happens to be the link-local IPv6 address on
my system's eth0 interface) to be resolved when AI_ADDRCONFIG is set - which I
consider a bug :)

> For what it's worth, both Microsoft Windows and Mac OS X appear to disregard
> link-local IPv6 addresses for AI_ADDRCONFIG purposes, with no apparent ill
> effects.

Perhaps no-one is attempting to actually do link-local IPv6 communication yet.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.