[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: slapd read_config / interface bind errors

To: Jason Swank <jswank@sonatype.com>
Subject: Re: slapd read_config / interface bind errors
From: Andrew Findlay <andrew.findlay@skills-1st.co.uk>
Date: Thu, 20 Nov 2014 09:03:32 +0000
Cc: openldap-technical@openldap.org
Content-disposition: inline
In-reply-to: <20141119210932.GD3705@sonatype.com>
References: <20141119203711.GA3705@sonatype.com> <546D031A.1080200@stroeder.com> <20141119210932.GD3705@sonatype.com>
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Nov 19, 2014 at 04:09:32PM -0500, Jason Swank wrote:

> What about the interface bind conflict when ldap:// is specified?  Is
> that expected behavior?

Yes. ldap:/// binds to port 389 on *all* IPv4 and IPv6 interfaces.
If you also have ldap://<hostname>/ then you are trying to bind at least
one of those interfaces twice.

Note also that you should be using fully-qualified domain names everywhere.
Simple hostnames will not work properly with TLS.

Andrew
-- 
-----------------------------------------------------------------------
|                 From Andrew Findlay, Skills 1st Ltd                 |
| Consultant in large-scale systems, networks, and directory services |
|     http://www.skills-1st.co.uk/                +44 1628 782565     |
-----------------------------------------------------------------------

Follow-Ups:
- Re: slapd read_config / interface bind errors
  - From: Jason Swank <jswank@sonatype.com>

References:
- slapd read_config / interface bind errors
  - From: Jason Swank <jswank@sonatype.com>
- Re: slapd read_config / interface bind errors
  - From: Michael Ströder <michael@stroeder.com>
- Re: slapd read_config / interface bind errors
  - From: Jason Swank <jswank@sonatype.com>

Prev by Date: Re: any help on "ldap_sasl_bind_s failed (53)"
Next by Date: Re: slapd read_config / interface bind errors
Index(es):
- Chronological
- Thread