Re: Error on Windows 7 after installing nmap 7.30

[食肉大灰兔V5 <hsluoyz () gmail com>]

Hi Keith,


Please try latest Npcap 0.10 r10 here:
https://github.com/nmap/npcap/releases and try again. I have fixed a
related bug in that version.


Cheers,
Yang


On Mon, Oct 24, 2016 at 10:43 PM, Keith Christian <keith1christian () gmail com
> wrote:

> 7.31 was installed this morning and exhibits the same symptoms:
>
>
>         Mon 10/24/2016  8:36:12.40 C:\Users\keith\Downloads>nmap
> 192.168.2.5
>
>         Starting Nmap 7.31 ( https://nmap.org ) at 2016-10-24 08:36
> Mountain Daylight Time
>         dnet: Failed to open device eth1
>         QUITTING!
>
>
> Again: 7.12 works without issues.
>
> (Difficult to install "debug" builds on this corporate PC, sorry.)
>
> FWIW, Pertinent "systeminfo" output:
>
> OS Name:                   Microsoft Windows 7 Enterprise
> OS Version:                6.1.7601 Service Pack 1 Build 7601
> OS Manufacturer:           Microsoft Corporation
> OS Configuration:          Member Workstation
> OS Build Type:             Multiprocessor Free
>
>
> On Thu, Oct 13, 2016 at 11:09 PM, Keith Christian
> <keith1christian () gmail com> wrote:
> > Yang,
> >
> > Thanks, unable to do this on the Windows 7 machine which is a
> > corporate PC.  Get too many security pop-ups and execution of npcap
> > debug is denied.
> >
> > Hopefully someone can test this on a different Window 7 PC.  Nmap 7-12
> > works fine on this machine.
> >
> > Thanks for the reply.
> >
> > On Wed, Oct 12, 2016 at 5:57 AM, 食肉大灰兔V5 <hsluoyz () gmail com> wrote:
> > > Hi Keith,
> > >
> > > Please download latest Npcap 0.10 r7 debug version here:
> > > https://github.com/nmap/npcap/releases/download/v0.10-r7/
> npcap-0.10-r7-debug.exe.
> > > And try to run the Nmap command that has error again. Then submit the
> > > DiagReport and as many as possible kinds of logs documented here:
> > > https://htmlpreview.github.io/?https://github.com/nmap/
> npcap/blob/master/docs/npcap-guide-wrapper.html#npcap-issues.
> > > At least you need to submit these:
> > > 1) DiagReport-XXX.txt
> > > 2) install.log
> > > 3) NPFInstall.log
> > > 4) Packet.log
> > >
> > > If you want, you can also submit the output of DbgView for driver. I
> don't
> > > know if this issue relates to the driver for now, so you can either
> submit
> > > it or not.
> > >
> > >
> > > Cheers,
> > > Yang
> > >
> > >
> > > On Wed, Oct 12, 2016 at 2:43 AM, Daniel Miller <bonsaiviking () gmail com>
> > > wrote:
> > > > 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/