Daniel Miller
Daniel Miller
wpcap.dll symbols are now distributed in the DebugSymbols package for Npcap 0.9991 and later. This issue is now about documentation for debugging/profiling Npcap.
Should be fixed in be9c6d96ee3285d7dcbced539282c8a8132dcea7. Let us know if you continue to have problems.
We've confirmed this issue, but we don't know why it's happening. Neither Npcap nor the "NDIS Sample LightWeight Filter" driver from [Microsoft/Window-driver-samples](https://github.com/Microsoft/Windows-driver-samples/) can bind to the VF adapter. I can't...
Thanks so much for the insight, @jtippet! As @pc500 points out, in this setup the Hyper-V Virtual Ethernet Adapter is not present, so I think Npcap will be unable to...
@tamwoza WinPcap was a Protocol driver, not a filter driver, so it attached to the stack in a very different place. Npcap is architecturally different than WinPcap, so we will...
This issue should be resolved in Npcap 1.80, but we would appreciate if someone with the Broadcom NetXtreme adapter could confirm.
@nodeez @pc500 Thanks so much for confirming! We'll consider this issue closed.
@joshuafc Thanks for reporting this. I extracted all 3 architectures of `wpcap.dll` from our installer and verified that `pcap_oid_get_request` is exported using `dumpbin /exports` . I also see it in...
Duplicate of #2854
Duplicate of #2754