Nmap Development mailing list archives
Re: Looking at the windows 64 sockets allowed bug.
From: David Fifield <david () bamsoftware com>
Date: Tue, 17 Jul 2012 08:04:24 -0700
On Mon, Jul 09, 2012 at 10:18:29AM -0700, James Rogers wrote:
I am seeing 12 second scan times for a single host in the latest Nmap 6.02 compared to 3 to 4 second scan times in Nmap 6.01. An example of this comparison is in NormalNmap.jpg that I have attached to this email. So it looks like scan times have regressed between 6.01 and 6.02 on windows 7 - 32 bit.
Is this reproducible? I mean, does it consistently happen if you repeat the test? A range of ±10 seconds is not unusual for such a short scan—one dropped probe could cause that. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Re: Looking at the windows 64 sockets allowed bug. James Rogers (Jul 02)
- Re: Looking at the windows 64 sockets allowed bug. James Rogers (Jul 09)
- Re: Looking at the windows 64 sockets allowed bug. Henri Doreau (Jul 10)
- Re: Looking at the windows 64 sockets allowed bug. James Rogers (Jul 14)
- RE: Looking at the windows 64 sockets allowed bug. Rob Nicholls (Jul 15)
- Re: Looking at the windows 64 sockets allowed bug. David Fifield (Jul 17)
- Re: Looking at the windows 64 sockets allowed bug. James Rogers (Jul 17)
- Re: Looking at the windows 64 sockets allowed bug. Henri Doreau (Jul 10)
- Re: Looking at the windows 64 sockets allowed bug. James Rogers (Jul 09)
- Re: Looking at the windows 64 sockets allowed bug. David Fifield (Jul 17)