WEBVTT - This file was automatically generated by VIMEO

0
00:00:08.210 --> 00:00:12.230
Hi. And now come back to section two network fundamentals.

1
00:00:12.770 --> 00:00:13.603
In this video,

2
00:00:14.040 --> 00:00:19.030
we're going to see an introduction about the layer three network in layer

3
00:00:19.100 --> 00:00:22.570
four transport. Here in layer three,

4
00:00:22.620 --> 00:00:26.730
we're gonna see some protocols present in this layer.

5
00:00:28.220 --> 00:00:30.400
So we have some protocols like arp,

6
00:00:31.650 --> 00:00:34.510
IP version four and version six,

7
00:00:35.170 --> 00:00:40.030
and I C M P version, I version and version six arp.

8
00:00:40.530 --> 00:00:43.070
That's mean address resolution protocol.

9
00:00:43.220 --> 00:00:47.590
They are both logical and visco Addresses are used for communication on a

10
00:00:47.590 --> 00:00:48.423
network.

11
00:00:48.550 --> 00:00:53.400
Logical addresses allow for communication among multiple networks in,

12
00:00:54.150 --> 00:00:56.170
in indirectly connected devices.

13
00:00:57.300 --> 00:01:01.660
Visco addresses facilitate communication on a single network segment

14
00:01:02.120 --> 00:01:06.940
of devices that are directly connected to each other when a switch, for example,

15
00:01:07.890 --> 00:01:12.760
these two type of addressing must work together in order for communication to

16
00:01:12.850 --> 00:01:13.270
occur.

17
00:01:13.270 --> 00:01:18.080
When application want to initiate a communication is already have a remote

18
00:01:18.080 --> 00:01:19.400
host IP addresses.

19
00:01:19.910 --> 00:01:24.600
That means that the system should have all it needed to build

20
00:01:24.700 --> 00:01:28.960
the layer three through layer seven information of the packet.

21
00:01:29.460 --> 00:01:34.360
It wants to transmit the only pieces of information it needs at this point.

22
00:01:34.980 --> 00:01:39.970
It the layer two data link information containing the MEC addresses of

23
00:01:39.990 --> 00:01:41.010
the target host

24
00:01:42.600 --> 00:01:47.500
MEC addresses are needed because a switch interconnections devices

25
00:01:47.800 --> 00:01:52.780
on a network using a content address addressable memory can table

26
00:01:53.430 --> 00:01:58.340
which list the MEC addresses of all devices plugged in each

27
00:01:58.440 --> 00:02:02.640
of each ports. If the destination MAC is a no,

28
00:02:03.270 --> 00:02:07.280
then it must be resolved. The mechanism of resolution process,

29
00:02:07.580 --> 00:02:12.320
the D C P IP networking, which e P four, IP four version four,

30
00:02:13.190 --> 00:02:17.240
used to resolve IP addresses to make addresses.

31
00:02:17.390 --> 00:02:20.480
It's called ARP Address Resolution Protocol.

32
00:02:20.660 --> 00:02:23.440
The ARP resolution process use two packets,

33
00:02:23.940 --> 00:02:28.300
ARP request and ARP response IP

34
00:02:29.020 --> 00:02:33.420
Internet protocol. Today we have two versions, version four and version six.

35
00:02:34.080 --> 00:02:37.180
IP version four is the whole work,

36
00:02:37.390 --> 00:02:39.980
whole house of the communication process,

37
00:02:40.480 --> 00:02:44.940
and is ultimately responsible for carrying data between devices

38
00:02:45.860 --> 00:02:48.740
regardless of where the communication endpoints are located.

39
00:02:50.050 --> 00:02:54.340
IP version four are 22 beat for bytes.

40
00:02:54.960 --> 00:02:58.660
Assign numbers use it to uniquely identify devices.

41
00:02:58.690 --> 00:03:03.280
Connected to a network is converted to base 10 and

42
00:03:03.680 --> 00:03:08.560
represented as a number between zero and 255

43
00:03:09.180 --> 00:03:10.013
in the format.

44
00:03:10.520 --> 00:03:15.480
A B C D IP addresses consists of

45
00:03:15.480 --> 00:03:18.520
two parts, a network portion and a host portion.

46
00:03:19.220 --> 00:03:23.880
The network portion notifies the land local network the device is

47
00:03:23.880 --> 00:03:28.680
connected to, and the host portion notifies the device itself on that network.

48
00:03:28.980 --> 00:03:33.960
The network mask of our subnet mask determine which part of

49
00:03:34.060 --> 00:03:37.880
the IP address belongs to the network or the host.

50
00:03:37.910 --> 00:03:42.600
Part I C M P internet control message each in the,

51
00:03:42.600 --> 00:03:47.560
in the ion in this version six is the utility protocol of T C

52
00:03:47.600 --> 00:03:52.360
P A P responsible for providing information regarding the availability of the

53
00:03:52.360 --> 00:03:56.920
devices, services, or routers on the T C I P network.

54
00:03:57.300 --> 00:04:01.800
The common pinging is used to test for connectivity to a device.

55
00:04:02.540 --> 00:04:07.320
It utilize I C M P to archive achieve its small

56
00:04:07.600 --> 00:04:08.433
functionality.

57
00:04:08.660 --> 00:04:13.600
The pinging common sends one packet at time to a device and listens

58
00:04:14.220 --> 00:04:18.960
or reply to determine we where there is connectivity to the

59
00:04:18.960 --> 00:04:19.793
devices.

60
00:04:19.940 --> 00:04:24.680
So we have a ping echo pinging for request and an echo ping

61
00:04:24.740 --> 00:04:26.830
for response. Okay,

62
00:04:26.970 --> 00:04:30.870
so let's take a look and some protocols in the layer three.

63
00:04:31.450 --> 00:04:34.750
So I have here my Linux call Linux environment here,

64
00:04:35.290 --> 00:04:39.590
and I will start my version of Wireshark installed in this

65
00:04:39.740 --> 00:04:44.520
environment. So let's, we saw in the, uh,

66
00:04:44.620 --> 00:04:48.440
latest video, we have some interface, network interface protocol here.

67
00:04:49.180 --> 00:04:52.540
And I will start, uh, capturing life,

68
00:04:52.540 --> 00:04:57.260
capturing all the protocols in this my default networking

69
00:04:57.260 --> 00:05:01.600
interface. So here we have some protocols,

70
00:05:01.710 --> 00:05:04.560
some packets, some information, traffic

71
00:05:06.250 --> 00:05:10.080
in my network. So let's take a look.

72
00:05:10.940 --> 00:05:14.860
First of all in the IP packet structure.

73
00:05:16.370 --> 00:05:18.470
So in this interface here, in this panel,

74
00:05:18.630 --> 00:05:23.470
I have configured this panel here to show a graphic layer representation

75
00:05:23.730 --> 00:05:28.390
of protocols of packet structure. So here, for example,

76
00:05:28.570 --> 00:05:32.000
select the packet number two, it's uh,

77
00:05:33.920 --> 00:05:38.160
a protocol EEG MB version two, for example. But as we saw,

78
00:05:38.420 --> 00:05:40.440
we have some layers.

79
00:05:41.630 --> 00:05:45.370
We have a composition of some layers here. So for example,

80
00:05:45.370 --> 00:05:49.010
we have a composition for the, uh, layer 2, 3, 4,

81
00:05:49.830 --> 00:05:54.710
and we have for LEO two A frame A

82
00:05:54.850 --> 00:05:59.400
one, two, and three is a layer for IP protocol.

83
00:05:59.660 --> 00:06:02.840
So this IP protocol is version two. Here

84
00:06:04.610 --> 00:06:07.560
we have a graph per representation here.

85
00:06:08.880 --> 00:06:12.980
So internet protocol, we have a version, we have some information for flags,

86
00:06:12.980 --> 00:06:16.220
for example, we we're gonna see time to leave, for example.

87
00:06:16.770 --> 00:06:19.650
Time to leave is, uh, uh,

88
00:06:19.760 --> 00:06:23.230
information that represent the,

89
00:06:23.900 --> 00:06:28.390
this packet will traffic for, for some servers, some ho some nodes.

90
00:06:28.850 --> 00:06:33.390
And for each host, uh, is a mentation for this information here.

91
00:06:33.610 --> 00:06:34.750
That's mean. Uh, this,

92
00:06:34.780 --> 00:06:39.590
this is very interesting because the packet will try

93
00:06:39.590 --> 00:06:42.910
to arrive some destination, but if some,

94
00:06:43.100 --> 00:06:47.710
some proper internet and this packet will travel to some

95
00:06:48.020 --> 00:06:50.590
different machines. For example, uh,

96
00:06:50.620 --> 00:06:54.430
this packet has to drop 'cause it is not possible to have this,

97
00:06:54.500 --> 00:06:58.310
this protocol travel into the internet forever, for example.

98
00:06:58.690 --> 00:07:03.070
So time to leave is an example for, for this limitation,

99
00:07:03.970 --> 00:07:06.870
we have the protocol, the source address,

100
00:07:07.090 --> 00:07:11.850
and the source destination here is more simple

101
00:07:11.990 --> 00:07:16.410
to, to verify this. For example, we have the version, version four.

102
00:07:17.310 --> 00:07:19.840
We have some flags here.

103
00:07:21.640 --> 00:07:26.220
We have the time to leave, as I said before. We have the type of protocol

104
00:07:27.880 --> 00:07:32.770
and we have the source address in the destination address

105
00:07:32.770 --> 00:07:33.603
here.

106
00:07:33.710 --> 00:07:38.400
So this is the structure of the IP protocol.

107
00:07:38.400 --> 00:07:42.450
Version four. Lemme put a filter here.

108
00:07:43.220 --> 00:07:47.490
Lemme put a filter here for a protocol.

109
00:07:48.760 --> 00:07:53.370
So here we have a protocol address, resolution protocol,

110
00:07:54.030 --> 00:07:58.890
and we talked before that we have, uh, for a, we have two, uh,

111
00:07:59.710 --> 00:08:03.270
two process requests in response. So for example,

112
00:08:03.340 --> 00:08:08.260
here we have a request. Let me open the protocol.

113
00:08:09.500 --> 00:08:13.280
So we have the other type here, internet,

114
00:08:13.460 --> 00:08:14.520
we have the,

115
00:08:15.300 --> 00:08:20.030
the protocol type for each version of the IP in this layer,

116
00:08:20.090 --> 00:08:21.830
for example, so is IP four.

117
00:08:23.070 --> 00:08:27.570
We have the op code in this case a request. And we have the addresses,

118
00:08:27.870 --> 00:08:30.710
the address for Mac for the sender,

119
00:08:31.250 --> 00:08:34.870
and the target in the ip. So we have, uh,

120
00:08:36.140 --> 00:08:40.070
IP sender. So this is the address of my gateway.

121
00:08:40.810 --> 00:08:45.330
So I have a, a request for the sender and the target.

122
00:08:46.960 --> 00:08:49.710
Another request. We have a,

123
00:08:50.580 --> 00:08:53.660
a collection of requesters and we have a reply here.

124
00:08:54.040 --> 00:08:57.350
So let me check the here.

125
00:08:59.030 --> 00:08:59.863
Okay,

126
00:08:59.980 --> 00:09:04.640
so we have here first a request for the sender or this ip

127
00:09:04.820 --> 00:09:09.710
and the target was this IP here. And we have, uh,

128
00:09:10.240 --> 00:09:11.073
reply

129
00:09:12.410 --> 00:09:16.420
from this request for the sender here

130
00:09:17.320 --> 00:09:21.280
to this IP here. So here we have a cycle,

131
00:09:22.140 --> 00:09:26.120
the beginning of a request, and then the response.

132
00:09:27.400 --> 00:09:32.200
Okay? And at last, let's take a look of the pinging.

133
00:09:32.500 --> 00:09:37.360
The IIC m p protocol is use it for verify the

134
00:09:37.360 --> 00:09:42.240
connectivity of a network, for example. So lemme in this filter,

135
00:09:42.510 --> 00:09:47.410
I'll open a terminal section here and I will

136
00:09:47.610 --> 00:09:48.443
p

137
00:09:49.240 --> 00:09:53.360
our website just to produce some

138
00:09:54.080 --> 00:09:56.080
protocols for our analysis here.

139
00:09:56.970 --> 00:10:00.830
So let me to take a pinging for example, or

140
00:10:02.340 --> 00:10:06.050
one gov we have pinging here.

141
00:10:06.760 --> 00:10:11.620
This is a, uh, ip, uh, version, uh, six. So,

142
00:10:13.870 --> 00:10:17.770
and analyze here, okay, for here we have our,

143
00:10:19.430 --> 00:10:21.050
uh, I C M P version six.

144
00:10:21.840 --> 00:10:25.100
So here we have all the layers composing

145
00:10:26.710 --> 00:10:30.760
this information, this protocol here. So we have the IP version six.

146
00:10:31.830 --> 00:10:36.440
Here we have looked at a little different from a structure of IP six

147
00:10:36.720 --> 00:10:39.360
i IP four. So we have here IP four,

148
00:10:39.420 --> 00:10:43.120
we all the information here, the headers here,

149
00:10:44.490 --> 00:10:48.350
and I have now another packet, IP six.

150
00:10:48.530 --> 00:10:52.070
So we have some difference on flags

151
00:10:54.440 --> 00:10:59.260
to leave. T t L was changed for hope. Hope limit here. Okay?

152
00:10:59.280 --> 00:11:00.820
But the idea is the same.

153
00:11:02.040 --> 00:11:04.460
We have the source address and the destination address.

154
00:11:05.620 --> 00:11:10.470
This is a little different from IP four. Just look here,

155
00:11:10.530 --> 00:11:15.470
we have more information and we have a big, uh,

156
00:11:15.640 --> 00:11:17.470
range of addresses.

157
00:11:18.010 --> 00:11:22.990
So this is 128 beats different from

158
00:11:22.990 --> 00:11:26.440
22 beats for version four. Okay? Uh,

159
00:11:26.590 --> 00:11:31.570
this give me more a huge number of devices that I

160
00:11:31.570 --> 00:11:34.030
can use for IB six. Okay?

161
00:11:34.170 --> 00:11:37.550
So this give me more flexibility and, uh,

162
00:11:37.710 --> 00:11:42.530
a huge number of devices because this was a,

163
00:11:42.610 --> 00:11:44.490
a, a problem in i p four.

164
00:11:45.230 --> 00:11:50.090
We have a limited available numbers for device for addresses in i

165
00:11:50.130 --> 00:11:53.720
P four. And this was resolved in in IP six.

166
00:11:54.110 --> 00:11:58.920
Because of this, the number of devices is a huge in this version here.

167
00:11:59.710 --> 00:12:03.370
So we have our address stores and our destination address here.

168
00:12:04.740 --> 00:12:09.420
And we have M C P version six because the

169
00:12:09.530 --> 00:12:13.390
IP here was six. So we have, uh,

170
00:12:13.830 --> 00:12:18.640
structured and forces a request, a section

171
00:12:20.200 --> 00:12:24.090
for data here. Look for this is only to,

172
00:12:25.600 --> 00:12:28.100
to get the connectivity.

173
00:12:28.760 --> 00:12:33.440
So we have some request as we saw here.

174
00:12:34.600 --> 00:12:36.290
Hype is echoing. Request

175
00:12:39.290 --> 00:12:40.810
location request two.

176
00:12:43.430 --> 00:12:48.330
And the number of seconds is changed because we are exchanging information on

177
00:12:48.350 --> 00:12:51.530
to get the information go and down. Okay,

178
00:12:52.070 --> 00:12:56.200
let me start here again. The capturing, let

179
00:12:58.830 --> 00:13:00.260
start another pinging.

180
00:13:04.730 --> 00:13:07.130
Okay, this website here,

181
00:13:08.420 --> 00:13:13.320
we have IP version four. Okay. In the format,

182
00:13:13.460 --> 00:13:17.240
as I say A, B, D, and D.

183
00:13:18.400 --> 00:13:22.010
Okay, let put a filter

184
00:13:23.530 --> 00:13:27.770
for I M P. So here we have the,

185
00:13:27.770 --> 00:13:28.603
the IP four,

186
00:13:29.750 --> 00:13:33.590
and we have request and reply. Okay,

187
00:13:33.940 --> 00:13:37.670
because this is showing to me, to me the responsibility

188
00:13:39.180 --> 00:13:42.170
of this address. So we have some information here.

189
00:13:42.510 --> 00:13:47.210
We have a sequence for I M P, we have, uh, time to leave.

190
00:13:47.670 --> 00:13:51.570
That's mean. That is a good route because any,

191
00:13:51.710 --> 00:13:56.610
any packet was not the number here. D T L was not changed.

192
00:13:56.990 --> 00:14:01.890
That's mean that there is not any problem in the flow for this communication.

193
00:14:01.890 --> 00:14:02.640
If, for example,

194
00:14:02.640 --> 00:14:07.550
this packet go into a different server to arrive in the

195
00:14:07.550 --> 00:14:11.610
destination, the t t l here will be decremented, for example.

196
00:14:12.150 --> 00:14:16.730
The time of the response is very low. That's means is a,

