Re: Error on Windows 7 after installing nmap 7.30

[Daniel Miller <bonsaiviking () gmail com>]

Keith,

This does sound like a different problem than I experienced. I've CC'd Yang
Luo, who is primarily responsible for the Npcap packet capture library,
which may be related. Please continue to keep the dev () nmap org mailing list
CC'd so that others can help or benefit from the discussion in the archives.

To ensure this is not a symptom of a different problem which has already
been fixed, please download and install the latest Npcap 0.10 r7 from
https://github.com/nmap/npcap/releases . If the problem persists, please
run (as administrator) the DiagReport.bat script that is installed along
with Npcap and attach the generated diagnostic file to a reply (this can be
off-list to Yang and myself, since it contains detailed system info). It
would also be helpful to have the output of `nmap --iflist`, and any
security software or filter drivers that you may have installed that could
be blocking or interfering with Nmap's operation.

If none of this turns up any obvious problems, I will try to build a
debugging/test build of Nmap 7.30 that will allow us to trace the call to
libdnet's eth_open function to see exactly which of several places is
causing it to return NULL (resulting in the error you saw.). This could
happen because:

1. we are unable to get the pcap device name for the name "eth1"
2. we are unable to allocate space for the eth_t (unlikely)
3. we are unable to open the adapter via Npcap
4. we are unable to allocate a packet buffer for the adapter
5. we are unable to get the network type via PacketGetNetType

Dan

On Oct 11, 2016 12:33 PM, "Keith Christian" <keith1christian () gmail com>
wrote:

> Yes it does, nmap 7.30 does not work at all except for simple things
> like nmap -sL IP_ADDRESS.
>
> On Sun, Oct 9, 2016 at 4:45 AM, Daniel Miller <bonsaiviking () gmail com>
> wrote:
> > Keith,
> >
> > Thanks for bringing this to our attention. I have seen the "failed to
> open
> > device" error before, but it usually only happens once, and subsequent
> runs
> > are not affected. Does the error persist beyond the first run?
> >
> > Dan
> >
> >
> > On Oct 7, 2016 11:47 AM, "Keith Christian" <keith1christian () gmail com>
> > wrote:
> > > I re-installed this on the Windows 7 machine as Administrator and no
> > > improvement.  Never had this issue with Windows Nmap before.
> > >
> > > Hope the development team will have a few minutes to look at this
> > > soon, thanks in advance for creating Nmap and your continuing efforts.
> > >
> > > On Tue, Oct 4, 2016 at 2:59 PM, Keith Christian
> > > <keith1christian () gmail com> wrote:
> > > > When running nmap getting this error:
> > > >
> > > > Starting Nmap 7.30 ( https://nmap.org ) at 2016-10-04 07:53 Mountain
> > > > Daylight Time
> > > > dnet: Failed to open device eth1
> > > > QUITTING!
> > > >
> > > > NMap has never reported an error for device "eth1" on Windows before.
> > > _______________________________________________
> > > Sent through the dev mailing list
> > > https://nmap.org/mailman/listinfo/dev
> > > Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/