Wireshark mailing list archives
Re: Problems with \Device\NPF_ prefix
From: Gisle Vanem <gisle.vanem () gmail com>
Date: Fri, 12 Jan 2018 09:07:32 +0100
I wrote:
In my recently built Tshark/Wireshark etc., I've discovered this longer works: tshark.exe -i \Device\NPF_{3A46ACA0-CBED-44BC-A239-6AEA3D0C451D} It says: Capturing on '\Device\NPF_{3A46ACA0-CBED-44BC-A239-6AEA3D0C451D}' tshark: The capture session could not be initiated on interface '\Device\NPF_{3A46ACA0-CBED-44BC-A239-6AEA3D0C451D}' (Error opening adapter: Operasjonen er utført. (0)). << == NO_ERROR !!?? But this works: tshark.exe -i {3A46ACA0-CBED-44BC-A239-6AEA3D0C451D}
It has been fixed by removing the Win10Pcap installation and reinstalling the trust old WinPcap. All back to normal. I had Win10Pcap and WinPcap installed at the same time. -- --gv ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Problems with \Device\NPF_ prefix Gisle Vanem (Jan 11)
- Re: Problems with \Device\NPF_ prefix Gisle Vanem (Jan 12)