Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: A hang towards the end of the "Slow comprehensive scan"
From: David Fifield <david () bamsoftware com>
Date: Wed, 20 Jun 2012 07:28:21 -0700

On Wed, Jun 20, 2012 at 10:16:14AM -0400, Whit Blauvelt wrote:
On Tue, Jun 19, 2012 at 08:27:52PM -0400, Whit Blauvelt wrote:
On Tue, Jun 19, 2012 at 03:19:44PM -0700, David Fifield wrote:
nmap -sS -sU -T4 -A -v -PE -PS80,443 -PA3389 -PP -PU40125 -PY --source-port 53 --script "default or (discovery 
and safe)"

Let me put this in the form of a development suggestion. I'm running now
with the current "Slow comprehensive scan" as above, and it appears to be
getting hung up right towards the end:

Service scan Timing: About 97.58% done; ETC: 09:03 (0:17:46 remaining)
Completed Service scan at 09:03, 44085.36s elapsed (16083 services on 18 hosts)
Initiating OS detection (try #1) against 18 hosts
Retrying OS detection (try #2) against 16 hosts
Retrying OS detection (try #3) against 11 hosts
Retrying OS detection (try #4) against 11 hosts
Retrying OS detection (try #5) against 11 hosts
Initiating Traceroute at 09:03
Completed Traceroute at 09:03, 3.11s elapsed
Initiating Parallel DNS resolution of 27 hosts. at 09:03
Completed Parallel DNS resolution of 27 hosts. at 09:03, 0.12s elapsed
Initiating System CNAME DNS resolution of 2 hosts. at 09:03
Completed System CNAME DNS resolution of 2 hosts. at 09:03, 0.03s elapsed
NSE: Script scanning 18 hosts.
Initiating NSE at 09:03

It's been stuck there for an hour. I'm guessing that for my case this may be
from one specific script in the set that's not runnable in my context for
whatever reason. So a question:

- Is there a switch I could have added to the profile that would have caused
  each script to be named as it is run, so it would be obvious where it's
  hanging up?

You can try "-d2 --stats-every 10m". -d is enough to see then names of
scripts as they run and finish, but that's not convenient for the
purpose of finding out which script is taking a long time, because
scripts are run in parallel. On the command line, you can use the
runtime interaction (increase debugging and then press enter to get a
list of running scripts).
http://nmap.org/book/man-runtime-interaction.html

David Fifield
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]