197
00:14:16.730 --> 00:14:20.830
is a good connection. And we have a request and reply here.

198
00:14:21.980 --> 00:14:26.640
So let me close here and look for the request

199
00:14:27.070 --> 00:14:27.903
echo.

200
00:14:29.190 --> 00:14:32.360
We have this shorter here and the data.

201
00:14:33.630 --> 00:14:37.700
And for reply, we have some changes.

202
00:14:38.390 --> 00:14:43.210
First of all, reply the response time because this is a,

203
00:14:43.210 --> 00:14:44.810
is a reply type

204
00:14:47.130 --> 00:14:51.980
and the, the destination of the reply here,

205
00:14:52.120 --> 00:14:55.690
the, the, the address, the request,

206
00:14:56.870 --> 00:15:00.010
and the reply. Here in the layer four transport,

207
00:15:00.310 --> 00:15:01.890
we have two main protocols.

208
00:15:02.210 --> 00:15:06.450
T C P and U D P C P means transmission control protocol.

209
00:15:06.710 --> 00:15:10.050
And U D P means user datagram protocol.

210
00:15:10.930 --> 00:15:15.060
Part P is provide end-to-end reliability for the delivery of data.

211
00:15:15.900 --> 00:15:19.400
So it's able to handle this data sequencing, error,

212
00:15:20.120 --> 00:15:22.640
recovery and ensure data place delivery.

213
00:15:23.160 --> 00:15:25.400
R p is a connection oriented protocol.

214
00:15:25.820 --> 00:15:30.600
So that's mean that he's able to establish a formal connection before con

215
00:15:31.200 --> 00:15:35.000
transmitting data. He's able to track packet delivery.

216
00:15:36.310 --> 00:15:40.720
He's able to attempts to formally close communication channels.

217
00:15:41.200 --> 00:15:45.410
Maintain transmission is complete in many commonly used application layer

218
00:15:45.690 --> 00:15:49.810
protocols use to deliver the packet to the final destination.

219
00:15:49.990 --> 00:15:54.210
For this protocol, we have some ports. So we have, uh,

220
00:15:54.270 --> 00:15:59.090
six 5,525 ports available for use

221
00:15:59.090 --> 00:16:02.730
when communicating with T C P. And we have two groups,

222
00:16:03.570 --> 00:16:07.890
a system port group or external port or known port.

223
00:16:08.230 --> 00:16:08.790
In this group,

224
00:16:08.790 --> 00:16:13.490
we have port number one to port number 1020 23.

225
00:16:14.240 --> 00:16:18.140
And another group is a ephemeral port group. That's mean that we can use,

226
00:16:19.160 --> 00:16:22.940
uh, this port for our applications, our connection, for example,

227
00:16:23.280 --> 00:16:26.100
and start in the port a hundred,

228
00:16:26.420 --> 00:16:28.620
1,024 to six

229
00:16:28.690 --> 00:16:31.980
5,525 port.

230
00:16:32.560 --> 00:16:37.260
And for this communication, for example, http use a t p for,

231
00:16:37.320 --> 00:16:40.100
for connection. And we have some ways, okay,

232
00:16:40.800 --> 00:16:44.900
for open connection to close a connection

233
00:16:45.680 --> 00:16:50.090
and to close more abruptly a connection

234
00:16:50.760 --> 00:16:54.460
for open a connection, we have a T C P three-way handshake.

235
00:16:55.520 --> 00:17:00.020
So all the T C P based communication must begin with a handshake

236
00:17:00.290 --> 00:17:05.090
between the two hosts for the following purpose. For example,

237
00:17:05.090 --> 00:17:10.010
the first one is it allows the transmitting host to ensure that

238
00:17:10.010 --> 00:17:12.970
the recipient host is up and able to communicate.

239
00:17:14.080 --> 00:17:18.900
It lets the transmitting host check that the recipient is listening

240
00:17:19.120 --> 00:17:23.300
on the port that transmitting host is attempted to communicate on.

241
00:17:23.480 --> 00:17:28.100
So this ensure the communication between the two hosts and it allows

242
00:17:28.280 --> 00:17:32.860
the transmitting host to send its starting segment number

243
00:17:33.240 --> 00:17:37.740
to the recipient so that both hosts can keep this stream of packets

244
00:17:38.080 --> 00:17:41.260
in the proper segment because we have, uh,

245
00:17:41.260 --> 00:17:44.540
segment number in this, uh, streaming.

246
00:17:44.680 --> 00:17:49.680
And we have this representation here. So we have host here, we has o host A,

247
00:17:51.050 --> 00:17:52.010
communicate with host B,

248
00:17:52.590 --> 00:17:56.530
and first of all have to create packets for start connection.

249
00:17:56.940 --> 00:17:57.810
First of all,

250
00:17:58.120 --> 00:18:02.610
host A will send a packet with the flag sync to host B.

251
00:18:02.840 --> 00:18:06.810
Host B will respond, uh, when another package, uh,

252
00:18:06.810 --> 00:18:11.170
when the flag scene to host a. And finally,

253
00:18:11.360 --> 00:18:15.250
host A will send a packet with the flag X to host B.

254
00:18:15.510 --> 00:18:18.890
So this is how open connection start.

255
00:18:19.550 --> 00:18:23.420
We have a T C P tier down to close the connection.

256
00:18:23.480 --> 00:18:27.540
So it's used to gracefully and a connection between two devices

257
00:18:28.230 --> 00:18:31.580
After they have finished communicate all the communication.

258
00:18:32.210 --> 00:18:36.460
This process involves our package and is it utilize

259
00:18:37.080 --> 00:18:40.580
the fin flag to signify the end of connection.

260
00:18:41.280 --> 00:18:43.140
So in this representation here,

261
00:18:43.400 --> 00:18:48.380
we have a host A and host B host A has to end the

262
00:18:48.380 --> 00:18:53.100
connection. So host A using send a packet with a flag fin egg to host B,

263
00:18:53.490 --> 00:18:57.860
host B will res respond host A in two packets.

264
00:18:57.910 --> 00:19:00.060
First a packet with a flag egg,

265
00:19:00.720 --> 00:19:04.260
and then a packet with a flag fin egg. Finally,

266
00:19:04.450 --> 00:19:09.260
host A will send a package to flag win a flag A to host

267
00:19:09.500 --> 00:19:13.260
B. So the connection will be gracefully close.

268
00:19:13.600 --> 00:19:15.100
And we have the d p reset.

269
00:19:15.680 --> 00:19:19.940
That's mean that when we have to aim a Berkeley a connection,

270
00:19:20.480 --> 00:19:23.740
so host A will all host b uh,

271
00:19:23.800 --> 00:19:28.780
is depend of who will the host that will end the

272
00:19:28.780 --> 00:19:29.700
connection. Uh,

273
00:19:29.710 --> 00:19:34.580
we'll send a packet with the flag r s t to reset the

274
00:19:34.580 --> 00:19:39.040
connection. And we have we,

275
00:19:39.100 --> 00:19:43.690
the protocol u d p, that's mean user datagram protocol.

276
00:19:44.970 --> 00:19:48.670
Uh, and it's aimed to provide speedy transmission.

277
00:19:49.500 --> 00:19:54.310
It's aless protocol. That's mean that when host A and host B, we don't have,

278
00:19:54.650 --> 00:19:59.530
uh, the formality open connection and close connection, for example,

279
00:19:59.870 --> 00:20:01.690
in the same way as T C P.

280
00:20:02.310 --> 00:20:06.090
So don't not formally establish the eliminate connection. Uh,

281
00:20:06.090 --> 00:20:10.370
the protocol that reply on U D P typically have their own

282
00:20:11.030 --> 00:20:15.930
re reliability services or use certain features of I C

283
00:20:16.050 --> 00:20:16.883
M P, for example,

284
00:20:16.950 --> 00:20:21.930
to make the connection somehow more reli like D N s and

285
00:20:22.210 --> 00:20:23.043
D H C P.

286
00:20:23.630 --> 00:20:28.210
So this protocol use U D P as the transport protocol

287
00:20:28.590 --> 00:20:31.930
to have more, uh, speed for the, for the connection,

288
00:20:31.990 --> 00:20:36.730
but they implement some building features for reliability.

289
00:20:38.290 --> 00:20:42.590
And, uh, we're gonna see more details. But these both, uh, protocols.

290
00:20:43.400 --> 00:20:48.040
So now let's take a look in the D C P N D P protocols

291
00:20:48.340 --> 00:20:53.000
and in more detail, uh, in more detail. And let me open, uh,

292
00:20:53.020 --> 00:20:57.980
the Wireshark. So here is our,

293
00:20:58.080 --> 00:21:01.660
our shark, the list of inter network interfaces.

