On Wed, Apr 01, 2009 at 04:46:35PM -0400, Justin Azoff wrote: > I used git bisect against git://git.debian.org/~lamont/nmap.git to track this > down to a commit, and the result was d37f15389455ff474c00223cbf18be4117cedd76. > > The changelog for that says: > > +o Included David's major massping migration project. The same > + underlying engine is now uses for ping scanning as for port > + scanning. We hope this will lead to better performance and > + accuracy, as well as helping to de-bloat Nmap. Please test it out > + and report your results to nmap-dev! For more details, see > + http://seclists.org/nmap-dev/2007/q3/0277.html > > the test I ran was: > > time sudo nmap --host_timeout 2000 -n -sP -PE a.b.0.0/16 -oG - | grep > 'Status: Up' -c > > I verified that with the previous rev > (f501df2e2a74f0bc8ce35a9ddc67d6864afddf96) the results are: > num: 3868 > time: 9:36 > > with d37f15389455ff474c00223cbf18be4117cedd76 the results are: > num: 291 > time: 1:11 > > so it runs in 1/10th the time, but finds 1/10th the hosts. > > As a workaround I changed the timeout to 30000. That finds the expected > number of hosts, and still runs in about 13 minutes. > > Unfortunately I'm not sure what the fix for this is :-) It may be > working as designed and something just needs to be documented better...
Hi Justin. If you can reproduce this with the latest version of Nmap (4.85BETA7), we'd be happy to hear about it and might be able to fix it upstream. You can obtain the latest version of Nmap at http://nmap.org/download.html. Then you can find bug reporting instructions at http://nmap.org/book/man-bugs.html. Nmap 4.62 was released on May 3, 2008. So it is almost a year old now. Cheers, -F -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
