To explicitly specify the PATH, you may need to include the path portion in double quotes (e.g. In order for the system to find dumpcap, you will need to include it as part of the Windows PATH environment variable, or explicitly specify the path. It resides in the Wireshark root folder (e.g. To capture Wireshark data, you will need to use “dumpcap” which is a command line utility installed as part of Wireshark. Now I think, you can play with the command as per your need.How to use Wireshark (on Windows) to capture a driver or network issue that may only occur very infrequently, for example, to capture data on an issue which may occur only once a month. w mypcap.pcap will create that pcap file, which will be opened using wireshark. You can remove this to capture all packets. Port ftp or ssh is the filter, which will capture only ftp and ssh packets. Default is eth0, if you not use this option.

i eth0 is using to give Ethernet interface, which you to capture. 65535, after this capture file will not truncate. s 0 will set the capture byte to its maximum i.e. You can use following command to capture the dump in a file: tcpdump -s 0 port ftp or ssh -i eth0 -w mycap.pcap I am writing this post, so that you can create a pcap file effectively. When you create a pcap file using tcpdump it will truncate your capture file to shorten it and you may not able to understand that.

so many other options available, see tcpdump man page.

you can directly see the capture of a remote system in any other Linux system using wireshark, for more detail click “ Remote packet capture using WireShark and tcpdump”.you can create filter to capture only required packets like ftp or ssh etc.you can also create a pcap file (to see the capture in wireshark),.you can see the packet dump in your terminal,.When you have only command line terminal access of your system, this tool is very helpful to sniff network packets. Tcpdump is a command line network sniffer, used to capture network packets.

Run wireshark pcap