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 (other OS'es unknown)
- interface is remote ("rpcap://...")
- dumpcap is trying to read the link type (-L)
For example, old stable 2.0.6 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)
>
\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).
Thanks,
Lukas Tribus
___________________________________________________________________________
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
