RE: Nmap 6 fails to initialize on Windows xp sp3

[Venkataramanappa Sathyanarayana <Sathyanarayana.V () technicolor com>]

Hi David,

Please find below the traces asked.

1) nmap --route-dst 2001:470:9388:4034:5a98:35ff:fe19:37fe
2001:470:9388:4034:5a98:35ff:fe19:37fe

eth0 eth0 srcaddr :: direct



Starting Nmap 6.00 ( http://nmap.org ) at 2012-05-23 10:25 Romance Daylight Time

Nmap done: 0 IP addresses (0 hosts up) scanned in 0.22 seconds

WARNING: No targets were specified, so 0 hosts scanned.


2) nmap -6 --packet-trace 2001:470:9388:4034:5a98:35ff:fe19:37fe

Starting Nmap 6.00 ( http://nmap.org ) at 2012-05-23 10:31 Romance Daylight Time

SENT (0.3590s) ICMPv6 (58) :: > ff02::1:ff19:37fe (type=135/code=0) hopl=255 flow=0 payloadlen=32

SENT (0.5630s) ICMPv6 (58) :: > ff02::1:ff19:37fe (type=135/code=0) hopl=255 flow=0 payloadlen=32

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.78 seconds

3) nmap --iflist



Starting Nmap 6.00 ( http://nmap.org ) at 2012-05-23 10:16 Romance Daylight Time

************************INTERFACES************************

DEV  (SHORT) IP/MASK                                   TYPE        UP   MTU  MAC

eth0 (eth0)  192.168.1.66/24                           ethernet    up   1500 B8:AC:6F:2E:C3:D3

eth0 (eth0)  2001:470:9388:4034:2dde:5925:6618:6744/64 ethernet    up   1500 B8:AC:6F:2E:C3:D3

eth0 (eth0)  2001:470:9388:4034:baac:6fff:fe2e:c3d3/64 ethernet    up   1500 B8:AC:6F:2E:C3:D3

eth0 (eth0)  fe80::baac:6fff:fe2e:c3d3/64              ethernet    up   1500 B8:AC:6F:2E:C3:D3

eth1 (eth1)  192.168.239.1/24                          ethernet    up   1500 00:50:56:C0:00:01

eth1 (eth1)  fe80::250:56ff:fec0:1/64                  ethernet    up   1500 00:50:56:C0:00:01

eth2 (eth2)  192.168.41.1/24                           ethernet    up   1500 00:50:56:C0:00:08

eth2 (eth2)  fe80::250:56ff:fec0:8/64                  ethernet    up   1500 00:50:56:C0:00:08

lo0  (lo0)   127.0.0.1/0                               loopback    up   1520

tun0 (tun0)  fe80::ffff:ffff:fffd/64                   point2point down 1280

tun1 (tun1)  (null)/0                                  point2point up   1280

tun2 (tun2)  fe80::5efe:c0a8:142/64                    point2point up   1280

tun2 (tun2)  fe80::5efe:c0a8:2901/64                   point2point up   1280

tun2 (tun2)  fe80::5efe:c0a8:ef01/64                   point2point up   1280

lo1  (lo1)   ::1/64                                    loopback    up   1500

lo1  (lo1)   fe80::1/64                                loopback    up   1500



DEV  WINDEVICE

eth0 \Device\NPF_{1AB61650-D0A9-4BF6-A215-9F34C0C0D9F2}

eth0 \Device\NPF_{1AB61650-D0A9-4BF6-A215-9F34C0C0D9F2}

eth0 \Device\NPF_{1AB61650-D0A9-4BF6-A215-9F34C0C0D9F2}

eth0 \Device\NPF_{1AB61650-D0A9-4BF6-A215-9F34C0C0D9F2}

eth1 \Device\NPF_{5035C5EF-2F3D-46F4-83CC-17CDAA6E71A7}

eth1 \Device\NPF_{5035C5EF-2F3D-46F4-83CC-17CDAA6E71A7}

eth2 \Device\NPF_{D8563F34-505F-49D7-A2C6-C322633A44BA}

eth2 \Device\NPF_{D8563F34-505F-49D7-A2C6-C322633A44BA}

lo0  <none>

tun0 \Device\NPF_{247E394B-1833-45EE-9377-8A93EA3F8CA8}

tun1 <none>

tun2 <none>

tun2 <none>

tun2 <none>

lo1  <none>

lo1  <none>



**************************ROUTES**************************

DST/MASK           DEV  GATEWAY

255.255.255.255/32 eth2 192.168.41.1

255.255.255.255/32 eth1 192.168.239.1

192.168.41.1/32    lo0  127.0.0.1

192.168.1.66/32    lo0  127.0.0.1

192.168.1.255/32   eth0 192.168.1.66

192.168.41.255/32  eth2 192.168.41.1

192.168.239.1/32   lo0  127.0.0.1

192.168.239.255/32 eth1 192.168.239.1

255.255.255.255/32 eth0 192.168.1.66

192.168.1.0/24     eth0 192.168.1.66

192.168.41.0/24    eth2 192.168.41.1

192.168.239.0/24   eth1 192.168.239.1

127.0.0.0/8        lo0  127.0.0.1

224.0.0.0/4        eth1 192.168.239.1

224.0.0.0/4        eth2 192.168.41.1

224.0.0.0/4        eth0 192.168.1.66

0.0.0.0/0          eth0 192.168.1.254


Regards
Sathya
 
Sathyanarayana Venkataramanappa
QACC Engineer
DIGITAL DELIVERY GROUP
Sathyanarayana.V () technicolor com
tel.: 32 344 36 522

Prins Boudewijnlaan 47  -  2650 Edegem  -  Belgium
Technicolor Delivery Technologies Belgium NV
Registered office (maatschappelijke zetel): Prins Boudewijnlaan 47, 2650 Edegem, Belgium
Company registration number (ondernemingsnummer): 0428837295 - RPR Antwerpen

Help preserve the color of our world - Think before you print.



-----Original Message-----
From: David Fifield [mailto:david () bamsoftware com] 
Sent: woensdag 23 mei 2012 1:01
To: Venkataramanappa Sathyanarayana
Cc: nmap-dev () insecure org
Subject: Re: Nmap 6 fails to initialize on Windows xp sp3

On Tue, May 22, 2012 at 02:54:12PM +0200, Venkataramanappa Sathyanarayana wrote:
> I tried Nmap6  on Windows XP SP3. As startup, Nmap performed address 
> resolution with Neighbor solicitation sent using unspecified address 
> and Source Link layer address option.
> Neighbor Solicitation message must not be sent with source as 
> unspecified address and having source link layer as specified in
> RFC4861 section 7.1.1. Snapshot of the same indicated in bold.

Can you post your complete Nmap output? We do use IPv6 source addresses when sending ND probes; it may be a bug that 
your source address is being calculated as ::.

What is the output of this command?

nmap --route-dst ff02::1:ff19:37fe

What is the output of

nmap --iflist

Do the packets appear when you use the --packet-trace option? If not, then they are being sent by the operating system, 
not by Nmap itself.

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