Nmap Development mailing list archives
scan-delay enforces serialization - why?
From: Martin Mačok <martin.macok () underground cz>
Date: Mon, 21 Jan 2008 14:31:26 +0100
Hi, in some scenarios, it makes sense to define scan-delay but allow parallelization of probes (actually, when Nmap eases off due to lost packets, it does so automagically), but it is currently not possible to explicitely set this on cmdline: % nmap --scan-delay=10 --min-parallelism=2 127.0.0.1 --min-parallelism=2 must be less than or equal to --max-parallelism=1 QUITTING! My question is why max-parallelism=1 is enforced when scan-delay is explicitely set? Either the implementation should be fixed or the manpage should clearly mention it. Thank you! Martin _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- scan-delay enforces serialization - why? Martin Mačok (Jan 21)
- Re: scan-delay enforces serialization - why? Fyodor (Jan 21)
- Re: scan-delay enforces serialization - why? Martin Mačok (Jan 22)
- Re: scan-delay enforces serialization - why? Fyodor (Jan 21)