|
|||||||||||
|
Re: [Nagios-users] NSCA 2.7.2 errors
From: Andreas Ericsson <ae(at)op5.se>
Date: Wed Aug 29 2007 - 17:57:57 EDT
It isn't necessarily. The fact that it closes the connection prior to receiving even the init packet seems to indicate that the receiving end decides to disallow the connection after having accepted it. Since nsca doesn't run as root, and since raw socket manipulation only in order to get the sending host's IP address, it's common practice to accept a connection in order to determine who the other end is, and disconnect them if it's not in some whitelist of known accepted connectors. > I ran tcpdump and compared to when another working machine sends it's I'm not sure where you got the idea that send_nsca sends HTTP, but it doesn't. Anyways, if the exchange goes something like this, it's pretty obvious that what I wrote above is correct;
3way handshake:
immediately followed by EITHER
nsca sends FIN
OR send_nsca sends RST > Different versions of the encryption library, where one end tries to forcibly negotiate a cipher the other end knows nothing about usually causes connection termination. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/nullReceived on Wed Aug 29 17:58:15 2007 This archive was generated by hypermail 2.1.8 : Mon Oct 08 2007 - 17:56:17 EDT |
||||||||||
|
|||||||||||