http://defect.opensolaris.org/bz/show_bug.cgi?id=9340
amaguire <alan.maguire at sun.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ACCEPTED |FIXINPROGRESS
--- Comment #4 from amaguire <alan.maguire at sun.com> 2009-06-26 08:29:03 ---
n the course of investigating this I've determined that the form
of name resolution autofs uses to check if an automount
path is local specifies AI_ADDRCONFIG (actually it specifies
AI_DEFAULT, which is #defined as AI_V4MAPPED | AI_ADDRCONFIG).
>From the manpage:
o The AI_ADDRCONFIG flag specifies that a query for
AAAA records should occur only when the node is
configured with at least one IPv6 source address. A
query for A records should occur only when the node
is configured with at least one IPv4 source
address. For example, if a node is configured with
no IPv6 source addresses, af equals AF_INET6, and
the node name queried has both AAAA and A records,
then:
o A NULL pointer is returned when only the
AI_ADDRCONFIG value is specified.
o The A records are returned as IPv4-mapped IPv6
addresses when the AI_ADDRCONFIG and
AI_V4MAPPED values are specified.
This presents a problem since loopback mounts will fail
the self-check initiated by autofs when no non-loopback
IP interfaces are plumbed. You can simulate this situation
by unplumbing everything except lo0 and trying "ping localhost" -
you'll get "ping: unknown host localhost" (ping uses
AI_ADDRCONFIG in it's call to resolve hosts via getaddrinfo()).
The self_check() function should just specify AI_V4MAPPED,
as this will allow checking if addresses are local without
having a network (this has been tested and works).
So in other words, this isn't a bug in NWAM per se, but
rather a bug in how autofs does name resolution. The fix
is low-risk, and worth doing in my opinion. Fix on the
way...
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
