Nmap Development mailing list archives

nmap cannot detect version of services on solaris 10


From: Luong Nguyen <lucasart1989 () gmail com>
Date: Wed, 3 Jun 2015 21:52:10 -0400

Hi Dev,

I run nmap 6.47 on solaris to detect version of services but cannot success
the nmap command: nmap -sU -p 67,68 192.168.89.0/24 -sV -O
log shows:
  pcap_open_live(lo0, 256, 0, 200) FAILED. Reported error: lo0: No such
device exists (lo0: No DLPI device found).  Will wait 5 seconds then retry.
pcap_open_live(lo0, 256, 0, 200) FAILED. Reported error: lo0: No such
device exists (lo0: No DLPI device found).  Will wait 25 seconds then retry.
Call to pcap_open_live() failed three times. There are several possible
reasons for this, depending on your operating system:
LINUX: If you are getting Socket type not supported, try modprobe af_packet
or recompile your kernel with PACKET enabled.
 *BSD:  If you are getting device not configured, you need to recompile
your kernel with Berkeley Packet Filter support.  If you are getting No
such file or directory, try creating the device (eg cd /dev; MAKEDEV
<device>; or use mknod).
*WINDOWS:  Nmap only supports ethernet interfaces on Windows for most
operations because Microsoft disabled raw sockets as of Windows XP SP2.
Depending on the reason for this error, it is possible that the
--unprivileged command-line argument will help.
SOLARIS:  If you are trying to scan localhost or the address of an
interface and are getting '/dev/lo0: No such file or directory' or 'lo0: No
DLPI device found', complain to Sun.  I don't think Solaris can support
advanced localhost scans.  You can probably use "-Pn -sT localhost" though.

debug log:
 [3288.5830s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for
EID 46083 [192.168.89.40:32774]
NSOCK DEBUG [3288.5830s] msevent_deleteNSE: TCP 192.168.89.34:521 >
192.168.89.40:32774 | SEND
(): msevent_delete (IOD #270) (EID #46083)
NSOCK DEBUG FULL [3288.5830s] process_event(): Processing event 33322
(timeout in 19345ms, done=0)
NSOCK DEBUG FULL [3288.5830s] process_iod_events(): Processing events on
IOD 287 (ev=0)
NSOCK DEBUG FULL [3288.5830s] process_event(): Processing event 36720
(timeout in 21801ms, done=0)
NSOCK DEBUG FULL [3288.5830s] process_iod_events(): Processing events on
IOD 288 (ev=0)
NSOCK DEBUG FULL [3288.5830s] process_event(): Processing event 36890
(timeout in 21922ms, done=0)
NSOCK DEBUG FULL [3288.5830s] process_iod_events(): Processing events on
IOD 290 (ev=0)
NSOCK DEBUG FULL [3288.5830s] process_event(): Processing event 38314
(timeout in 23029ms, done=0)
NSOCK DEBUG FULL [3288.5830s] process_iod_events(): Processing events on
IOD 293 (ev=2)
NSOCK DEBUG FULL [3288.5830s] process_event(): Processing event 46091
(timeout in 29995ms, done=0)
NSOCK DEBUG FULL [3288.5830s] process_event(): NSE #46091: Sending event
NSOCK INFO [3288.5830s] nsock_trace_handler_callback(): Callback: WRITE
SUCCESS for EID 46091 [192.168.89.40:32775]
NSOCK DEBUG [3288.5830NSE: TCP 192.168.89.34:137 > 192.168.89.40:32775 |
SEND
s] msevent_delete(): msevent_delete (IOD #293) (EID #46091)
NSOCK DEBUG FULL [3288.5830s] process_event(): Processing event 41682
(timeout in 876ms, done=0)
NSOCK DEBUG FULL [3288.5830s] process_iod_events(): Processing events on
IOD 302 (ev=1)
NSOCK DEBUG FULL [3288.5830s] process_event(): Processing event 46098
(timeout in 29995ms, done=0)
NSOCK DEBUG FULL [3288.5830s] process_event(): NSE #46098: Sending event
NSOCK INFO [3288.5830s] nsock_trace_handler_callback(): Callback: READ
SUCCESS for EID 46098 [192.168.89.40:32774] (28 bytes):
.....O......................
NSOCK INFONSE: TCP 192.168.89.34:665 < 192.168.89.40:32774 | 00000000: 80
00 00 18 06 4f f3 b2 00 00 00 01 00 00 00 00      O
00000010: 00 00 00 00 00 00 00 00 00 00 00 01

 [3288.5830s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for
EID 46107 [192.168.89.253:80]
NSOCK NSE: TCP 192.168.89.34:15 > 192.168.89.253:80 | SEND
DEBUG [3288.5830s] msevent_delete(): msevent_delete (IOD #306) (EID #46107)
NSOCK DEBUG FULL [3288.5830s] process_event(): Processing event 46112
(timeout in 4996ms, done=1)
NSOCK DEBUG FULL [3288.5830s] process_event(): NSE #46112: Sending event
NSOCK INFO [3288.5830s] nsock_trace_handler_callback(): Callback: CONNECT
ERROR [Address already in use (125)] for EID 46112 [192.168.89.253:80]
NSOCK DEBUGNSE: TCP 0.0.0.0:0 > 192.168.89.253:80 | CONNECT
 [3288.5830s] msevent_delete(): msevent_delete (IOD #307) (EID #46112)
Assertion failed: gh_hnode_is_valid(hnode), file gh_heap.c, line 232

Regards,
Luong Nguyen
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/

Current thread: