mailing list archives
Re: IPv6 Support on Windows
From: "Kris Katterjohn" <katterjohn () gmail com>
Date: Mon, 12 May 2008 00:27:53 +0530
On Sun, May 11, 2008 at 8:23 PM, jah <jah () zadkiel plus com> wrote:
Hey Jah, thanks for the report and tracking the problem down.
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?
Hmm.. I hadn't tried this until today. I got Nmap working across the
internet easily with hosts like www.kame.net, www.ipv6.org and
ipv6.google.com using Teredo ("netsh interface ipv6 set teredo
client"). Does this work for you?
I set up another box with IPv6 on my LAN and I'm now running into the
same problems with it that you are. I'll look into this more this
upcoming week if nobody has any ideas.
Sent through the nmap-dev mailing list
Archived at http://SecLists.Org
Re: IPv6 Support on Windows Kris Katterjohn (May 20)