Re: Nmap 6 bug: get_srcaddr

[David Fifield <david () bamsoftware com>]

On Wed, May 23, 2012 at 10:35:57AM +0200, Martin Clausen wrote:
> So I just upgraded to Nmap 6. While testing I ran into this little 
> problem:
>
> C:\Temp\server-lans>nmap -T3 -sn 10.80.0.0/16 -dd -vv
>
> Starting Nmap 6.00 ( http://nmap.org ) at 2012-05-23 10:30 Romance 
> Daylight Time
> 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 context.
> nexthost: failed to determine route to 10.80.0.0
> QUITTING!

Is this on Windows XP?

Does it work to scan the targets 10.80.1-254.1-254?

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