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: [PATCH] new --min-retries options
From: Fyodor <fyodor () insecure org>
Date: Thu, 6 Jul 2006 18:35:27 -0700

On Wed, Jul 05, 2006 at 10:14:10PM -0500, Jon Passki wrote:
Hello All,

Today I was scanning using an unreliable network (shared wireless)  
and had some packet loss. I had root access to the host I was  
scanning, which allowed me to review the firewall logs and run a  
tcpdump of the traffic.  There was 2% to 20% packet loss, depending  
upon --max-parallelism and --min-parallelism settings.  The host had  
two ports open and four ports closed, will all the others filtered.   
Even with what seemed the default two retransmissions there still was  
loss.

Did you get wrong results with the default Nmap timing behavior, or
had you also specified aggressive timing options such as
--min-parallelism when this happened?

Cheers,
-F


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


  By Date           By Thread  

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