Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Scans failing on Win32 - failures differ depending on args len (maybe)
From: jah <jah () zadkiel plus com>
Date: Fri, 07 Oct 2011 13:18:01 +0100

Hello,

I'm having a problem with latest svn, 5.61TEST2 and 5.61TEST1 on Win32
where scans exit with pcap and dnet errors.

The failures differ depending on the command arguments given and the
'shell' in which the command is executed - I get different errors in
MS-DOS, Cygwin and VC++ for the same arguments and it appears that
it's the overall length of command arguments which is significant
rather than the combination of arguments or targets.

Here's some example commands and the outcome for different shells
(the VC++ is a debug binary, the others are release binaries and
both were built from the same revision; eth0 is a perfectly ordinary
ethernet device):

nmap -F -v -v -d -n 195.166.128.231
VC++   - FAIL - dnet: Failed to open device eth0\nQUITTING!
Cygwin - FAIL - pcap_open_live(eth0, 256, 0, 2) FAILED.
                Reported error: Error opening adapter:
                The system cannot find the device specified. (20).
                Will wait 5 seconds then retry.
                ... Call to pcap_open_live() failed three times.
MS-DOS - FAIL - route_dst_generic: Failed to obtain system routes:
                getsysroutes_dnet: sysroutes_dnet_find_interfaces()
                failed

nmap -F -v -d -n 195.166.128.231
VC++   - FAIL - route_dst_generic: Failed to obtain system routes:
                getsysroutes_dnet: sysroutes_dnet_find_interfaces()
                failed
Cygwin - FAIL - pcap_open_live(eth0, 256, 0, 2) FAILED.
                Reported error: Error opening adapter:
                The system cannot find the device specified. (20).
                Will wait 5 seconds then retry.
                ... Call to pcap_open_live() failed three times.
MS-DOS - SUCCESS

nmap -p 180 -v -v -d -n 195.166.128.231
VC++   - SUCCESS
Cygwin - SUCCESS
MS-DOS - SUCCESS

The same commands with a different target:

nmap -F -v -v -d -n 84.92.6.208
VC++   - FAIL - dnet: Failed to open device eth0\nQUITTING!
Cygwin - FAIL - dnet: Failed to open device eth0\nQUITTING!
MS-DOS - SUCCESS

nmap -F -v -d -n 84.92.6.208
VC++   - FAIL - dnet: Failed to open device eth0\nQUITTING!
Cygwin - FAIL - dnet: Failed to open device eth0\nQUITTING!
MS-DOS - FAIL - pcap_open_live(eth0, 256, 0, 2) FAILED.
                Reported error: Error opening adapter:
                The system cannot find the device specified. (20).
                Will wait 5 seconds then retry.
                ... Call to pcap_open_live() failed three times...

nmap -p 180 -v -v -d -n 84.92.6.208
VC++   - SUCCESS
Cygwin - SUCCESS
MS-DOS - SUCCESS

I can get any of the scans which fail to succeed simply by adding more
arguments to a command, for example, adding an explicit ping type or
adding --traceroute.

I've not yet had the time to investigate fully, but I'll attempt to do
so this weekend.  In the meantime, does this make any sense to anyone?
Is there any known reason why the length of command arguments might
affect the the outcome in this rather bizarre fashion?

Best,

jah

_______________________________________________
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:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault