Nmap Development mailing list archives
Re: problems when migrating from winpcap to npcap
From: Daniel Miller <bonsaiviking () gmail com>
Date: Mon, 18 Mar 2019 09:30:17 -0500
Thanks Jens and Werner for reporting this issue. This is a known problem with the Npcap 0.99-r9 installer (https://github.com/nmap/nmap/issues/1456) that will be fixed an upcoming release that is currently in final testing. Dan On Sun, Mar 17, 2019 at 1:21 AM Jens Rupp <jens.rupp () paessler com> wrote:
Hi, I get the same error (see attached image) with the r9 oem version. Client is Windows 10 64bit. With the r7 release it works. Thanks, Jens Rupp *From:* dev <dev-bounces () nmap org> *On Behalf Of *w.henze () avm de *Sent:* Donnerstag, 7. März 2019 14:29 *To:* dev () nmap org *Subject:* problems when migrating from winpcap to npcap Hi to all! I was just migrating from latest winpcap to npcap 0.99-r9. First problem is the installer (installed npcap as part of wireshark). I kept the default checkbox settings and enabled the setting for winpcap compatibility. The installer then fails to write "C:\program files\npcap\npinstall2.exe" (or so). It will not proceed if I press ignore or retry. The only way to solve this was to manually deinstall winpcap and press cancel during this error message of the npcap installer. Now that I got npcap installed wireshark works. But my own tools that still use the winpcap API fail. My tool tries to open all non-loopback network devices. First step is to pcap_findalldevs and filter out all pcap_if_t *pNic with pNic->flags & PCAP_IF_LOOPBACK. This used to work, but now does not work. My MS loopback network adapter is not recognized as a loopback device. Second step is to "pcap_open_live(pNic->name, 65535, 0, 1, errbuf);". This works on my primary network interface but fails on my secondary network interface (where all the test equipment is connected to). The error I get is "failed to set hardware filter to non-promiscuous mode". The npcap installer claims that npcap can be installed winpcap compatible. But this is not true. npcap does not mark loopback devices correctly and it fails on some network devices. Is somebody interested in fixing this? Do you need more information from me? The failing network card is an "Intel(R) Gigabit CT Desktop Adapter" with Intel driver 12.7.28.0. OS is Windows 7 x64. Mit freundlichen Grüßen/Best regards Werner Henze _______________________________________________ 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/
Current thread:
- problems when migrating from winpcap to npcap w . henze (Mar 07)
- Re: problems when migrating from winpcap to npcap w . henze (Mar 07)
- RE: problems when migrating from winpcap to npcap Jens Rupp (Mar 16)
- Re: problems when migrating from winpcap to npcap Daniel Miller (Mar 18)