Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




nmap-dev logo Nmap Development mailing list archives

Re: Nmap question (timeout versus scan-delay)
From: "John P. Wilson" <jpw () creare com>
Date: Thu, 5 Oct 2006 11:08:02 -0400

Martin,

 

Sorry for the separate posting to this list; I wasn't subscribed to the
list when I made the first post.

 

Thank you for your explanation.  I think I follow, but to make sure I
understand:

 

timeout is the amount of time to wait for a response

 

scan-delay is the amount of time to wait between consecutive probes -
these can either be repeated probes to the same port or when moving from
one port to another port.  If scan-delay is zero (which I assume it is
by default) then I suppose multiple probes can be sent to multiple ports
at once, right (parallel probing)?  If scan-delay is greater than zero
then, as you point out, this enforces serialization - only dealing with
one probe at a time.  Is there ever a case where multiple probes are
sent all at once to one port?

 

If no reply is received and timeout expires, and if there are still
retries to perform, is the probe sent out immediately, regardless of
what scan-delay is set to?

 

Also: must scan-delay be greater than timeout?

 

Many thanks for any additional information you can provide,

 

John P. Wilson

Creare Inc.

P.O. Box 71

Hanover, NH 03755

603-640-2474

Fax 603-643-4657

 


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


  By Date           By Thread  

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