Nmap Development mailing list archives
Re: nmap quits after 30 hosts when -min-parallelism 300 is used
From: Fyodor <fyodor () insecure org>
Date: Sat, 22 Apr 2006 00:14:31 -0700
On Mon, Apr 03, 2006 at 12:27:46PM +0200, Richard van den Berg wrote:
I was running nmap 4.00 with these options: nmap -sS -P0 -r -n -T4 --max-rtt-timeout 300 --min-rtt-timeout 50 --initial-rtt-timeout 250 --min-parallelism 300 -A -vv -p- -oA foo hosts After finishing the first group of 30 hosts, nmap quits with saying: box(300, 100, 15) called (min,max,num) QUITTING!
Thanks for this report. For the next version, I have put in the following fix. Let me know if you are still able to reproduce the problem. --- NmapOps.cc (revision 3224) +++ NmapOps.cc (working copy) @@ -433,6 +433,10 @@ if (af() != AF_INET) mass_dns = false; + /* Prevent performance values from getting out of whack */ + if (min_parallelism > max_parallelism) + max_parallelism = min_parallelism; + } void NmapOps::setMaxRttTimeout(int rtt) Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev
Current thread:
- nmap quits after 30 hosts when -min-parallelism 300 is used Richard van den Berg (Apr 03)
- Re: nmap quits after 30 hosts when -min-parallelism 300 is used Fyodor (Apr 22)