7 hours 1 minute
Welcome to the end map lesson on I, P, T, C, P, U, T P and ICMP headers. This lesson is simply a brief overview of the most important TCP I be protocols you need to understand when composing and map scans. My main objective will be to help you to understand the difference between
their headers and what important features about age you need to grasp
if you walk away from it with an understanding of the TCP three way handshake, encapsulation source and destination addresses in ports, flags and ICMP types and codes. I've done my job.
I'll also provide you with some good reference videos in case you want to dive deeper.
Let's get started
in this lesson. We'll talk about two important concepts in T C P I p encapsulation in the TCP three way handshake.
Well, then go on to discuss TCP and examine its header.
Then we'll talk about UDP and it's header.
Next, we'll take a look at the I P header
and we'll finish up with the discussion on ICMP and it's header
in each of these slides. I'll provide you with some additional reference material and we'll try to focus on why and how this information is relevant to using n map.
The more you understand this stuff, the better you will be in constructing great and map scans.
Let's talk about two important concepts in normal. T c P I p. Communication.
Some of you may be asking why encapsulation and the TCP three way handshake are on the same slide.
Well, I have no good explanation, except for the fact that these two concepts are high level mechanisms that must be understood to conceptualize what is happening when n map scans are executed.
But the fact is, encapsulation and the TCP three way handshake are not necessarily related, other than they're both part of the traditional T. C V I. P. Stack.
And both fundamental
encapsulation is the process of adding headers and trailers to data.
Many people talk about it in terms of rappers, as in candy wrappers, not like Jay Z or Eminem.
The idea is that lower layers tack on headers and in some case, trailers toe higher layer packets in such a way that they're wrapped in them.
The picture in this slide shows the two most important OS I or T C B. I p model layers on the left as faras end map is concerned, the transport and the network layers
and on the right it shows which protocols exist in those layers as well as what data grams air called in each layer.
So what? The transport layer, therefore of the O S. I model a data. Graham is called a segment
and can either be TCP or UDP
at the network layer or layer three a data. Graham is called a packet.
I wanted to start with this because we're going to do further analysis of ways that end. Map uses each of these layers as it generates its scans by manipulating those headers.
The second concept here is the TCP three way handshake.
Some of you may be wondering why there is no UDP handshake on this slide.
The reason is that there is no such thing
as we discussed in the previous lesson. UDP does not provide connection oriented, take a reliable and to end communication.
It only provides best effort or connection. Lis communication between house.
The TCP three way handshake, on the other hand, is what makes connection oriented communication possible.
As the picture shows user A's computer initiates communication with server. Be with a sin flag set in the TCP segment
server. Be responds with both sin and act like flag set,
then user A's computer responds with an AK.
The connection is established and communication continues.
This is an important concept, and Matt, because N. Map and its users, such as you can generate scans that manipulate the TCP flags in different ways in order to solicit various responses so you can critically evaluate the results.
This capability is built into N map as a part of its packet Crafter called in Ping.
If you want to learn more about encapsulation and the TCP three way handshake, I've provided some links to some good videos.
Let's talk about two important concepts in normal T c B i B communication.
So on the right, I put a graphic that lays out the TSP header for you.
TCP is a transport layer layer for protocol that offers reliable connection or any communication and has passed down and encapsulated by I p
from n mouse perspective, the most important things you need to understand about the header is it sore sport,
the destination port and the TCBY flags
other things could be altered with and map through n paying. But these are the ones you'll spend most of your time working with an N map
in a regular and map scan. The sore sport is ephemeral, meaning you're scanning Station will automatically determine
the port. It opens for communication
and will be an upper level in non well known port. In other words, higher than 1024.
However, the destination port will either be defined by you and your scan statement or will be chosen by N map.
A regular and map scan, for instance, will scan 1000 popular ports, and a fast and map scan will scan 100 of the most popular.
A fast scan is built by using the Dash Capital F command line switch,
or you can literally specify exactly the ports you want to scan. I'll show you this later.
Another great feature of N map is that you don't have to build a full TCP connection a k a three way handshake when running a scan. In fact, by default and map generates a TCP syn scan against targets by setting the sin flag
not responding with a Cenac. This is because the response to sin scans are just as reliable as full connects scans, but are quieter and more polite
s capital s initiates a sin scan
and map. Dash s Capitol A initiates an axe can and and map
dash s capital t initiates a full connects Cannes.
Other important TCB flags to note are you for urgent
P for push bar for reset
and F for finish?
You can also initiate a so called Christmas Tree scan or Xmas scan
with a dash s uppercase X,
which sets all the TCBY flags
and in doing so, lights up the TCP segment like a Christmas tree.
Sometimes the responses to this type of scanning could be valuable, but they're definitely not quiet.
Some of the same things that applied to TCP also apply to you. T p
UDP itself is much simpler with less overhead than TCP. Though
the most important component of the UDP header is a destination port
with the ephemeral sore sport being supplied by your computer.
It's really important to be familiar with constructing UDP scans though an end map, because some really important service is use UDP for communication.
For example, the N S uses UDP Port 53 TP uses port 1 23
Net Bios uses port 1 37 and l'd APP uses 3 89
To initiate a UDP scan,
use an end map. Dash s Capitol. You followed by the poor to on a scan with the dash P switch. I'll show you some examples of this later.
The I P V four header is tacked onto the TCP or you d be header through the process of encapsulation
I p is connection. Listen, operates at layer three or the network layer.
You'll notice that I have
version circled in the graphic to the right.
The only reason why I've circled it is because I don't want you to get confused in i p v four communication. This value will always before. However, that doesn't mean that it changes to six If it is i p v six communication.
In fact, I P v six has an entirely different header.
Beyond that, you don't have to concern yourself with the version field.
The protocol field defines the protocol that is used in the creation of the packet
for the most part in and map. This will either be TCP or Protocol six
UDP or Protocol 17 or ICMP or Protocol one.
The source address will usually be your I P address, though this can be altered
and the destination address is the address of your target
Dash s Capital O allows you to determine which I p protocols. Air supported by Target Machine's
by default and map, will scan all 256 possible protocol values and provide you with the results.
As with the other slides in this module, I've provided you with a video on a deeper look into the I P header. Should you wish to learn more?
The Internet control message protocol is used all around the world by network analysts to determine if packets are routing successfully
if hosts are up and running. And for simple Leighton see analysis.
This is done using the ping or trace route command in your favorite operating system.
Hi. CMP is really a supporting protocol Enact similar to Layer four protocols but really exists in Layer three. Technically,
as you'll notice in the graphic, though, ICMP must be attached to I P because it has no address field it's better.
The two most important fields in the I C M P header are type and coat.
If you look at the graphic, you'll notice many familiar responses, with most of them being type 038 or 11
like destination host unreachable and T T L exceeded.
The biggest thing I want to point out is the fact that when you read about PING scans and end map, do not assume that this means ICMP is being used. In fact,
ICMP is really on Lee used as a helper utility. Charge it to traditional TCP and UDP scans in and map.
In fact, in order to initiate a nice CMP scan, you have to run and map
Dash S N Dash Capital, P Capital E
and map can be can use ICMP and novel ways, though. For instance, you can construct small ICMP packets that solicit responses from entire networks very quickly and then map.
This is much more effective than simply running a pink. A man wanted a time to every device on a network.
However, I think you'll see that using TCP and UDP scans are much more effective
and allowing and map to use ICMP as a helper is usually the best bet
in this lesson. We discussed too important concepts in T C V I P
encapsulation and the TCP three way handshake.
We then discuss TCP and examine it center.
Then we talked about UDP and it's header.
Next we took a look at the I P header
and we finished up with the discussion on ICMP and it's header.
I hope you found this information very helpful.
Thank you so much for working through it with me and I'll talk to you more in the next lesson.