We are not going to put effort towards fixing this since WinPcap API-compatible mode is a temporary shim to allow the ongoing use of software which has not been updated to use Npcap directly. Npcap in WinPcap API-compatible mode does not provide loopback traffic capture.We are working with the Wireshark developers to change this, since Npcap has become much more stable and WinPcap is no longer supported. Wireshark uses WinPcap when it finds it instead of Npcap.The Npcap native API is installed alongside the WinPcap API, and can still properly capture loopback traffic (I tested this using Nmap and the targets-sniffer NSE script). WinPcap did not offer loopback capture, so Npcap's WinPcap-compatible API does not, either. I can confirm this happens when Npcap is installed in WinPcap API-compatibility mode, which is caused by Wireshark preferring WinPcap over Npcap.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |