Tcpdump usage examples
October 1, 2014
In most cases you will need root permission to be able to
capture packets on an interface. Using tcpdump (with root) to capture
the packets and saving them to a file to analyze with Wireshark (using a
regular account) is recommended over using Wireshark with a root
account to capture packets on an "untrusted" interface. See the Wireshark security advisories for reasons why.
See the list of interfaces on which tcpdump can listen:
See the list of interfaces on which tcpdump can listen:
tcpdump -DListen on interface eth0:
tcpdump -i eth0Listen on any available interface (cannot be done in promiscuous mode. Requires Linux kernel 2.2 or greater):
tcpdump -i anyBe verbose while capturing packets:
tcpdump -vBe more verbose while capturing packets:
tcpdump -vvBe very verbose while capturing packets:
tcpdump -vvvBe verbose and print the data of each packet in both hex and ASCII, excluding the link level header:
tcpdump -v -XBe verbose and print the data of each packet in both hex and ASCII, also including the link level header:
tcpdump -v -XXBe less verbose (than the default) while capturing packets:
tcpdump -qLimit the capture to 100 packets:
tcpdump -c 100Record the packet capture to a file called capture.cap:
tcpdump -w capture.capRecord the packet capture to a file called capture.cap but display on-screen how many packets have been captured in real-time:
tcpdump -v -w capture.capDisplay the packets of a file called capture.cap:
tcpdump -r capture.capDisplay the packets using maximum detail of a file called capture.cap:
tcpdump -vvv -r capture.capDisplay IP addresses and port numbers instead of domain and service names when capturing packets (note: on some systems you need to specify -nn to display port numbers):
tcpdump -nCapture any packets where the destination host is 192.168.1.1. Display IP addresses and port numbers:
tcpdump -n dst host 192.168.1.1Capture any packets where the source host is 192.168.1.1. Display IP addresses and port numbers:
tcpdump -n src host 192.168.1.1Capture any packets where the source or destination host is 192.168.1.1. Display IP addresses and port numbers:
tcpdump -n host 192.168.1.1Capture any packets where the destination network is 192.168.1.0/24. Display IP addresses and port numbers:
tcpdump -n dst net 192.168.1.0/24Capture any packets where the source network is 192.168.1.0/24. Display IP addresses and port numbers:
tcpdump -n src net 192.168.1.0/24Capture any packets where the source or destination network is 192.168.1.0/24. Display IP addresses and port numbers:
tcpdump -n net 192.168.1.0/24Capture any packets where the destination port is 23. Display IP addresses and port numbers:
tcpdump -n dst port 23Capture any packets where the destination port is is between 1 and 1023 inclusive. Display IP addresses and port numbers:
tcpdump -n dst portrange 1-1023Capture only TCP packets where the destination port is is between 1 and 1023 inclusive. Display IP addresses and port numbers:
tcpdump -n tcp dst portrange 1-1023Capture only UDP packets where the destination port is is between 1 and 1023 inclusive. Display IP addresses and port numbers:
tcpdump -n udp dst portrange 1-1023Capture any packets with destination IP 192.168.1.1 and destination port 23. Display IP addresses and port numbers:
tcpdump -n "dst host 192.168.1.1 and dst port 23"Capture any packets with destination IP 192.168.1.1 and destination port 80 or 443. Display IP addresses and port numbers:
tcpdump -n "dst host 192.168.1.1 and (dst port 80 or dst port 443)"Capture any ICMP packets:
tcpdump -v icmpCapture any ARP packets:
tcpdump -v arpCapture either ICMP or ARP packets:
tcpdump -v "icmp or arp"Capture any packets that are broadcast or multicast:
tcpdump -n "broadcast or multicast"Capture 500 bytes of data for each packet rather than the default of 68 bytes:
tcpdump -s 500Capture all bytes of data within the packet:
tcpdump -s 0
No comments:
Post a Comment