Question on NPing Function

["Farley, Rob " <rob.farley () citi com>]

I currently have two versions of NMAP installed on my laptop.  Version 5.5.1 and 6.01.  My laptop is a Windows 7 64bit 
laptop with SP1 installed.

The Version 5.5.1 worked flawlessly (and still does) for both NPING and NMAP.  Both versions, 6.0 and 6.0.1 failed to 
resolve target hosts when attempting to run NPING or NMAP against another host.  I was able to verify the host was up 
by using normal PING and TRACERT utilities.

I ran NMAP -iflist under both versions to see their output.

Version 5.5.1 Output of NMAP -iflist:

Version 6.01 Output of NMAP -iflist:

When I use NPING 5.5.1 version to ping a host, I get this: (GOOD RESULT)
Starting Nping 0.5.51 ( http://nmap.org/nping ) at 2012-08-20 12:40 Central Daylight Time
SENT (0.6890s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=43338 iplen=28
RCVD (0.6890s) ICMP ************ > ************Echo reply (type=0/code=0) ttl=125 id=19221 iplen=28
SENT (2.0610s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=43338 iplen=28
RCVD (2.0610s) ICMP ************ > ************Echo reply (type=0/code=0) ttl=125 id=19393 iplen=28
SENT (3.0660s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=43338 iplen=28
RCVD (3.0660s) ICMP ************ > ************Echo reply (type=0/code=0) ttl=125 id=19556 iplen=28
SENT (4.0700s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=43338 iplen=28
RCVD (4.0700s) ICMP ************ > ************Echo reply (type=0/code=0) ttl=125 id=19792 iplen=28
SENT (5.0730s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=43338 iplen=28
RCVD (5.0730s) ICMP ************ > ************Echo reply (type=0/code=0) ttl=125 id=19983 iplen=28

Max rtt: 1.000ms | Min rtt: 1.000ms | Avg rtt: 1.000ms
Raw packets sent: 5 (210B) | Rcvd: 5 (230B) | Lost: 0 (0.00%)
Tx time: 4.38700s | Tx bytes/s: 47.87 | Tx pkts/s: 1.14
Rx time: 5.38800s | Rx bytes/s: 42.69 | Rx pkts/s: 0.93
Nping done: 1 IP address pinged in 6.09 seconds

When I use NPING 6.0.1 version to ping a host, I get this: (BAD RESULT)
Starting Nping 0.6.01 ( http://nmap.org/nping ) at 2012-08-20 12:50 Central Daylight Time
Device used for target host ************ seems to be down.
SENT (0.4060s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=61902 iplen=28
SENT (1.4080s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=61902 iplen=28
SENT (2.4080s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=61902 iplen=28
SENT (3.4080s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=61902 iplen=28
SENT (4.4100s) ICMP ************> ************ Echo request (type=8/code=0) ttl=64 id=61902 iplen=28

Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A
Raw packets sent: 5 (140B) | Rcvd: 0 (0B) | Lost: 5 (100.00%)
Tx time: 4.00500s | Tx bytes/s: 34.96 | Tx pkts/s: 1.25
Rx time: 5.00500s | Rx bytes/s: 0.00 | Rx pkts/s: 0.00
Nping done: 1 IP address pinged in 5.43 seconds


If I use the NPING 5.5.1 and specify the eth6 adapter using the -e option, I get a successful ping.  ETH6 being the 
Ethernet adapter that this version of NPING detects as my active network connection.
If I use the NPING 6.0.1 and specify the eth1 adapter using the  -e option, I get this:
        Starting Nping 0.5.51 ( http://nmap.org/nping ) at 2012-08-20 13:26 Central Daylight Time
Failed to determine route to host ************. Skipping it...
Execution aborted. Nping needs at least one valid target to operate.


Viewing a wireshark capture, I can see good responses going back and forth between the client and target.  When running 
NPING 6.0.1, I can see a DNS name resolution request and response, but no traffic is ever sent to the target host.

I love this tool and would like to remain current.  Please advise if this is a known issue, or if there is a fix for 
the latest version.  I did some investigation and only found generic references.

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