Nmap Development mailing list archives

RE: nmap 6.01 requested address is not valid bug


From: "security-lists" <security-lists () fnci com>
Date: Sun, 8 Jul 2012 11:29:53 -0500

Ron,

Thanks.  Here are the results:

1. nmap -sS -O 192.168.1.0/24  <<< "hung" with no output for a "while" until
I             CTRL-C'd it.  But did not fail with same message.  

2. nmap -sS -O 10.250.1.91     <<< worked as expected!!!

3. nmap -sS -O 10.250.1.1-255  <<< worked as expected!!!

4. Non-RFC's works on v4.20 and v6.1.

5. Debugging:
C:\Documents and Settings\Me>nmap -vv -dd 10.250.1.0/24

Starting Nmap 6.01 ( http://nmap.org ) at 2012-07-08 10:52 Central Daylight
Time

Fetchfile found C:\Program Files\Nmap/nmap-services
PORTS: Using top 1000 ports found open (TCP:1000, UDP:0, SCTP:0)
Winpcap present, dynamic linked to: WinPcap version 4.1.2 (packet.dll
version 4.
1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
NPF service is already running.
Fetchfile found C:\Program Files\Nmap/nmap.xsl
The max # of sockets we are using is: 0
--------------- Timing report ---------------
  hostgroups: min 1, max 100000
  rtt-timeouts: init 1000, min 100, max 10000
  max-scan-delay: TCP 1000, UDP 1000, SCTP 1000
  parallelism: min 0, max 0
  max-retries: 10, host-timeout: 0
  min-rate: 0, max-rate: 0
---------------------------------------------
get_srcaddr: can't connect socket: The requested address is not valid in its
con
text.
Failed to convert source address to presentation format!?!  Error: Unknown
error

QUITTING!

6. I overlaid pcap 4.1.2 with same version, no go.  Then I stepped-back all
the way to pcap v4.0, no go.

7. I removed nmap v6.1 and reinstalled nmap v4.20:

C:\Documents and Settings\Me>nmap -sP 10.250.1.0/24

Starting Nmap 4.20 ( http://insecure.org ) at 2012-07-08 11:08 Central Dayli
Time
Host 10.250.1.3 appears to be up.
MAC Address: REDACTED
Host 10.250.1.10 appears to be up.
MAC Address: REDACTED
Host 10.250.1.16 appears to be up.
MAC Address: REDACTED
Host 10.250.1.21 appears to be up.
MAC Address: REDACTED
Host 10.250.1.91 appears to be up.
MAC Address: REDACTED
Host 10.250.1.92 appears to be up.
MAC Address: REDACTED
Host 10.250.1.97 appears to be up.
Host 10.250.1.98 appears to be up.
MAC Address: REDACTED
Host 10.250.1.145 appears to be up.
MAC Address: REDACTED
Host 10.250.1.150 appears to be up.
MAC Address: REDACTED
Nmap finished: 256 IP addresses (10 hosts up) scanned in 13.047 seconds

I don't have handy any previous v6 binaries except v4.20.  I'd be happy to
test any v5 compiles.  But it does seem to be a new issue in later releases
from what v4.20 gives me.

For now, I'm happy to be able to scan with .1-255 syntax but ....


::Robert

-----Original Message-----
From: Ron [mailto:ron () skullsecurity net] 
Sent: Saturday, July 07, 2012 23:59
To: security-lists
Cc: nmap-dev () insecure org
Subject: Re: nmap 6.01 requested address is not valid bug

I can't reproduce. Running Win7 Starter and Nmap 6.01:

C:\Program Files\Nmap>nmap -sS -O 10.250.1.0/24

Starting Nmap 6.01 ( http://nmap.org ) at 2012-07-07 21:57 Pacific 
Daylight Time

Stats: 0:00:33 elapsed; 0 hosts completed (0 up), 256 undergoing Ping Scan
Ping Scan Timing: About 14.16% done; ETC: 22:00 (0:03:08 remaining)
...

Does this happen with other addresses? Non-RFC1918 addresses? Single 
hosts (not /24)? /24 if denoted as x.x.x.1-255 instead?

Ron

On 7/7/2012 8:46 PM, security-lists wrote:
I still find v6,01 has the "this requested address is not valid," bug.
Can
someone verify?

Platform: Windows XP Home SP3


C:\Documents and Settings\Me>nmap -sS -O 10.250.1.0/24

Starting Nmap 6.01 ( http://nmap.org ) at 2012-07-07 22:20 Central
Daylight
Time

get_srcaddr: can't connect socket: The requested address is not valid in
its
con
text.
Failed to convert source address to presentation format!?!  Error: Unknown
error

QUITTING!


::Robert


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


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


Current thread: