port status templates with automated port discovery v00.01

[johnrembo]

Hello community,

I did not found any set of scripts/templates to check port(-s) status of a specific device, so had to make my own.

Yes, I know - manage plug-in has this feature, but I've also needed a port scanner in addition.

A data-query uses nmap to scan host and detect services running


And resulting charts (it measures time to establish socket connectivity, which should be in ms at most)


however, due to some strange issues related with php and nmap - a scan might happen much faster in some cases (i.e. it might take 6 seconds for a data query to reload instead of 30), but with reduced amount of info avaiable (can't figure why this happens - please write me if you have some ideas). Anyway - it works.



ps: by default nmap scans for TCP ports. You can adjust it's command-line parameters on your own, but existing version of script checks only for TCP ports - small fix might be necessary if you're interested in UDP as well.

ps: don't forged to edit socket_states.php to change nmap and tmp folder paths.
ps2: not tested on windows
ps3: php-xml extension is required!

tested on: freebsd, debian, centos
nmap: 3.7, 5.x

[unnamed]

hmmmm I'm sorry but where is socket_states.xml ..

[johnrembo]

hmmmm I'm sorry but where is socket_states.xml ..

look above

you must download uncompressed .xml file + compressed .php file (.zip or .gzip)

[shd]

you must download uncompressed .xml file + compressed .php file (.zip or .gzip)

Code: Select all

+ Running data query [34].
+ Found type = '4 '[script query].
+ Could not find data query XML file at '.../resource/script_queries/socket_states.xml'
+ Error parsing XML file into an array.
+ Could not find data query XML file at '.../resource/script_queries/socket_states.xml'
+ Could not find data query XML file at '.../resource/script_queries/socket_states.xml'
+ Could not find data query XML file at '.../resource/script_queries/socket_states.xml'

uncompressed xml file is not enough - it is a template export.

[johnrembo]

you must download uncompressed .xml file + compressed .php file (.zip or .gzip)

Code: Select all

+ Running data query [34].
+ Found type = '4 '[script query].
+ Could not find data query XML file at '.../resource/script_queries/socket_states.xml'
+ Error parsing XML file into an array.
+ Could not find data query XML file at '.../resource/script_queries/socket_states.xml'
+ Could not find data query XML file at '.../resource/script_queries/socket_states.xml'
+ Could not find data query XML file at '.../resource/script_queries/socket_states.xml'

uncompressed xml file is not enough - it is a template export.

oh crap, sorry
I've repacked and reattached the files - should be fine now

[gilles]

right, manage can't do that
but there is a workaround in the ports template
i don't recommend this (php time limit on scripts if you use this) but you can edit scripts/ports.inc to specifically add any port you want to scan
1 port per line...
then run a Verbose Query

[johnrembo]

right, manage can't do that
but there is a workaround in the ports template
i don't recommend this (php time limit on scripts if you use this) but you can edit scripts/ports.inc to specifically add any port you want to scan
1 port per line...
then run a Verbose Query

Oh, I must have missed that...
Well, theoreticaly I had same idea - to build a php-based port-discovery tool, yet, after digging more into nmap's advanced features it became obvious - you can't perform that fast on php side (I'm not even mentioning App./OS Discovery features).

Anyway, Gilles, maybe you've come with some i.e. data_input template that could use you port checking scripts to graph (visualize) historical port availability? That's the major thing I've missed in "Manage".