Re: Nmap 6.01 not working on Windows 7

[Jake Moe <jakesaddress () gmail com>]

On 4 July 2012 00:13, Rob Nicholls <robert () robnicholls co uk> wrote:

> > -----Original Message-----
> > From: nmap-dev-bounces () insecure org [mailto:nmap-dev-
> > bounces () insecure org] On Behalf Of Jake Moe
> > Sent: 03 July 2012 06:37
> > To: nmap-dev () insecure org
> > Subject: Nmap 6.01 not working on Windows 7
>
> > If I uninstall v6.01 and reinstall v5.51, it works again.  Reverse the
> process and
> > it doesn't work without --unprivilged and even then, as I said, it works
> much
> > slower.
>
> It wouldn't hurt to send the output from --iflist (inline is fine), but I
> wouldn't be surprised if this is caused by some of the interface/route
> issues that are affecting a number of other people. It appeared to work
> fine
> up until 5.51 (I think 5.51SVN-dnet-pcap2 in March 2011 was fine too), but
> I
> think the introduction of IPv6 support with 5.52 has broken something. For
> some reason my Nmap 6 thinks that all routes should use eth2, even for
> hosts
> on the local subnet for eth1. Djalal was looking into fixing this on Linux,
> but his patch seems to break the routes completely on Windows (to be fair,
> I
> wasn't expecting this to work as he did say it wouldn't). You might be able
> to get Nmap 6 to work correctly by forcing it to use the correct interface
> (e.g. "-e eth1"), assuming this is a routing issue and not some other issue
> - if forcing the interface works, do let us know! Using --unprivileged will
> force Nmap to use the OS to send it (instead of using WinPcap), and Windows
> will know the correct interface and route to use, which is probably why it
> works.
>
> Rob

Using -e <interface> works a treat.  I assume then that this is your known
problem.  Thanks for the help.

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