Why tcpdump?

Tcpdump is the premier network analysis tool for information security professionals. Having a solid grasp of this über-powerful application is mandatory for anyone desiring a thorough understanding of TCP/IP. Many prefer to use higher level analysis tools such as Wireshark, but I believe this to usually be a mistake.

When using a tool that displays network traffic a more natural (raw) way the burden of analysis is placed directly on the human rather than the application. This approach cultivates continued and elevated understanding of the TCP/IP suite, and for this reason I strongly advocate using tcpdump instead of other tools whenever possible.


Below are a few options you can use when configuring tcpdump. They’re easy to forget and/or confuse with other types of filters, e.g., Wireshark, so hopefully this page can serve as a reference for you, as it does me. here are the main ones I like to keep in mind depending on what I’m looking at.


  • -i any : Listen on all interfaces just to see if you’re seeing any traffic.
  • -i eth0 : Listen on the eth0 interface.
  • -D : Show the list of available interfaces
  • -l : Line-readable output (for viewing as you save, or sending to other commands)
  • -A : Display output in ASCII.
  • -n : Don’t resolve hostnames.
  • -nn : Don’t resolve hostnames or port names.
  • -q : Be less verbose (more quiet) with your output.
  • -t : Give human-readable timestamp output.
  • -tttt : Give maximally human-readable timestamp output.
  • -X : Show the packet’s contents in both hex and ASCII.
  • -XX : Same as -X, but also shows the ethernet header.
  • -v, -vv, -vvv : Increase the amount of packet information you get back.
  • -c : Only get x number of packets and then stop.
  • -s : Define the snaplength (size) of the capture in bytes. Use -s0 to get everything, unless you are intentionally capturing less.
  • -S : Print absolute sequence numbers.
  • -e : Get the ethernet header as well.
  • -q : Show less protocol information.
  • -E : Decrypt IPSEC traffic by providing an encryption key.

The default snaplength as of tcpdump 4.0 has changed from 68 bytes to 96 bytes. While this will give you more of a packet to see, it still won’t get everything. Use -s 1514 or -s 0 to get full coverage.


In tcpdump, Expressions allow you to trim out various types of traffic and find exactly what you’re looking for. Mastering the expressions and learning to combine them creatively is what makes one truly powerful with tcpdump.

There are three main types of expression: type, dir, and proto.

  • Type options are: host, net, and port.
  • Direction lets you do src, dst, and combinations thereof.
  • Proto(col) lets you designate: tcp, udp, icmp, ah, and many more.


So, now that we’ve seen what our options are, let’s look at some real-world examples that we’re likely to see in our everyday work.

Basic Communication

Just see what’s going on, by looking at all interfaces.

# tcpdump -i any


Specific Interface

Basic view of what’s happening on a particular interface.

# tcpdump -i eth0


Raw Output View

Verbose output, with no resolution of hostnames or port numbers, absolute sequence numbers, and human-readable timestamps.

# tcpdump -ttttnnvvS


Find Traffic by IP

One of the most common queries, this will show you traffic from, whether it’s the source or the destination.

# tcpdump host

Seeing More of the Packet with Hex Output

Hex output is useful when you want to see the content of the packets in question, and it’s often best used when you’re isolating a few candidates for closer scrutiny.

# tcpdump -nnvXSs 0 -c1 icmp

Filtering by Source and Destination

It’s quite easy to isolate traffic based on either source or destination using src and dst.

# tcpdump src
# tcpdump dst

Finding Packets by Network

To find packets going to or from a particular network, use the net option. You can combine this with the src or dst options as well.

# tcpdump net

Show Traffic Related to a Specific Port

You can find specific port traffic by using the port option followed by the port number.

# tcpdump port 3389

# tcpdump src port 1025

Show Traffic of One Protocol

If you’re looking for one particular kind of traffic, you can use tcp, udp, icmp, and many others as well.

# tcpdump icmp

Show only IP6 Traffic

You can also find all IP6 traffic using the protocol option.

# tcpdump ip6

Find Traffic Using Port Ranges

You can also use a range of ports to find traffic.

# tcpdump portrange 21-23

Find Traffic Based on Packet Size

If you’re looking for packets of a particular size you can use these options. You can use less, greater, or their associated symbols that you would expect from mathematics.

# tcpdump less 32

# tcpdump greater 64

# tcpdump <= 128

Reading / Writing Captures to a File

It’s often useful to save packet captures into a file for analysis in the future. These files are known as PCAP (PEE-cap) files, and they can be processed by hundreds of different applications, including network analyzers, intrusion detection systems, and of course by tcpdump itself. Here we’re writing to a file called capture_file using the -w switch.

# tcpdump port 80 -w capture_file

You can read PCAP files by using the -r switch. Note that you can use all the regular commands within tcpdump while reading in a file; you’re only limited by the fact that you can’t capture and process what doesn’t exist in the file already.

# tcpdump -r capture_file


Now that we’ve seen what we can do with the basics through some examples, let’s look at some more advanced stuff.

It’s All About the Combinations

Being able to do these various things individually is powerful, but the real magic of tcpdump comes from the ability to combine options in creative ways in order to isolate exactly what you’re looking for. There are three ways to do combinations, and if you’ve studied programming at all they’ll be pretty familiar to you.

  1. AND
    and or &&
  2. OR
    or or ||
    not or !

Here are some examples of combined commands.

From specific IP and destined for a specific Port

Let’s find all traffic from going to any host on port 3389.

tcpdump -nnvvS src and dst port 3389

From One Network to Another

Let’s look for all traffic coming from 192.168.x.x and going to the 10.x or 172.16.x.x networks, and we’re showing hex output with no hostname resolution and one level of extra verbosity.

tcpdump -nvX src net and dst net or

Non ICMP Traffic Going to a Specific IP

This will show us all traffic going to that is not ICMP.

tcpdump dst and src net and not icmp

Traffic From a Host That Isn’t on a Specific Port

This will show us all traffic from a host that isn’t SSH traffic (assuming default port usage).

tcpdump -vv src mars and not dst port 22

As you can see, you can build queries to find just about anything you need. The key is to first figure out precisely what you’re looking for and then to build the syntax to isolate that specific type of traffic.

Keep in mind that when you’re building complex queries you might have to group your options using single quotes. Single quotes are used in order to tell tcpdump to ignore certain special characters—in this case below the “( )” brackets. This same technique can be used to group using other expressions such as host, port, net, etc.

# tcpdump 'src and (dst port 3389 or 22)'

Isolate TCP Flags

You can also use filters to isolate packets with specific TCP flags set.

Isolate TCP RST flags.

The filters below find these various packets because tcp[13] looks at offset 13 in the TCP header, the number represents the location within the byte, and the !=0 means that the flag in question is set to 1, i.e. it’s on.

# tcpdump 'tcp[13] & 4!=0'
# tcpdump 'tcp[tcpflags] == tcp-rst'

Isolate TCP SYN flags.

# tcpdump 'tcp[13] & 2!=0'
# tcpdump 'tcp[tcpflags] == tcp-syn'

Isolate packets that have both the SYN and ACK flags set.

# tcpdump 'tcp[13]=18'

Only the PSH, RST, SYN, and FIN flags are displayed in tcpdump‘s flag field output. URGs and ACKs are displayed, but they are shown elsewhere in the output rather than in the flags field.

Isolate TCP URG flags.

# tcpdump 'tcp[13] & 32!=0'
# tcpdump 'tcp[tcpflags] == tcp-urg'

Isolate TCP ACK flags.

# tcpdump 'tcp[13] & 16!=0'
# tcpdump 'tcp[tcpflags] == tcp-ack'

Isolate TCP PSH flags.

# tcpdump 'tcp[13] & 8!=0'
# tcpdump 'tcp[tcpflags] == tcp-psh'

Isolate TCP FIN flags.

# tcpdump 'tcp[13] & 1!=0'
# tcpdump 'tcp[tcpflags] == tcp-fin'

Everyday Recipe Examples

Because tcpdump can output content in ASCII, you can use it to search for cleartext content using other command-line tools like grep.

Finally, now that we the theory out of the way, here are a number of quick recipes you can use for catching various kinds of traffic.

Both SYN and RST Set

# tcpdump 'tcp[13] = 6'

Find HTTP User Agents

The -l switch lets you see the traffic as you’re capturing it, and helps when sending to commands like grep.

# tcpdump -vvAls0 | grep 'User-Agent:'

Cleartext GET Requests

# tcpdump -vvAls0 | grep 'GET'

Find HTTP Host Headers

# tcpdump -vvAls0 | grep 'Host:'

Find HTTP Cookies

# tcpdump -vvAls0 | grep 'Set-Cookie|Host:|Cookie:'

Find SSH Connections

This one works regardless of what port the connection comes in on, because it’s getting the banner response.

# tcpdump 'tcp[(tcp[12]>>2):4] = 0x5353482D'

Find DNS Traffic

# tcpdump -vvAs0 port 53

Find FTP Traffic

# tcpdump -vvAs0 port ftp or ftp-data

Find NTP Traffic

# tcpdump -vvAs0 port 123

Find Cleartext Passwords

# tcpdump port http or port ftp or port smtp or port imap or port pop3 or port telnet -lA | egrep -i -B5 'pass=|pwd=|log=|login=|user=|username=|pw=|passw=|passwd=|password=|pass:|user:|username:|password:|login:|pass |user '

Find Traffic With Evil Bit

There’s a bit in the IP header that never gets set by legitimate applications, which we call the “Evil Bit”. Here’s a fun filter to find packets where it’s been toggled.

# tcpdump 'ip[6] & 128 != 0'

Check out my other tutorials as well.


Here are the takeaways.

  1. tcpdump is a valuable tool for anyone looking to get into networking or information security.
  2. The raw way it interfaces with traffic, combined with the precision it offers in inspecting packets make it the best possible tool for learning TCP/IP.
  3. Protocol Analyzers like Wireshark are great, but if you want to truly master packet-fu, you must become one with tcpdump first.

Well, this primer should get you going strong, but the man page should always be handy for the most advanced and one-off usage scenarios. I truly hope this has been useful to you, and feel free to contact me if you have any questions.


  1. I’m currently (sort of) writing a book on tcpdump for No Starch Press.
  2. The leading image is from
  3. Some of the isolation filters borrowed from Sébastien Wains.
  4. Thanks to Peter at for inspiration on the new table of contents (simplified), and also for some additional higher-level protocol filters added in July 2018.
  5. An anagram for the TCP flags is: Unskilled Attackers Pester Real Security Folk.
0 (0)
Article Rating (No Votes)
Rate this article
There are no attachments for this article.
There are no comments for this article. Be the first to post a comment.
Full Name
Email Address
Security Code Security Code
Related Articles RSS Feed
How to Synchronize Directories Using Lsyncd in Linux
Viewed 10958 times since Wed, Oct 31, 2018
python learning
Viewed 1070 times since Wed, Dec 18, 2019
How To Find Largest Top 10 Files and Directories On Linux / UNIX / BSD find
Viewed 1759 times since Mon, Oct 29, 2018
Linux 20 Netstat Commands for Linux Network Management
Viewed 8576 times since Mon, Sep 21, 2020
Linux RedHat How To Create An RPM Package
Viewed 772 times since Sun, Jan 9, 2022
FIO (Flexible I/O) – a benchmark tool for any operating system
Viewed 18321 times since Wed, Jul 25, 2018
How To Use the Linux Auditing System on CentOS 7
Viewed 2759 times since Fri, Apr 5, 2019
RHCS6: Basic operations on clustered services
Viewed 1944 times since Sun, Jun 3, 2018
Linux get the list of FC HBA’s and WWPN
Viewed 1880 times since Tue, May 22, 2018
RHCS6: Quorum disk and heuristics
Viewed 3108 times since Sun, Jun 3, 2018