olzmob.blogg.se

" section does not change regardless of which capture driver is used.

This only affects which user space DLL Wireshark loads, there is no change in functionality as currently Wireshark is compiled with the WinPcap SDK so can only use the API originally exposed by WinPcap that is also supported by npcap. If it doesn't find npcap then it will fall back to WinPcap. Wireshark 3.x and later will first check for npcap and if found use that. With GnuTLS 3.6.3, with Gcrypt 1.8.3, with brotli 1.0.2, binary plugins Locale English_United Kingdom.1252, with WinPcap version 4.1.3 (packet.dll

With WinPcap installed I get the following: Locale English_United Kingdom.1252, with Npcap version 0.9983, based on libpcap I7-8550U CPU 1.80GHz (with SSE4.2), with 16225 MB of physical memory, with Running on 64-bit Windows 10 (1903), build 18362, with Intel(R) Core(TM) Resolver, with nghttp2 1.39.2, with brotli, with LZ4, with Zstandard, with With npcap installed I get the following (I have emphasised the important part):Ĭompiled (64-bit) with WinPcap SDK (WpdPack) 4.1.2, with GLib 2.52.3, with zlibġ.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4, with GnuTLS 3.6.3Īnd PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos, with MaxMind DB " section to see what Wireshark has found and is using. " section of the output rather than the "Compiled with. The answer from is almost correct but you need to look at the "Running on.