294
00:21:03.080 --> 00:21:06.300
And let me start the live capturing

295
00:21:07.770 --> 00:21:12.650
package. Okay? So we start to capture all the,

296
00:21:12.830 --> 00:21:16.130
the package traffic in my network, uh, between the, my,

297
00:21:16.130 --> 00:21:19.240
my laptop here and my router.

298
00:21:20.730 --> 00:21:22.400
Lemme open a web browser

299
00:21:24.440 --> 00:21:27.060
and I'll access the web, the Google website.

300
00:21:29.810 --> 00:21:33.750
Let stop the captain and let's analyze all the captors.

301
00:21:34.370 --> 00:21:38.190
So I have, I access the, the website, the Google website here.

302
00:21:39.670 --> 00:21:44.650
And let's take a look in the three-way handshake or T

303
00:21:44.730 --> 00:21:48.820
C P or here we have some of the package,

304
00:21:52.470 --> 00:21:54.530
the filter. T C P is more,

305
00:21:55.880 --> 00:22:00.120
is more interesting here. So

306
00:22:02.060 --> 00:22:06.450
here, here we have, uh, this IP here,

307
00:22:09.280 --> 00:22:12.290
this IP here, 1 5 7.

308
00:22:19.290 --> 00:22:22.610
Lemme choose a good example.

309
00:22:25.730 --> 00:22:27.620
Okay? These are good example here.

310
00:22:28.660 --> 00:22:32.340
So here we have my IP address here.

311
00:22:32.920 --> 00:22:37.580
And send us a syn for this, uh, destination here.

312
00:22:38.280 --> 00:22:40.460
So if we take a look,

313
00:22:41.700 --> 00:22:43.320
we have the IP six,

314
00:22:43.460 --> 00:22:48.040
we have all the package composed by passing through

315
00:22:48.260 --> 00:22:52.410
the layers, okay? That the, for the O S I model,

316
00:22:53.770 --> 00:22:57.390
we have the IP four in D C P. Here

317
00:22:59.270 --> 00:23:03.020
we have the, the femoral port that we talked before.

318
00:23:04.280 --> 00:23:07.470
Uh, destination port in the,

319
00:23:09.530 --> 00:23:13.320
the ip, the source in the destination, okay?

320
00:23:14.320 --> 00:23:18.290
Was at tcp. As we're taking, uh,

321
00:23:18.880 --> 00:23:22.490
observation here, we have the flag here for sync.

322
00:23:23.240 --> 00:23:27.940
We have a set of flags and this is the,

323
00:23:28.080 --> 00:23:32.610
the sink flag for open the communication.

324
00:23:34.080 --> 00:23:38.700
We have some optional, uh, plugs here too.

325
00:23:42.510 --> 00:23:43.410
And that's it. Okay,

326
00:23:43.670 --> 00:23:47.670
so we have the first is a sync for the first package here,

327
00:23:48.940 --> 00:23:53.010
the destination will respond, means sync act. Okay?

328
00:23:53.930 --> 00:23:55.590
And then the first,

329
00:23:56.820 --> 00:24:01.360
this device here that open the connection will respond,

330
00:24:01.360 --> 00:24:04.420
mean act. That's mean that the connection,

331
00:24:05.700 --> 00:24:10.520
the connection here is open. 'cause we have this, uh,

332
00:24:10.520 --> 00:24:14.760
this package, assemble of package here, sync syn,

333
00:24:15.080 --> 00:24:18.570
e and E. So the connection is done.

334
00:24:19.190 --> 00:24:23.480
That's mean that we can exchange data between this

335
00:24:24.800 --> 00:24:29.320
host here, ACT data. Okay?

336
00:24:29.860 --> 00:24:34.360
We have the, all the, the communication between these both, uh,

337
00:24:34.730 --> 00:24:37.400
hosts. Okay?

338
00:24:38.550 --> 00:24:41.420
We have some transmissions here.

339
00:24:42.640 --> 00:24:46.010
This filter is applied for all the life capturing captain.

340
00:24:46.230 --> 00:24:51.160
That's mean that this can have more package from other

341
00:24:51.590 --> 00:24:54.010
devices and hosts, okay?

342
00:24:54.190 --> 00:24:57.860
But you have to pay attention and the source destination here,

343
00:24:59.650 --> 00:25:03.150
for example, we have others example of the transmission.

