<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'>For the most part, this works. However, the problem is that it requires that ALL open ports be accepted as parameters. I want to specify the ports to check. For example, if port 8081 is open, it may not always be open, then I get the stupid notification. I don't want to monitor port 8081, I want to monitor 25,80,110,143, etc.<br><br>----- Original Message -----<br>From: "Marc Powell" <marc@ena.com><br>To: "Nagios-Users Mailinglist" <Nagios-users@lists.sourceforge.net><br>Sent: Tuesday, September 29, 2009 3:27:09 PM GMT -06:00 US/Canada Central<br>Subject: Re: [Nagios-users] Monitoring Open Ports<br><br><br>On Sep 29, 2009, at 2:51 PM, Matt Baer wrote:<br><br>> Is there a way that Nagios can monitor open ports, even if there <br>> isn't anything listening on the destination? I'd like to monitor my <br>> open ports on my firewall JUST to make sure they're open. I would <br>> just specify the port with the normal Nagios command and point it at <br>> my public IP address, but obviously, the check will fail unless <br>> something is listening on the other end. Basically I want to port <br>> scan specific ports. Any ideas?<br><br>A quick google for 'nagios nmap' yields this result that looks <br>promising --<br><br>http://ubermonkey.wordpress.com/2006/09/28/nagios-nmap-plugin/<br><br>--<br>Marc<br><br><br>------------------------------------------------------------------------------<br>Come build with us! The BlackBerry® Developer Conference in SF, CA<br>is the only developer event you need to attend this year. Jumpstart your<br>developing skills, take BlackBerry mobile applications to market and stay <br>ahead of the curve. Join us from November 9-12, 2009. Register now!<br>http://p.sf.net/sfu/devconf<br>_______________________________________________<br>Nagios-users mailing list<br>Nagios-users@lists.sourceforge.net<br>https://lists.sourceforge.net/lists/listinfo/nagios-users<br>::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. <br>::: Messages without supporting info will risk being sent to /dev/null<br></div></body></html>