Issues on Windows using Nmap with a VPN, Dial-up adapter, or other PPP like interface

[kx <kxmail () gmail com>]

Just wanted to reply to all the recent questions and issue reports
about issues on Windows using Nmap with a VPN, Dial-up adapters, or
other PPP like interfaces.

Short and sweet - winpcap doesn't support these well enough for nmap
to support routine use on these interfaces.

http://www.winpcap.org/misc/faq.htm#Q-5
http://www.winpcap.org/misc/faq.htm#Q-6

Would it make sense to add this to the error messages everyone posted?


WINDOWS: If you are getting Error opening adapter, you might be trying
to use nmap over a dial-up, VPN or other PPP type adapter, which
libpcap/winpcap does not routinely support.



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 r
ecompile your kernel with SOCK_PACKET enabled.
*BSD:  If you are getting device not configured, you need to recompile your kern
el with Berkeley Packet Filter support.  If you are getting No such file or dire
ctory, try creating the device (eg cd /dev; MAKEDEV <device>; or use mknod).
SOLARIS:  If you are trying to scan localhost and getting '/dev/lo0: No such fil
e or directory', complain to Sun.  I don't think Solaris can support advanced lo
calhost scans.  You can probably use "-P0 -sT localhost" though.

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