Bug 42152 - net/openldap2: Unable to connect to ldap port (IPv4)
Summary: net/openldap2: Unable to connect to ldap port (IPv4)
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-29 05:00 UTC by Scot W. Hetzel
Modified: 2002-09-01 18:06 UTC (History)
0 users

See Also:

Attachments
file.diff (860 bytes, patch)
2002-08-29 05:00 UTC, Scot W. Hetzel 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Scot W. Hetzel 2002-08-29 05:00:05 UTC 
    After installing the net/openldap2 port, I am unable to connect with ldapsearch
    to the TCPv4 port (389), but the TCPv6 port works.  Checking the output of
    netstat -a | grep ldap, only the TCPv6 port is listed:

        current# netstat -a | grep ldap
        tcp6       0      0  *.ldap                 *.*                    LISTEN

    A search thru the OpenLDAP archives resulted in a similar problem on NetBSD:

        http://www.openldap.org/lists/openldap-software/200203/msg00188.html

Fix: Change slapd.sh to start slapd with -h "ldap://[::] ldap://0.0.0.0"; 

    The following msg mentions that NetBSD has 'mapped addresses' off by
    default, and that enabling this will also cause OpenLDAP v2 to bind to
    both the TCPv4 & TCPv6 ports. Do we have this option of FreeBSD?

    http://www.openldap.org/lists/openldap-software/200203/msg00215.html
How-To-Repeat: 
    Install OpenLDAP2 and try to connect to the TCPv4 port with ldapsearch.
Comment 1 dwcjr freebsd_committer freebsd_triage 2002-09-01 18:06:14 UTC 
State Changed
From-To: open->closed

Committed, thanks!