344
00:25:04.900 --> 00:25:09.640
That's mean that the data is flowing to one host from or

345
00:25:09.640 --> 00:25:13.960
another in the act. That's mean that, okay, I receive this, uh, this data,

346
00:25:15.160 --> 00:25:18.640
you are allowed to go ahead. For example,

347
00:25:20.350 --> 00:25:22.690
we saw the open connection.

348
00:25:24.150 --> 00:25:28.610
This is our other open connection for other device o other

349
00:25:28.880 --> 00:25:32.360
host here. And here, here we have the,

350
00:25:33.750 --> 00:25:38.250
the formality, the package for close a connection. Okay?

351
00:25:38.250 --> 00:25:41.860
We have a finac, we have a,

352
00:25:41.980 --> 00:25:46.150
a act here we have another finac look,

353
00:25:46.860 --> 00:25:49.670
this IP here, send a finac the,

354
00:25:52.380 --> 00:25:53.880
the destination package,

355
00:25:54.920 --> 00:25:58.790
the version of the flow send a finac to, okay?

356
00:25:58.930 --> 00:26:03.770
So this is configuring and, uh,

357
00:26:04.060 --> 00:26:06.610
gracefully finish a connection.

358
00:26:07.270 --> 00:26:10.940
We have a end of connection here,

359
00:26:12.870 --> 00:26:15.520
okay? And for U D P,

360
00:26:17.490 --> 00:26:21.860
let put a filter here, DP or D N s.

361
00:26:23.090 --> 00:26:23.480
Okay,

362
00:26:23.480 --> 00:26:28.450
we saw that d s use the U D P in order

363
00:26:29.150 --> 00:26:31.410
the communications. So we have a D n ss.

364
00:26:32.370 --> 00:26:36.050
D n S is a package responsible

365
00:26:37.360 --> 00:26:38.860
to, uh, identify

366
00:26:40.440 --> 00:26:43.790
our destination to check where is,

367
00:26:44.370 --> 00:26:46.640
if I put address, for example,

368
00:26:46.960 --> 00:26:50.620
D N SS is a protocol to resolve this,

369
00:26:51.010 --> 00:26:55.380
this IP here. So for d n s,

370
00:26:55.380 --> 00:26:59.310
we have a lot of package here. And for example, here,

371
00:26:59.310 --> 00:27:04.140
we have here U D P user DATAGRAM protocol here,

372
00:27:04.730 --> 00:27:08.990
okay? Use it for,

373
00:27:09.210 --> 00:27:14.140
get more speed for the, the information for D N Ss.

374
00:27:15.140 --> 00:27:18.300
We have some information here. Okay?

375
00:27:19.140 --> 00:27:23.260
D n s is is a protocol that queries some

376
00:27:23.770 --> 00:27:28.200
curious to resolve package because the,

377
00:27:29.080 --> 00:27:30.740
the protocol user package, for example,

378
00:27:30.840 --> 00:27:35.180
to resolve the name he sent for a hope for, for a host. This host don't,

379
00:27:35.400 --> 00:27:39.380
if this host has to resolve the, the address,

380
00:27:40.300 --> 00:27:42.050
he'll give the, the result. If not,

381
00:27:42.150 --> 00:27:47.130
he will send another d n s request for another host and another host and another

382
00:27:47.160 --> 00:27:49.890
host. That's mean, that is a, like a, a loop.

383
00:27:51.320 --> 00:27:55.630
So see the number of curries? And for each queue we have,

384
00:27:55.890 --> 00:28:00.230
we have the re the, the answer. Uh, and we have

385
00:28:02.180 --> 00:28:04.720
the use of U D P. Here we have the structure.

386
00:28:04.750 --> 00:28:07.580
Here is a protocol

387
00:28:09.090 --> 00:28:13.060
different from D C P. So the header is very different.

388
00:28:13.160 --> 00:28:15.020
We have the source port, the smash port,

389
00:28:15.690 --> 00:28:20.180
some checks on applied for the D n s and the payload is, uh,

390
00:28:21.090 --> 00:28:22.710
is information here. Okay?

391
00:28:23.330 --> 00:28:26.720
In this video we saw some main protocols.

392
00:28:27.020 --> 00:28:31.800
Use it in the layers three and four of the OZ model.

393
00:28:32.880 --> 00:28:37.260
The next section, we'll take a look at net penetration test.

394
00:28:37.780 --> 00:28:38.660
I hope see you there.
