It also may be that you have to run tcpdump with sudo. Alternatively, one can provide the password to plink using the -pw option.Īgain, it may be that you have to provide the full path to tcpdump and/or wireshark. On Windows I have to omit the Wireshark option -k (immediately start capture) and manually start it from the Wireshark UI once SSH keyboard authentication is done. plink -ssh 'tcpdump -s 0 -w - 'port 8080'' | wireshark -i. Make sure you filter as much as possible on the remote side using tcpdump’s filters. On your host machine (from where we want to capture remote data), make a. Please note! Such a remote capture session can be pretty heavy on the network depending on the application. Install TCP dump on the remote (Server) computer, you need tcpdump installed. You may also need to run tcpdump with sudo which means you need to change the command to: ssh remote-host 'sudo /usr/sbin/tcpdump -s0 -w - 'port 8080'' | wireshark -k -i. Make sure tcpdump is on the path on your remote host or change the line to include the path a la: ssh remote-host '/usr/sbin/tcpdump -s0 -w - 'port 8080'' | wireshark -k -i. There are a few things that may make the line above not work in your case. The output is sent over SSH to the local host’s “stdout” where Wireshark is waiting on “stdin” for input. This will run tcpdump on host “remote-host” and capture full packages (-s0) on port 8080.

Linux ssh remote-host 'tcpdump -s0 -w - 'port 8080'' | wireshark -k -i. Run Wireshark on your desktop (Linux or Windows) and capture on the remote server. You want to use tcpdump in combination with Wireshark but on the server there is no X environment or no Wireshark installed?

Wireshark capture remote machine