Nmap Development mailing list archives

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


From: Fredrik Pettai <pettai () nordu net>
Date: Wed, 24 Mar 2010 00:13:46 +0100

On Mar 23, 2010, at 7:01 PM, David Fifield wrote:
On Tue, Mar 23, 2010 at 06:55:30PM +0100, Fredrik Pettai wrote:
On Mar 23, 2010, at 5:57 PM, David Fifield wrote:
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).

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.

I also compiled the SVN version (in pkgsrc on NetBSD), and it fails the
same way as before:

bash-4.0# ./work/nmap-5.22/nmap --iflist

Starting Nmap 5.21 ( http://nmap.org ) at 2010-03-23 18:52 CET
INTERFACES: NONE FOUND(!)
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
ROUTES: NONE FOUND(!)

"INTERFACES: NONE FOUND(!)" is definitely the error here. That's not
expected. Give me some time to think more about what might be causing
it.

Btw. these are all new warnings I see during compilation from 5.10BETA1 -> 5.21. (Current gives even more warnings.)
Maybe those can give hints to something?

Makefile:341: makefile.dep: No such file or directory
intf.c: In function 'intf_loop':
intf.c:733: warning: dereferencing 'void *' pointer
nbase_misc.c: In function 'sockaddr_storage_cmp':
nbase_misc.c:179: warning: control reaches end of non-void function
Makefile:80: makefile.dep: No such file or directory
Makefile:165: makefile.dep: No such file or directory
ncat_proxy.c: In function 'ncat_http_server':
ncat_proxy.c:163: warning: dereferencing type-punned pointer will break strict-a
liasing rules
ncat_ssl.c: In function 'setup_ssl_listen':
ncat_ssl.c:137: warning: assignment discards qualifiers from pointer target type
test/test-wildcard.c: In function 'test':
test/test-wildcard.c:159: warning: value computed is not used
test/test-wildcard.c: In function 'print_escaped':
test/test-wildcard.c:365: warning: array subscript has type 'char'
test/test-wildcard.c:365: warning: array subscript has type 'char'
output.cc: In function 'void printportoutput(Target*, PortList*)':
output.cc:601: warning: format '%ld' expects type 'long int', but argument 4 has
 type 'int'
nmap_dns.cc: In function 'void parse_resolvdotconf()':
nmap_dns.cc:950: warning: format '%u' expects type 'unsigned int', but argument
4 has type 'long unsigned int'

Re,
/P
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/


Current thread: