On Wed, Dec 16, 2009, Chuck McIntyre wrote:
> 636 is TLS though. Changing the port won't help unless ldap.monitor
> detects that and supports TLS, does it? I'm not currently using mon
> but I recall having to make my own.
636 is SSL, not TLS. You'll need to 'use Net::LDAPS' instead of
'Net::LDAP
636 is TLS though. Changing the port won't help unless ldap.monitor
detects that and supports TLS, does it? I'm not currently using mon
but I recall having to make my own.
On Wednesday, December 16, 2009, Jim Trocki wrote:
> On Wed, 16 Dec 2009, Smaïne Kahlouch wrote:
>
>
> Hi guys,
>
> I would l
Message initial
De: Jim Trocki
À: Smaïne Kahlouch
Cc: mon@linux.kernel.org
Sujet: Re: LDAPS monitoring on port 636
Date: Wed, 16 Dec 2009 13:50:26 -0500 (EST)
On Wed, 16 Dec 2009, Smaïne Kahlouch wrote:
> Hi guys,
>
> I would like to know if it's possible to m
On Wed, 16 Dec 2009, Smaïne Kahlouch wrote:
Hi guys,
I would like to know if it's possible to monitor my ldap server using
the ldap.monitor or another way and by issuing a request to the port 636
instead of port 389.
simply use "monitor ldap.monitor --port 636"
___
Hi guys,
I would like to know if it's possible to monitor my ldap server using
the ldap.monitor or another way and by issuing a request to the port 636
instead of port 389.
I already configured a ldap server with this tool using the port 389, it
worked great.
Or do i have to find another tool ?
