Nmap Development mailing list archives
Re: massping migration and you
From: Brandon Enright <bmenrigh () ucsd edu>
Date: Thu, 30 Aug 2007 05:52:30 +0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I apologize for replying to my own post. I was not able to reproduce the bug on a second run with the same options. I'll keep trying. The results for the two scans this time around were: Pre-migration (svn from a few days ago): Nmap finished: 186336 IP addresses (11600 hosts up) scanned in 1330.331 seconds real 22m10.338s user 0m8.086s sys 0m40.785s Post-migration: Nmap done: 186336 IP addresses (11554 hosts up) scanned in 9040.909 seconds real 150m40.914s user 21m38.227s sys 2m26.036s Ignore the fact that fewer hosts were found, the scan took longer so more machines were turned off for the night. I'll keep trying to reproduce the crash. Brandon On Thu, 30 Aug 2007 02:59:21 +0000 plus or minus some time Brandon Enright <bmenrigh () ucsd edu> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 29 Aug 2007 20:45:01 -0600 plus or minus some time David Fifield <david () bamsoftware com> wrote:Okay, I've increased the threshold for some of the messages. Go ahead and change any others that you think are inappropriate. Thanks for giving it a try! David FifieldExcellent. I got a crash (no error message) today testing a -PA -sP scan with your migrated mass-ping against the old code. I wasn't able to run -d because of the extreme verbosity and Kris beat me to the note about turning it down. Here are the results of today's preliminary test: I ran two scans: time ./nmap -n -v -PA135,139,445,3389 -sP --min-hostgroup 2048 -oA ~/oldping a.b.0.0/16 c.d.0.0/16 e.f.0.0/16 and time ./nmap -n -v -PA135,139,445,3389 -sP --min-hostgroup 2048 -oA ~/newping a.b.0.0/16 c.d.0.0/16 e.f.0.0/16 This is the typical Windows host discovery scan I do every few days to find hosts that I then go do a 64k port scan of. The oldping scan produced this at the end: Host e.f.255.255 appears to be down. Read data files from: . Nmap finished: 186336 IP addresses (13293 hosts up) scanned in 1336.978 seconds real 22m16.992s user 0m7.834s sys 0m39.758s $ echo $? 0 The newping scan produced this at the end: Host c.d.200.31 appears to be down. Initiating Ping Scan at 00:14 Scanning 2048 hosts [4 ports/host] Ping Scan Timing: About 7.76% done; ETC: 00:20 (0:05:57 remaining) real 83m39.999s user 11m47.630s sys 1m25.964s $ echo $? 130 Without debugging output I don't have anything else for you yet. I'm firing off both scans again this time with -d so hopefully in ~83 minutes I'll have results. Brandon -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFG1jKJqaGPzAsl94IRAnnYAJ9qUAotyR6YODOPqViypWLiG9R2DwCfWUc0 1umJWcemOZZBCoyZkUlUKSA= =vqdC -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFG1lseqaGPzAsl94IRAjXXAJ4mG0HyWZVOqZ8IZgWpJavkdUz66QCgu84r c8IrIUBwdR6QLj4tNUNY1Ow= =u47c -----END PGP SIGNATURE----- _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- massping migration and you David Fifield (Aug 28)
- Re: massping migration and you Fyodor (Aug 28)
- Re: massping migration and you Kris Katterjohn (Aug 29)
- Re: massping migration and you Kris Katterjohn (Aug 29)
- Re: massping migration and you David Fifield (Aug 29)
- Re: massping migration and you Kris Katterjohn (Aug 29)
- Re: massping migration and you Brandon Enright (Aug 29)
- Re: massping migration and you Brandon Enright (Aug 29)
- Re: massping migration and you David Fifield (Aug 30)
- Re: massping migration and you Brandon Enright (Aug 30)
- Re: massping migration and you Brandon Enright (Aug 30)
- Re: massping migration and you David Fifield (Aug 30)
- Re: massping migration and you Brandon Enright (Aug 30)
- Re: massping migration and you David Fifield (Aug 30)
- Re: massping migration and you Brandon Enright (Aug 31)
- Re: massping migration and you David Fifield (Sep 02)