 | 1 | initial version |
From your Wireshark Help -> About Wireshark information:
Running on 64-bit Windows 7 Service Pack 1, build 7601, with Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz (with SSE4.2), with 4006 MB of physical memory, with locale English_United States.1252, with WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.6.3, with Gcrypt 1.8.3, without AirPcap, binary plugins supported (14 loaded). Built using Microsoft Visual Studio 2017 (VC++ 14.16, build 27030).
Note without AirPcap.
Compare to the relevant information from my system:
Running on 64-bit Windows 10 (1809), build 17763, with Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz (with SSE4.2), with 16225 MB of physical memory, with locale English_United States.1252, with light display mode, without HiDPI, with Npcap version 0.996, based on libpcap version 1.9.1-PRE-GIT, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with brotli 1.0.2, with AirPcap 4.1.0 build 1622, binary plugins supported (19 loaded). Built using Microsoft Visual Studio 2017 (VC++ 14.15, build 26730).
You may want to try to reinstall the AirPcap drivers or contact Riverbed for support. Until Wireshark sees with AirPcap 4.1.0 build 1622 or equivalent, it's not going to recognize your AirPcap adapter.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
