is without question the premier network analysis tool because it provides both power and simplicity in one interface.
My other tutorials This tutorial will show you how to isolate traffic in various ways-from IP, to port, to protocol, to application-layer traffic-to make sure you find exactly what you need as quickly as possible.
tcpdump is the tool everyone should learn as their base for packet analysis.
Install tcpdump with apt install tcpdump (Ubuntu), or yum install tcpdump (Redhat/Centos)
Let’s start with a basic command that will get us HTTPS traffic:
278239097, win 28, options [nop,nop,TS val 939752277 ecr 1208058112], length 0 0x0000: 4500 0034 0014 0000 2e06 c005 4e8e d16e E..4........N..n 0x0020: 8010 001c d202 0000 0101 080a 3803 7b55 ............8.{U 0x0030: 4801 8100This showed some HTTPS traffic, with a hex display visible on the right portion of the output (alas, it’s encrypted). Just remember-when in doubt, run the command above with the port you’re interested in, and you should be on your way.
Examples
PacketWizard™ isn’t really trademarked, but it should be.
Now that you are able to get basic traffic, let’s step through numerous examples that you are likely to need during your job in networking, security, or as any type of PacketWizard™.
Just see what’s going on, by looking at what’s hitting your interface.
tcpdump -i eth0
One of the most common queries, using host, you can see traffic that’s going to or from 1.1.1.1.
12790+ A? chúng tôi 12790 1/0/0 A 172.217.15.78 (44)If you only want to see traffic in one direction or the other, you can use src and dst.
To find packets going to or from a particular network or subnet, use the net option.
You can combine this with the and options as well.
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.
You can find specific port traffic by using the port option followed by the port number.
If you’re looking for one particular kind of traffic, you can use tcp, udp, icmp, and many others as well.
You can also find all IP6 traffic using the protocol option.
You can also use a range of ports to find traffic.
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.
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.
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.
More options
Here are some additional ways to tweak how you call tcpdump.
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.
Use this combination to see verbose output, with no resolution of hostnames or port numbers, using absolute sequence numbers, and showing human-readable timestamps.
Here are some examples of combined commands.
Let’s find all traffic from 10.5.2.3 going to any host on port 3389.
Let’s look for all traffic coming from chúng tôi and going to the 10.x or chúng tôi networks, and we’re showing hex output with no hostname resolution and one level of extra verbosity.
This will show us all traffic going to 192.168.0.2 that is not ICMP.
This will show us all traffic from a host that isn’t SSH traffic (assuming default port usage).
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 10.0.2.4 and (dst port 3389 or 22)’
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.
Isolate TCP SYN flags.
Isolate packets that have both the SYN and ACK flags set.
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.
Isolate TCP ACK flags.
Isolate TCP PSH flags.
Isolate TCP FIN flags.
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.
The -l switch lets you see the traffic as you’re capturing it, and helps when sending to commands like grep.
This one works regardless of what port the connection comes in on, because it’s getting the banner response.
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.
Check out my other tutorials as well.
Summary
Here are the takeaways.
tcpdump is a valuable tool for anyone looking to get into networking or information security.
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.
Protocol Analyzers like Wireshark are great, but if you want to truly master packet-fu, you must become one with tcpdump first.
Notes
I’m currently (sort of) writing a book on tcpdump for No Starch Press.
The leading image is from SecurityWizardry.com.
Some of the isolation filters borrowed from Sébastien Wains.
Thanks to Peter at chúng tôi for inspiration on the new table of contents (simplified), and also for some additional higher-level protocol filters added in July 2018.