[prev in list] [next in list] [prev in thread] [next in thread]
List: wireshark-dev
Subject: Re: [Wireshark-dev] Problems with \Device\NPF_ prefix
From: Gisle Vanem <gisle.vanem () gmail ! com>
Date: 2018-01-12 8:07:32
Message-ID: 131f31cc-541e-f742-9a75-696a88b33b6b () gmail ! com
[Download RAW message or body]
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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic