https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12930
Bug ID: 12930
Summary: infinite loop in "dumpcap -L" with rpcap:// interface
in 2.2.0
Product: Wireshark
Version: 2.2.0
Hardware: x86
OS: Windows 7
Status: UNCONFIRMED
Severity: Major
Priority: Medium
Component: Common utilities (libwsutil)
Assignee: bugzilla-ad...@wireshark.org
Reporter: luky...@hotmail.com
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 (32-bit) with Qt 5.3.2, with WinPcap (4_1_3), with GLib 2.38.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 7 Service Pack 1, build 7601, with locale
German_Germany.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.2.15,
with Gcrypt 1.6.2, with AirPcap 4.1.0 build 1622.
Intel(R) Core(TM) i5-4210M CPU @ 2.60GHz (with SSE4.2), with 8073MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 40629
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Hello,
dumpcap (and wireshark, if using that dumpcap feature) hangs using a full CPU
core since 2.2.0 in the following conditions:
- OS is Windows (I'm unable to get rpcap working at all in Linux)
- interface is remote ("rpcap://...")
- dumpcap is trying to read the link type (-L)
Old stable 2.0.6 (and any other older build) works fine:
Wireshark206Portable\App\Wireshark>dumpcap -i rpcap://[172.22.0.12]/eth0 -L
Data link types of interface rpcap://[172.22.0.12]/eth0 (use option -y to set):
EN10MB (Ethernet)
Wireshark206Portable\App\Wireshark>
2.2.0 hangs (presumed infinite loop):
Wireshark220Portable\App\Wireshark>dumpcap -i rpcap:// [172.22.0.12]/eth0 -L
<<--- hangs using a full CPU core
Wireshark, if using this dumpcap feature hangs as well (when adding remote
interfaces).
Wireshark 2.0.6 and previous releases work fine.
Capturing traffic actually still works fine, only the -L knob is affected (but
when adding remote interfaces to Wireshark that knob is always needed).
--
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://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
