You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
297 lines
6.9 KiB
297 lines
6.9 KiB
= Network analysis !
|
|
Apostolos rootApostolos@swarmlab.io
|
|
// Metadata:
|
|
:description: Intro and Install
|
|
:keywords: sec, tcpdump
|
|
:data-uri:
|
|
:toc: right
|
|
:toc-title: Πίνακας περιεχομένων
|
|
:toclevels: 4
|
|
:source-highlighter: highlight
|
|
:icons: font
|
|
:sectnums:
|
|
|
|
|
|
|
|
{empty} +
|
|
|
|
|
|
|
|
[[cheat-Docker]]
|
|
== Install docker (Home PC)
|
|
|
|
HowTo: See http://docs.swarmlab.io/SwarmLab-HowTos/labs/Howtos/docker/install.adoc.html[How to^]
|
|
|
|
|
|
|
|
.NOTE
|
|
[NOTE]
|
|
====
|
|
Assuming you're already logged in
|
|
====
|
|
|
|
|
|
**tcpdump** is a common packet analyzer that runs under the command line. It allows the user to display TCP/IP and other packets being transmitted or received over a network to which the computer is attached. Distributed under the BSD license, tcpdump is free software.
|
|
|
|
https://en.wikipedia.org/wiki/Tcpdump[More: wikipedia]
|
|
|
|
== Basic
|
|
|
|
=== Everything on an interface
|
|
|
|
Just see what’s going on, by looking at what’s hitting your interface.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump -i eth0
|
|
----
|
|
|
|
=== Find Traffic by IP
|
|
|
|
One of the most common queries, using host, you can see traffic that’s going to or from 1.1.1.1.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump host 1.1.1.1
|
|
----
|
|
|
|
|
|
=== Filtering by Source and/or Destination
|
|
|
|
If you only want to see traffic in one direction or the other, you can use src and dst.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump src 1.1.1.1
|
|
tcpdump dst 1.0.0.1
|
|
----
|
|
|
|
=== Finding Packets by Network
|
|
|
|
To find packets going to or from a particular network or subnet, use the net option.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump net 1.2.3.0/24
|
|
----
|
|
|
|
|
|
=== Show Traffic Related to a Specific Port
|
|
|
|
You can find specific port traffic by using the port option followed by the port number.
|
|
|
|
[source,bash]
|
|
----
|
|
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.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump icmp
|
|
----
|
|
|
|
=== Reading / Writing Captures to a File (pcap)
|
|
|
|
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.
|
|
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump port 80 -w capture_file
|
|
----
|
|
|
|
|
|
== Advanced
|
|
|
|
|
|
Now that we’ve seen what we can do with the basics through some examples, let’s look at some more advanced stuff.
|
|
|
|
.More options
|
|
[source,bash]
|
|
----
|
|
-X : Show the packet’s contents in both hex and ASCII.
|
|
-XX : Same as -X, but also shows the ethernet header.
|
|
-D : Show the list of available interfaces
|
|
-l : Line-readable output (for viewing as you save, or sending to other commands)
|
|
-q : Be less verbose (more quiet) with your output.
|
|
-t : Give human-readable timestamp output.
|
|
-tttt : Give maximally human-readable timestamp output.
|
|
-i eth0 : Listen on the eth0 interface.
|
|
-vv : Verbose output (more v’s gives more output).
|
|
-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.
|
|
----
|
|
|
|
|
|
[NOTE]
|
|
====
|
|
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.
|
|
|
|
- AND
|
|
|
|
and or &&
|
|
|
|
- OR
|
|
|
|
or or ||
|
|
|
|
- EXCEPT
|
|
|
|
not or !
|
|
====
|
|
|
|
|
|
=== From specific IP and destined for a specific Port
|
|
|
|
Let’s find all traffic from 10.5.2.3 going to any host on port 3389.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump -nnvvS src 10.5.2.3 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.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump -nvX src net 192.168.0.0/16 and dst net 10.0.0.0/8 or 172.16.0.0/16
|
|
----
|
|
|
|
|
|
=== 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.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump 'tcp[13] & 4!=0'
|
|
tcpdump 'tcp[tcpflags] == tcp-rst'
|
|
----
|
|
|
|
==== Isolate TCP SYN flags.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump 'tcp[13] & 2!=0'
|
|
tcpdump 'tcp[tcpflags] == tcp-syn'
|
|
----
|
|
|
|
==== Isolate packets that have both the SYN and ACK flags set.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump 'tcp[13]=18'
|
|
----
|
|
|
|
[NOTE]
|
|
====
|
|
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.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump 'tcp[13] & 32!=0'
|
|
tcpdump 'tcp[tcpflags] == tcp-urg'
|
|
----
|
|
|
|
==== Isolate TCP ACK flags.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump 'tcp[13] & 16!=0'
|
|
tcpdump 'tcp[tcpflags] == tcp-ack'
|
|
----
|
|
|
|
==== Isolate TCP PSH flags.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump 'tcp[13] & 8!=0'
|
|
tcpdump 'tcp[tcpflags] == tcp-psh'
|
|
----
|
|
|
|
==== Isolate TCP FIN flags.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump 'tcp[13] & 1!=0'
|
|
tcpdump 'tcp[tcpflags] == tcp-fin'
|
|
----
|
|
|
|
|
|
=== 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.
|
|
|
|
[source,bash]
|
|
----
|
|
tcpdump 'ip[6] & 128 != 0'
|
|
----
|
|
|
|
=== Summary
|
|
|
|
Here are the takeaways.
|
|
|
|
[NOTE]
|
|
====
|
|
- **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
|
|
====
|
|
|
|
|
|
[appendix]
|
|
== How to use tcpdump
|
|
|
|
|
|
This exercise 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.
|
|
|
|
https://danielmiessler.com/study/tcpdump[Origin]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
:hardbreaks:
|
|
|
|
{empty} +
|
|
{empty} +
|
|
{empty}
|
|
|
|
:!hardbreaks:
|
|
|
|
'''
|
|
|
|
.Reminder
|
|
[NOTE]
|
|
====
|
|
:hardbreaks:
|
|
Caminante, no hay camino,
|
|
se hace camino al andar.
|
|
|
|
Wanderer, there is no path,
|
|
the path is made by walking.
|
|
|
|
*Antonio Machado* Campos de Castilla
|
|
====
|
|
|