mailing list archives
Re: IPv6 Support on Windows
From: jah <jah () zadkiel plus com>
Date: Sun, 11 May 2008 15:53:55 +0100
On 03/05/2008 16:56, Kris Katterjohn wrote:
I've attached an incredibly simple patch to add IPv6 support on
Windows. The only other thing you need to do to make it work is to
actually install IPv6 (details are in the "Installation,
Configuration, and Use" section here). Vista users have IPv6
installed by default.
I got this working easily with same basic development environment I
have always used, which is described here (Windows XP, VC++ 2005
Express w/Platform SDK, etc.).
Please test and let me know how it goes; I'll commit it once I get a
few yays :) Hopefully it'll be as simple for you as it was for me!
I've got IPv6 installed on two directly connected XP machines (this
didn't need a download, it is already present and just requires
installing). My router does not support IPv6, but I guess for directly
connected hosts, the magic happens at layer 2.
I can ping each machine from the other and capture ICMPv6 (Echo request
and reply and Neighbor solicitation and advertisement) traffic with
wireshark. In order to do this, I have to append the link-local
interface number (so-called Zone ID)  to the address like so:
if I don't append %6 I get "Destination *net* unreachable" from ping.
If I run nmap like so:
nmap -6 -n -PN -sT -d9 -p80 fe80::20f:b5ff:fe47:7879%6
I get a Reason "host-unreach" - as I do if I don't append the %6 to the
I stepped my way through the code and confirmed that I get 10065
WSAEHOSTUNREACH "No route to host". And I found that the %6 is lost
during Target::GenerateIPString() in Target.cc and this seems to be down
to the code in inet_ntop.c - bit vague, I know.
So, have I missed something or is this something that needs doing to
nbase? Has anyone else managed to use IPv6 on directly connected targets?
 - How do I ping?
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org
Re: IPv6 Support on Windows Kris Katterjohn (May 20)