Home page logo
/

nmap-dev logo Nmap Development mailing list archives

IPv6 Local Link support in NSE
From: Kurt Grutzmacher <grutz () jingojango net>
Date: Tue, 25 Oct 2011 15:50:14 -0700

This may be very limited in use-case. When using IPv6 Local Link addressing
(fe80::0/64) NSE can not send packets to its targets because they do not
contain the transport interface. Originating system is Linux, target is
Windows 2003.

Attempts to connect return:

NSOCK (1.4540s) Callback: READ ERROR [Transport endpoint is not connected
(107)] for EID 354 [fe80::20c:29ff:fe0a:c682:445]
NSOCK (1.4540s) Callback: READ ERROR [Transport endpoint is not connected
(107)] for EID 362 [fe80::20c:29ff:fe0a:c682:445]
NSOCK (1.4540s) Callback: READ ERROR [Transport endpoint is not connected
(107)] for EID 370 [fe80::20c:29ff:fe0a:c682:445]

nmap of course has no problem connecting and discovering tcp/445 open.

Nmap scan report for fe80::20c:29ff:fe0a:c682
Host is up, received nd-response (0.00021s latency).
Scanned at 2011-10-25 15:44:47 PDT for 5s
PORT    STATE SERVICE      REASON
445/tcp open  microsoft-ds syn-ack
MAC Address: 00:0C:29:0A:C6:82 (VMware)

--
 Kurt Grutzmacher -=- grutz () jingojango net
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/


  By Date           By Thread  

Current thread:
  • IPv6 Local Link support in NSE Kurt Grutzmacher (Oct 25)
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault