usr/sbin/nmbd on all architectures uses function inet_ntoa, which may impact IPv6 support usr/bin/nmblookup on all architectures uses function inet_ntoa, which may impact IPv6 support usr/lib/libndr.so.0.0.2 on i686 ppc s390 uses function inet_addr, which may impact IPv6 support usr/lib/libndr.so.0.0.2 on i686 ppc s390 uses function inet_ntoa, which may impact IPv6 support usr/lib/libsmbconf.so.0 on i686 ppc s390 uses function gethostbyname, which may impact IPv6 support usr/lib/libsmbconf.so.0 on i686 ppc s390 uses function inet_ntoa, which may impact IPv6 support usr/lib/samba/libaddns.so on i686 ppc s390 uses function gethostbyname, which may impact IPv6 support usr/lib/samba/libaddns.so on i686 ppc s390 uses function inet_addr, which may impact IPv6 support usr/lib/samba/libgse.so on i686 ppc s390 uses function inet_ntoa, which may impact IPv6 support usr/lib/samba/libsamba-sockets.so on i686 ppc s390 uses function gethostbyaddr, which may impact IPv6 support usr/bin/smbtorture on all architectures uses function inet_ntoa, which may impact IPv6 support usr/lib64/libndr.so.0.0.2 on x86_64 ppc64 s390x uses function inet_addr, which may impact IPv6 support usr/lib64/libndr.so.0.0.2 on x86_64 ppc64 s390x uses function inet_ntoa, which may impact IPv6 support usr/lib64/libsmbconf.so.0 on x86_64 ppc64 s390x uses function gethostbyname, which may impact IPv6 support usr/lib64/libsmbconf.so.0 on x86_64 ppc64 s390x uses function inet_ntoa, which may impact IPv6 support usr/lib64/samba/libaddns.so on x86_64 ppc64 s390x uses function gethostbyname, which may impact IPv6 support usr/lib64/samba/libaddns.so on x86_64 ppc64 s390x uses function inet_addr, which may impact IPv6 support usr/lib64/samba/libgse.so on x86_64 ppc64 s390x uses function inet_ntoa, which may impact IPv6 support usr/lib64/samba/libsamba-sockets.so on x86_64 ppc64 s390x uses function gethostbyaddr, which may impact IPv6 support
usr/sbin/nmbd = NBT, which is IPv4-only. usr/bin/nmblookup = NBT, which is IPv4-only. This is from an automated tool I assume. Some of these calls are in explicit IPv4-only code. Some may not be. The problem with a report like this is determining which is which. Jeremy.
Yes, it is an automated tool but I wanted to inspect all of them just to make sure. What I found in a quick search was in libads code and code related to 'net dns'.
net dns is one of the few users of libaddns, and that's antique. :) Adding GSS-TSIG client side support to libcli/dns is on my todo list, no promises on delivery dates, though.
net ads gethostbyname was removed with 4.14. If you still see other valid IPv6 issues, please reopen or file another bug for that. *** This bug has been marked as a duplicate of bug 13706 ***