Gordon Fyodor Lyon

For the purpose of prioritization, I'm just noting that we had a customer recently request Virtual Function driver support on behalf of one of their customers who was using the...

Thanks folks. Will anyone still experiencing this please let us know your Npcap version number and what sort of (virtual) adapter software you are using? We did include support for...

Added a bullet point about only enabling promiscuous mode when necessary based in this note that @dmiller-nmap sent to a customer: > Promiscuous mode (https://npcap.com/guide/wpcap/pcap.html#promiscuous) is used to capture incoming...

Hi @aklassen-appneta. Thanks for the suggestion. The Npcap installer itself is 32-bit for maximum compatibility while it installs native drivers and DLL's for the target architectures (x86, x64, ARM64). Did...

@guyharris - that would be a good solution. We are considering moving to (or at least offering) an MSI package version ([Issue #103](https://github.com/nmap/npcap/issues/103)).

Update: As of 9/23/24, me and @dmiller-nmap can still reproduce this with Nmap 7.95. The issue is just that Windows takes so long to notify us about the RST. If...

Good find! With #2139 now fixed, this might be the last thing we have to revolve before we can make the more efficient IOCP engine the default on Windows!

Thanks for the note about WSL2. That is great news if it turns out to work with Nmap. And I agree that the best solution would be for WSL/WSL2 compatability...

Thanks for the suggestion, @anrossi. Deciding which NDIS versions to support is tricky since we need to create a different driver for each platform for each release for each NDIS...

An issue somewhat related to this is the desire for hardware timestamp support discussed in #581 . That one requires NDIS 6.82 or newer, which is also newer than we...