Nmap Development mailing list archives
nmap quits after 30 hosts when -min-parallelism 300 is used
From: Richard van den Berg <richard.vandenberg () ins com>
Date: Mon, 03 Apr 2006 12:27:46 +0200
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! My concern about this is 2 fold: 1) How can max-parallelism become lower than min-parallelism? There is a check for this in box(), hence fatal() is called. 2) Why don't my foo.nmap and foo.gnmap files contain the results of the scans for the first 30 hosts? I did not have a chance to test whether setting --min-parallelism 300 as well does not trigger this behavior. Sincerely, -- Richard van den Berg Consultant, INS E-mail: richard.vandenberg () ins com Mobile: +31 (0)6-52071109 PGP Key ID: 0x6614D2AC Fingerprint: 6829 0AD3 2F49 6D83 B65E E235 B8D3 8299 6614 D2AC _______________________________________________ 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)