Nmap Development mailing list archives

Re: nmap errors on *BSDs (noted on NetBSD and MacOSX, so far)


From: David Fifield <david () bamsoftware com>
Date: Tue, 23 Mar 2010 10:57:00 -0600

On Tue, Mar 23, 2010 at 05:28:29PM +0100, Fredrik Pettai wrote:
I've noted two problems that has surfaced in between the release of nmap 
5.00 (2009-07-15) -> 5.10BETA1 (2009-11-23).

First one, traceroute doesn't work any more on *BSD system. I've  
verified this on NetBSD, Mac OS X (I haven't verified OpenBSD, but this 
probably broken there as well). FreeBSD status is unknown.

Thanks for taking the time to report this. Please post the output that
you see. Make sure to run Nmap with the -d option to get debugging
output. I tested just now and traceroute works for me on OS X (with the
latest SVN version; I didn't test 5.10BETA1).

The other, more problematic error (not present on Mac OS X AFAIK), is  
then you run nmap as root on NetBSD, you get this error:

# ./nmap -A ping.sunet.se

Starting Nmap 5.10BETA1 ( http://nmap.org ) at 2010-03-23 16:35 CET
WARNING: Unable to find appropriate interface for system route to  
193.10.5.1
WARNING: Unable to find appropriate interface for system route to  
127.0.0.1
WARNING: Unable to find appropriate interface for system route to  
127.0.0.1
Target* nexthost(HostGroupState*, TargetGroup*, scan_lists*, int):  
failed to determine route to ping.sunet.se (192.36.125.18)
QUITTING!

However, running as a normal user, it works as expected.

This is probably not an error related to NetBSD, but to the routing
table on this particular host. Please send in the output of
"nmap --iflist". Some bugs related to routing were fixed recently and
aren't yet in an official release, and this might be affecting you.

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: