Thanks Tom, Something like this does the trick:
nmap -A -sV -T4 -P0 -vv However, this returns a lot of info, most of which is not relevant. Sometimes it picks an open port, other times it doesn't. I wouldn't even know how to parse it in Nagios to generate the appropriate response. On Tuesday 02 October 2007, Mick wrote: > On Sunday 30 September 2007, Mick wrote: > > Hi All, > > > > I want to monitor a host who has a Linksys router, which after 24 hours > > or so from being power cycled gradually locks out. All attempts to ping, > > httping, traceroute, fail. Surprisingly, nmap shows: > > ===================================== > > Host XX-XXX-XXX-XX.dhcp.kgpt.tn.charter.com (XX.XXX.XXX.XX) appears to be > > up ... good. > > ===================================== > > > > Sometimes it may find an open port, sometimes not in which case it > > reports that all ports are filtered. I assume from these tests that the > > problem lies with the router as opposed to the modem, otherwise I would > > get a connection refused/failed sort of message, right? Is there a way > > to set up Nagios to monitor/compare both modem and router? I am thinking > > along the lines of pinging the router as normal and when that fails > > repeatedly, to run a command to check the modem. How should I go about > > setting this up? > > Any ideas at all guys? I'm really stuck here. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Nagios-users mailing list [email protected] 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/null
