Re: LDAPS monitoring on port 636
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' in conjunction with --port 636 for that to work (and have the requisite IO::Socket::SSL module installed.) Or, if you really meant TLS, add $ldap-start_tls( verify = 'none' ); Somewhere after the new(), but before the bind() in the monitor script. -- Mahlon E. Smith http://www.martini.nu/contact.html pgpDtQXrjCzU9.pgp Description: PGP signature ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: LDAPS monitoring on port 636
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 ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: LDAPS monitoring on port 636
Message initial De: Jim Trocki troc...@gmail.com À: Smaïne Kahlouch smain...@free.fr 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 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 -- Oki thanks i'll do that. My server is listening with a FQDN. To reach it you have to use for exemple ldaps://ldap.domain.tld. How can i configure mon in order to connect to my server using ldap.domain.tld ? Thanks Grifith. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
