Stdin capture fails on Windows
Summary
On Win10 19042.630 with Wireshark Version 3.4.0 (v3.4.0-0-g9733f173),capture packet from remote ssh got nothing.
Steps to reproduce
(How one can reproduce the issue - this is very important)
I use the batch file below
@ECHO OFF
@SET PLINK_PATH="C:\Program Files\PuTTY\plink.exe"
@SET WIRESHARK_PATH="C:\Program Files\Wireshark\Wireshark.exe"
if not exist %PLINK_PATH% (
echo %PLINK_PATH% Not Found
if not exist %WIRESHARK_PATH% (
echo %WIRESHARK_PATH% Not Found
)
pause
)
@SET REMOTE_SERVER=192.168.2.1
@SET REMOTE_ACCOUNT=root
@SET REMOTE_PASSWORD=password
@SET REMOTE_INTERFACE=wlan0
%PLINK_PATH% -batch -ssh -pw %REMOTE_PASSWORD% %REMOTE_ACCOUNT%@%REMOTE_SERVER% "tcpdump -s0 -U -w - -i %REMOTE_INTERFACE% not port 22" | %WIRESHARK_PATH% -i - -k
What is the current bug behavior?
(What actually happens)
I can not see any packet with this script and wireshark version 3.4.0, and when I test with version 3.2.8,everything is ok.
What is the expected correct behavior?
(What you should see instead)
Wireshark version 3.4.0 should also capture packets.
Sample capture file
(If possible attach a sample capture file showing this issue)
Relevant logs and/or screenshots
(Paste any relevant logs)
Build information
(In Wireshark, select Help->About Wireshark from the main menu and use the button "Copy To Clipboard". Please paste the complete output here. Or from the command line, run `tshark -v` or `wireshark -v`)
Edited by Gerald Combs