Nmap Development mailing list archives

Re: Nmap and IPv6


From: "DePriest, Jason R." <jrdepriest () gmail com>
Date: Fri, 17 Oct 2008 21:13:14 -0500

I am having some general problems with IPv6 scanning with nmap.

I have two systems on a wireless LAN that have IPv6 addresses.  They
can ping each other.

Nmap says no, sir.

Laptop running nmap - fe80::a800:4ff:fe00:a04
System I am scanning - fe80::210:5aff:fe1d:5c3f

Hey, look!  I can ping it!
depriest@hole:~$ ping6 -I eth2 fe80::210:5aff:fe1d:5c3f
PING fe80::210:5aff:fe1d:5c3f(fe80::210:5aff:fe1d:5c3f) from
fe80::a800:4ff:fe00:a04 eth2: 56 data bytes
64 bytes from fe80::210:5aff:fe1d:5c3f: icmp_seq=1 ttl=64 time=1.07 ms
64 bytes from fe80::210:5aff:fe1d:5c3f: icmp_seq=2 ttl=64 time=1.04 ms
64 bytes from fe80::210:5aff:fe1d:5c3f: icmp_seq=3 ttl=64 time=1.07 ms
64 bytes from fe80::210:5aff:fe1d:5c3f: icmp_seq=4 ttl=64 time=1.46 ms
^C
--- fe80::210:5aff:fe1d:5c3f ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3010ms
rtt min/avg/max/mdev = 1.040/1.164/1.460/0.173 ms

Nmap is sad.
depriest@hole:~$ sudo nmap -sP -6 fe80::210:5aff:fe1d:5c3f

Starting Nmap 4.76 ( http://nmap.org ) at 2008-10-17 21:06 CDT
Strange error from connect (22):Invalid argument
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 0.21 seconds

What is this "invalid argument" it speaks of?

Dunno, but here is a more informative error messge.
CONN (0.2710s) TCP localhost > fe80::210:5aff:fe1d:5c3f:22 => Invalid argument

I did a fancier scan and ended up with 2000 of those.
depriest@hole:~$ grep "Invalid argument" nmap-ipv6.nmap | wc -l
2000

I am attaching the log file for someone who knows more about nmap -6 to look at.

Thanks in advance folks.

-Jason

Attachment: nmap-ipv6.nmap.bz2
Description:


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

Current thread: