https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12846
Bug ID: 12846
Summary: Live capture from USBPcap fails immediately
Product: Wireshark
Version: 2.2.0
Hardware: x86
OS: Windows 10
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: Qt UI
Assignee: bugzilla-ad...@wireshark.org
Reporter: sinde...@marconi.ttc.cz
Build Information:
Version 2.2.0 (v2.2.0-0-g5368c50 from master-2.2)
Copyright 1998-2016 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with Qt 5.3.2, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 10, build 10586, with locale Czech_Czech
Republic.1250, with Npcap version 0.07, based on 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.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (with SSE4.2), with 8141MB of
physical memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
After upgrade to 2.2.0 including an upgrade to the version of USBPcap which
comes bundled with it, an attempt to capture on USBPcapN extcap interface fails
with the following error popups (the second one pops up after you confirm the
first one):
1. Error reading from pipe: operation has returned due to timeout expiration
(error 1460)
(the actual text may be different on English-speaking Windows 10, the meaning
remains).
2. Error by extcap pipe: C:\Program Files\Wireshark\extcap\USBPcapCMD.exe:
--devices : unknown option
The USBPcapCMD.exe seems to be the same like the one which came bundled with
the previous versions, so I suppose a change at Wireshark side has caused the
trouble. If it is a USBPcap issue (not keeping pace with evolution of the
extcap specification), please let me know, I'll file a bug at USBPcap's github
page.
tshark falls into the same hole:
C:\WINDOWS\system32>"c:\Program Files\Wireshark\tshark.exe" -D
...
9. \\.\USBPcap1 (USBPcap1)
10. \\.\USBPcap2 (USBPcap2)
11. \\.\USBPcap3 (USBPcap3)
C:\WINDOWS\system32>"c:\Program Files\Wireshark\tshark.exe" -i 9
Capturing on 'USBPcap1'
tshark: Error reading from pipe: Dana operace se vratila, protoze vyprsel
casovy limit.
(error 1460)
tshark: Error by extcap pipe: c:\Program Files\Wireshark\extcap\USBPcapCMD.exe:
--devices : unknown option
0 packets captured
Just a NB, in the GUI, I could not find where the form with the parameters
which the extcap binary offers as configurable ones has moved (if it hasn't
just disappeared).
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
