Hmm, i ran into the issue that the npcap loopback adapter didn‘t showed up in the latest Wireshark 3.0.1 after installing it in a Win10 1809 VM. No matter what I did. The adapter was installed and shown in the device manager but not in Wireshark. After I installed the Linux subsystem it showed up and worked flawlessly.
Regards, Manuel König Mit freundlichen Grüßen/ Best regards Manuel König Product Manager / Technical Support T: +49 911 9728230 F: +49 911 9728233 E: [email protected] iba AG Supervisory Board: Horst Anhaus, Chairman; Management Board: Dr. Ulrich Lettau CEO, Marta Anhaus CFO, Harald Opel COO; Entry in the Commercial Register of Fuerth District Court (Amtsgericht): HRB 9865 Identification number for turnover tax, Vat. Reg. No. DE 132760166, WEEE-Reg.No. DE11469996 On Mon, May 6, 2019 at 6:00 PM +0200, "Jaap Keuter" <[email protected]<mailto:[email protected]>> wrote: As does using Npcap as capture engine. On 6 May 2019, at 15:42, Manuel König via Wireshark-dev <[email protected]<mailto:[email protected]>> wrote: Hi, I stumbled upon the wiki article about the Loopback capture setup (https://wiki.wireshark.org/CaptureSetup/Loopback). Under Supported Platforms it's stated that it's not possible to capture loopback traffic on Windows. I would add an asterisk to that, because on Windows 10 with the Subsystem for Linux installed you are able to capture this kind of traffic. Mit freundlichen Grüßen/Best regards Manuel König Product Manager/Technical Support
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
