mailing list archives
Re: disable valid IPv4 address check to allow scanning Hamachi (22.214.171.124/8) targets?
From: David Fifield <david () bamsoftware com>
Date: Sat, 2 Apr 2011 15:30:19 -0700
On Sat, Apr 02, 2011 at 02:51:21PM -0700, Brolin Empey wrote:
When I try scanning an Hamachi client’s 126.96.36.199/8 IP address, nmap
states “doArp can only handle IPv4 addresses” and aborts. I know
this is because Hamachi’s assignment of 188.8.131.52/8 IP addresses is
unofficial, but it would be nice if the valid IPv4 address check
could be disabled so Hamachi clients and other hosts with
unofficially-assigned IP addresses could still be scanned.
I searched for a solution/workaround but only found discussions
about Hamachi’s unofficial IP address assignments, not any way to
scan Hamachi clients.
I do not think these details matter in this case, but I am currently
using nmap v5.50 on Windows 7 Professional IA-32.
There must be something else going wrong, because I can ARP scan
/sbin/ifconfig eth0:1 184.108.40.206 netmask 255.0.0.0
nmap -PR 220.127.116.11/8 --packet-trace
Windows might be an issue. I'm not familiar with Hamachi, but if it
creates a pseudo-interface, it probably won't work on Windows. (Because
Windows lacks support for raw sockets, we can only do raw scans on
Ethernet devices.) However, if that's the case, then the error message
Please send the output of "nmap --iflist".
As a workaround you can try using the --unprivileged option to use plain
TCP connect scan.
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/