On Mon, May 3, 2010 at 10:47 AM, Rich Megginson <rmeggins(a)redhat.com&gt; wrote: I have, they're fine, the problem seems to be ns-slapd is listening *only* on ipv6. I don't understand why this is. I used Typical configuration setup, using all the defaults, ipv4 hostname, and domain are correctly found by the setup script. The DS instance is successfully created, but when the next part of the setup script runs, it cannot connect to ldap server because its not listening on the ipv4 interface, so admin configuration fails. I also tried the Advanced setup, and typed in the ipv4 IP to listen on. That failed too. I tried using strictly ipv6 host and domain, this too failed. Is this a bug in ns-slapd or setup-ds-admin.pl? Can anyone explain why ns-slapd is listenong on ipv6 only? And how can I complete the configuration as performed by setup-ds-admin.pl? Thanks -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http://www.ardynet.com:9000/ardymusic.ogg.m3u

On Mon, May 3, 2010 at 12:20 PM, Rich Megginson <rmeggins(a)redhat.com&gt; wrote: ws.int.kritek.net Yes. This has now been resolved, thanks to Rich for your wonderful help. As a result, I've filed two bugs at bugzilla.redhat.com regarding the problem with setup-ds-admin.pl on ipv6 enabled hosts, and a subsequent bug I found with 389-console using ipv4 mapped ipv6 addresses when trying to contact ipv4 hosts. Those bug numbers are 588480, and 588499 respectively. I'll detail the fix as given to me by Rich which enabled the successful completion of setup-ds-admin.pl on an ipv6 enabled host. Create /tmp/fixlistenhost.ldif and populate it with dn: cn=config changetype: modify replace: nsslapd-listenhost nsslapd-listenhost: your_ipv4_ip Run setup-ds-admin.pl slapd.ConfigFile=/tmp/fixlistenhost.ldif Both the DS instance, and the admin server were then correctly configured and running. Its still not understood why ns-slapd was listening only on ipv6 sockets. The problem with 389-console initially failing to connect to the ipv4 host turned out to be said client using an ipv4 mapped ipv6 address, which fails when sysctl key net.ipv6.bindv6only is set to 1 (which if I understand correctly, disables use of ipv4 mapped ipv6 addresses, and disables single socket listening for both ipv4 and ipv6). Thanks again Rich for your invaluable help! -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http://www.ardynet.com:9000/ardymusic.ogg.m3u