Nmap Development mailing list archives

RE: Nmap 4.11: False positive ping results


From: "Mike C (sec)" <check () imjc com>
Date: Tue, 25 Jul 2006 12:27:15 +0100

Curious - why do you say the bug was already fixed?

Isn't nmap 4.11 a later version than nmap 4.10?

In fact, isn't nmap 4.11 "the latest Nmap on Windows" (excluding the 4.20
Alpha's) - which Vitaly says is broke?

Regards,

Mike

-----Original Message-----
From: nmap-dev-bounces () insecure org [mailto:nmap-dev-bounces () insecure org]
On Behalf Of Martin Macok
Sent: 22 July 2006 11:20
To: nmap-dev () insecure org
Subject: Re: Nmap 4.11: False positive ping results


On Fri, Jul 21, 2006 at 03:55:27PM -0500, Vitaly McLain wrote:

1. Nmap 4.03 and Nmap 4.11, under Windows XP SP1 and SP2, reported all 254
hosts as up.
2. Angry IP Scanner reports 2 hosts as being up, even after being made
less
angry (slowed down).
3. Nmap 4.10 under Linux (kernel 2.4.25) says 22 hosts are up.

Number #3 (Nmap/Linux) is the only correct answer!

So it means the bug was already fixed so I don't think anybody is
interested unless the latest Nmap on Windows still has the bug. In
that case use "-vvv -d --packet-trace" options and send the output to
us. You don't need to scan all C class network, one IP that should be
"down" and Nmap is reporting it is "up" is enough to debug the
problem, anyway.

Martin Mačok
ICT Security Consultant


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev


Current thread: