ports/116778: security/nmap ping-scan misses some hosts

[Mark D. Foster]

The following reply was made to PR ports/116778; it has been noted by GNATS.

From: "Mark D. Foster" <mark at foster.cc>
To: bug-followup at FreeBSD.org
Cc:  
Subject: Re: ports/116778: security/nmap ping-scan misses some hosts
Date: Tue, 29 Jan 2008 14:11:09 -0800

 Using the latest version. -sP with range works fine as user... but not
 so with root.  I'm sure this doesn't help explain the other problem, but
 as root I only see 3 hosts, as user I see 5.
 
 /tmp/nmap-4.22SOC8 mdf at franco>./nmap -sP 192.168.1.1-11
 
 Starting Nmap 4.22SOC8 ( http://insecure.org ) at 2007-11-03 22:13 PDT
 Warning: File ./nmap-services exists, but Nmap is using
 /usr/local/share/nmap/nmap-services for security and consistency
 reasons.  set NMAPDIR=. to give priority to files in your local
 directory (may affect the other data files too).
 Host gw.foster.dmz (192.168.1.1) appears to be up.
 Host franco.foster.dmz (192.168.1.3) appears to be up.
 Host turing.foster.dmz (192.168.1.4) appears to be up.
 Host monk.foster.dmz (192.168.1.9) appears to be up.
 Host sonar.foster.dmz (192.168.1.11) appears to be up.
 Nmap done: 11 IP addresses (5 hosts up) scanned in 2.792 seconds
 /tmp/nmap-4.22SOC8 mdf at franco>sudo !!
 sudo ./nmap -sP 192.168.1.1-11
 
 Starting Nmap 4.22SOC8 ( http://insecure.org ) at 2007-11-03 22:13 PDT
 Warning: File ./nmap-services exists, but Nmap is using
 /usr/local/share/nmap/nmap-services for security and consistency
 reasons.  set NMAPDIR=. to give priority to files in your local
 directory (may affect the other data files too).
 Host gw.foster.dmz (192.168.1.1) appears to be up.
 MAC Address: 00:0F:B5:1F:89:D2 (Netgear)
 Host franco.foster.dmz (192.168.1.3) appears to be up.
 Host monk.foster.dmz (192.168.1.9) appears to be up.
 MAC Address: 00:09:6B:A0:96:17 (IBM)
 Nmap done: 11 IP addresses (3 hosts up) scanned in 0.762 seconds