Re: nmap on opensolaris WARNING: Unable to find appropriate interface for system route to 0.64.0.0

[Morten Gulbrandsen <Morten.Gulbrandsen () rwth-Aachen de>]

Fyodor wrote:
> On Tue, Oct 16, 2007 at 07:05:12PM +0200, Morten Gulbrandsen wrote:
>   
> > #  nmap -A -T4 scanme.nmap.org playground
> >
> > Starting Nmap 4.20 ( http://insecure.org ) at 2007-10-14 14:56 CEST
> > WARNING: Unable to find appropriate interface for system route to 0.64.0.0
> >     
>
> Thanks for the report, but please resend your message to
> nmap-dev () insecure org rather than nmap-hackers.  Also, it would help
> if you include the results of the command "nmap --iflist" in your
> report.
>
> Cheers,
> -F
>   

sure .
bash-3.00$ nmap --iflist      

Starting Nmap 4.20 ( http://insecure.org ) at 2007-10-16 23:50 CEST
tcpip.cc: Failed to open ethernet interface (nge0). A possible cause on 
BSD operating systems is running out of BPF devices (see 
http://seclists.org/lists/nmap-dev/2006/Jan-Mar/0014.html).
QUITTING!
bash-3.00$ uname -a
SunOS solaris-devx 5.11 snv_64a i86pc i386 i86pc
bash-3.00$ su root
Password:
# bash
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 
8232 index 1
        inet 127.0.0.1 netmask ff000000
nge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 
index 2
        inet 192.168.0.6 netmask ffffff00 broadcast 192.168.0.255
        ether 0:14:4f:21:45:fa
nge1: flags=201000802<BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 4
        inet 0.0.0.0 netmask 0
        ether 0:14:4f:21:45:fb
elxl0: flags=201004842<BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 
1500 index 3
        inet 0.0.0.0 netmask 0
        ether 0:50:4:89:fc:88
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 
8252 index 1
        inet6 ::1/128
# netstat -nr

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              192.168.0.1          UG        1         93          
192.168.0.0          192.168.0.6          U         1         14 nge0     
224.0.0.0            127.0.0.1            U         1          0 lo0      
127.0.0.1            127.0.0.1            UH        1          4 lo0      

Routing Table: IPv6
  Destination/Mask            Gateway                   Flags Ref   
Use    If  
--------------------------- --------------------------- ----- --- 
------- -----
ff00::/8                    ::1                         U       1       
0 lo0  
::1                         ::1                         UH      1      
28 lo0  
#

# ping  192.168.0.1
192.168.0.1 is alive
# ping  192.168.0.250
192.168.0.250 is alive
# ping  192.168.0.254
192.168.0.254 is alive
# tracert 192.168.0.1
bash: tracert: command not found
# traceroute 192.168.0.1
traceroute to 192.168.0.1 (192.168.0.1), 30 hops max, 40 byte packets
 1  localhost (192.168.0.1)  1.894 ms  7.567 ms  0.367 ms


#  nmap -A -T4 scanme.nmap.org playground

Starting Nmap 4.20 ( http://insecure.org ) at 2007-10-14 14:56 CEST
WARNING: Unable to find appropriate interface for system route to 0.64.0.0

WARNING: Unable to find appropriate interface for system route to
255.255.255.255

WARNING: Unable to find appropriate interface for system route to 1.0.0.0

WARNING: Unable to find appropriate interface for system route to
255.255.255.255

WARNING: Unable to find appropriate interface for system route to 0.32.0.0

WARNING: Unable to find appropriate interface for system route to
255.255.255.255

WARNING: Unable to find appropriate interface for system route to
255.255.255.255

WARNING: Unable to find appropriate interface for system route to
255.255.255.255

WARNING: Unable to find appropriate interface for system route to
255.255.255.255

Failed to resolve given hostname/IP: playground.  Note that you can't
use '/mask' AND '1-4,7,100-' style IP ranges


http://bbs.chinaunix.net/viewthread.php?tid=670330

has the same error.

what can it be ?



http://pastebin.com/f6679cb77

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