WEBVTT - This file was automatically generated by VIMEO

0
00:00:08.430 --> 00:00:12.650
Hi, and welcome back to Session two Network Fundamentals.

1
00:00:14.270 --> 00:00:18.530
In this video, we are going to see an introduction to Wild Sharkk,

2
00:00:19.380 --> 00:00:22.130
while sharkk is a network protocol analyzer.

3
00:00:22.710 --> 00:00:27.250
And we saw in the last video that network communications are defined by

4
00:00:27.650 --> 00:00:32.170
protocols to communicate between systems and a logical grouping of

5
00:00:32.490 --> 00:00:35.810
protocols that work together is called a protocol stack.

6
00:00:36.800 --> 00:00:37.940
In protocol analysis,

7
00:00:38.560 --> 00:00:43.220
we can describe structure and inter live data

8
00:00:43.680 --> 00:00:48.660
as it flows across a network to better understand what is happening on

9
00:00:48.660 --> 00:00:53.660
the network. Protocol analysis can help with understand network characters

10
00:00:54.790 --> 00:00:56.910
learning, who is on a network,

11
00:00:58.270 --> 00:01:02.750
determining who or what is utilizing available

12
00:01:03.020 --> 00:01:07.170
bandwidth, identify peak network usage times,

13
00:01:08.130 --> 00:01:09.730
identify malicious activity,

14
00:01:10.350 --> 00:01:14.210
and finding unsecured and broader applications.

15
00:01:14.720 --> 00:01:16.650
When we are using Product Analyzer,

16
00:01:16.790 --> 00:01:21.330
we can evaluate this tool with some properties of IT

17
00:01:21.980 --> 00:01:24.630
supported protocols, user friendliness,

18
00:01:25.260 --> 00:01:29.110
cost program support, source code access,

19
00:01:29.450 --> 00:01:31.990
and OSS support. At the high level,

20
00:01:32.470 --> 00:01:37.110
a protocol analyzer works by starting first in a collection

21
00:01:37.490 --> 00:01:42.270
that's mean it collects raw binary data in a network interface

22
00:01:42.850 --> 00:01:46.430
in promiscuous mode. Then these two,

23
00:01:47.010 --> 00:01:51.830
two works in convention in capturing binary data to

24
00:01:52.030 --> 00:01:53.990
a readable form. And finally,

25
00:01:54.500 --> 00:01:59.190
it's possible to analyze the protocols while Sharkk is present

26
00:01:59.330 --> 00:02:02.230
in many cybersecurity distribution like Call,

27
00:02:02.510 --> 00:02:06.230
Linux and Perot OS for a clean installation.

28
00:02:06.500 --> 00:02:11.310
Wireshark is available@wireshark.org and he's

29
00:02:11.310 --> 00:02:16.240
available for Microsoft Windows and Micro S

30
00:02:16.240 --> 00:02:19.260
two. So let's start here.

31
00:02:19.480 --> 00:02:23.660
I'm using a Calli Linux environment and, uh,

32
00:02:23.760 --> 00:02:27.380
the wire track is already solid in this environment, this machine,

33
00:02:28.000 --> 00:02:30.820
and is available in my start menu.

34
00:02:37.560 --> 00:02:41.900
And this is our initial interface windows in the interface of

35
00:02:41.970 --> 00:02:42.803
Wireshark.

36
00:02:45.150 --> 00:02:49.800
What we are seeing here is a list of all my network interfaces,

37
00:02:50.420 --> 00:02:54.720
uh, available for me. So we have a real, uh, interface here.

38
00:02:54.840 --> 00:02:58.840
A physical interface here is some visual interface available here.

39
00:02:59.920 --> 00:03:04.380
In this graph here is showing all the live packing package,

40
00:03:05.040 --> 00:03:07.020
uh, traffic, and by my,

41
00:03:07.410 --> 00:03:12.340
that are passing through my network interface here and may

42
00:03:12.340 --> 00:03:15.780
not double click is if I put the mouse here, uh,

43
00:03:15.880 --> 00:03:20.500
to tip will show my IP version four and version

44
00:03:20.920 --> 00:03:25.760
six. And for start a live capturing package,

45
00:03:26.880 --> 00:03:30.120
I will do a double click in my network interface here.

46
00:03:30.340 --> 00:03:35.120
So what we're seeing here is a live cap about all the protocols that

47
00:03:35.220 --> 00:03:37.800
are passing through this interface here.

48
00:03:41.810 --> 00:03:43.790
So we have some, some protocols here.

49
00:03:43.930 --> 00:03:48.750
If I open a web browser and start to, to assess some links

50
00:03:51.550 --> 00:03:52.383
like this,

51
00:03:56.070 --> 00:03:57.050
you're gonna see that

52
00:03:58.620 --> 00:04:02.970
more package are tracking about this network here.

53
00:04:05.470 --> 00:04:10.290
So this tool Bar Shark is responsible for this,

54
00:04:10.390 --> 00:04:15.090
for capturing all the package that are drafting in this in the, in my network,

55
00:04:15.270 --> 00:04:19.810
in my, uh, interface, network interface. Uh,

56
00:04:19.950 --> 00:04:22.370
we have here three three panels.

57
00:04:22.590 --> 00:04:25.690
So the first one is to show all the, the,

58
00:04:25.870 --> 00:04:30.300
the package with some information about the number of the package,

59
00:04:31.120 --> 00:04:34.380
uh, the time, the source, the source and the destination,

60
00:04:35.000 --> 00:04:36.180
the type of protocol.

61
00:04:37.820 --> 00:04:42.040
The length of this package is some additional information that, uh,

62
00:04:42.040 --> 00:04:45.720
wire shark is providing when get this package.

63
00:04:46.780 --> 00:04:51.640
The second panel here is about the details is, uh,

64
00:04:51.640 --> 00:04:56.520
packet details to show the layers for each

65
00:04:56.520 --> 00:05:00.240
package. We're gonna see in the next video about the network layer,

66
00:05:01.890 --> 00:05:06.150
and every package belongs from one

67
00:05:06.790 --> 00:05:08.870
specific uh, layer. Okay,

68
00:05:09.100 --> 00:05:14.070
this package passed through some layers and this is what we are

69
00:05:14.070 --> 00:05:17.290
seeing here this moment. So in the next video,

70
00:05:17.290 --> 00:05:20.730
we're gonna see more details about this, but for every different package,

71
00:05:22.840 --> 00:05:27.580
the number of layers passed from this package could

72
00:05:27.580 --> 00:05:29.700
change is the end of the, the, the package.

73
00:05:30.230 --> 00:05:33.500
Every package belongs from a specific layer.

74
00:05:34.980 --> 00:05:39.280
And the last panel here is about the package bites.

75
00:05:39.740 --> 00:05:44.680
That's mean is a, is a raw information in, uh, for odax more,

76
00:05:44.780 --> 00:05:45.640
uh, bytes.

77
00:05:46.260 --> 00:05:50.990
So it's useful when we are seeing some specific information

78
00:05:51.080 --> 00:05:52.670
about, about this package.

79
00:05:54.020 --> 00:05:57.440
The next information here is about the,

80
00:05:57.860 --> 00:06:01.600
the color that we are seeing here. So, uh,

81
00:06:02.020 --> 00:06:06.480
for every package we have a different context and we,

82
00:06:06.660 --> 00:06:10.960
we can change the color to help through our analysis.

83
00:06:11.460 --> 00:06:14.200
And this is a custom, uh, configuration.

84
00:06:14.940 --> 00:06:17.640
So we're going see here in view menu

85
00:06:19.250 --> 00:06:20.770
coloring rules,

86
00:06:21.430 --> 00:06:25.810
and here we have a list of some package and some filters.

87
00:06:26.230 --> 00:06:27.530
We are gonna see that, uh,

88
00:06:27.600 --> 00:06:32.410
wire shark is very powerful about the filters that we can use

89
00:06:32.790 --> 00:06:37.650
for our analysis package analysis. Uh, and this we have, uh, the full,

90
00:06:38.310 --> 00:06:41.290
uh, color rule already.

91
00:06:41.550 --> 00:06:46.140
So for every color here, we have specific rule.

92
00:06:46.640 --> 00:06:48.940
For example, for D C P and U D P,

93
00:06:48.940 --> 00:06:53.780
we have a different colors here for H T T P protocol for the

94
00:06:53.860 --> 00:06:58.580
Port 80, for example, we have a different color for our protocol.

95
00:06:59.200 --> 00:07:03.920
For example, this rule here for BET C P, we have, uh,

96
00:07:04.320 --> 00:07:09.040
a conditional filter and we have some elements here from, for example,

97
00:07:09.130 --> 00:07:14.080
flags analyze for T C P, uh, windows update, window update.

98
00:07:14.860 --> 00:07:15.260
Uh,

99
00:07:15.260 --> 00:07:20.120
so we is a filter is a logical condition that we can

100
00:07:20.220 --> 00:07:24.560
use. We can use a direct condition like this, or we can use, um,

101
00:07:24.960 --> 00:07:29.040
multiple logical conditions with some, uh, conditional, uh,

102
00:07:29.270 --> 00:07:32.280
options and, or, or for example.

103
00:07:33.890 --> 00:07:38.440
And this is a powerful option to create strong

104
00:07:38.510 --> 00:07:43.180
filters and help in our analysis. Next,

105
00:07:44.150 --> 00:07:46.130
for all this package collecting,

106
00:07:46.860 --> 00:07:49.560
we have our option to save and support

107
00:07:51.350 --> 00:07:53.840
this capture package. So we,

108
00:07:53.840 --> 00:07:57.840
we have to stop the live filtering capturing here,

109
00:07:58.500 --> 00:08:00.880
and we have some specific options to save.

110
00:08:02.050 --> 00:08:05.710
The format is PC pickup energy,

111
00:08:06.250 --> 00:08:11.030
but we have some other different options here to,

112
00:08:11.410 --> 00:08:14.390
to use in others, uh, tools.

113
00:08:15.050 --> 00:08:17.070
So is very, uh,

114
00:08:17.470 --> 00:08:22.430
powerful with this a kind of integration about all the

115
00:08:22.430 --> 00:08:24.310
information that we capture,

116
00:08:26.530 --> 00:08:31.190
or we can use our option to export for specific, uh, format.

117
00:08:31.650 --> 00:08:35.910
For example, we have this, uh, spark packet section here.

118
00:08:36.650 --> 00:08:41.350
So we can export this format for a JS O, for example,

119
00:08:42.010 --> 00:08:45.070
or a C V Ss or a plain text.

120
00:08:45.730 --> 00:08:48.550
So this is a part of your configuration and option here.

121
00:08:49.410 --> 00:08:54.230
Or we can export for a packet bite, for example. So this is very,

122
00:08:54.410 --> 00:08:59.400
uh, interesting to get more information to, can add the tail,

123
00:09:00.040 --> 00:09:04.400
a condition, for example, to use in another, uh, format or in another,

124
00:09:04.400 --> 00:09:07.680
another tool, finalize this package.

125
00:09:10.780 --> 00:09:15.710
Another very interesting option that we have here is about the collecting

126
00:09:15.710 --> 00:09:18.870
package. When the time of the reference,

127
00:09:19.050 --> 00:09:22.070
the reference time for each package, for example,

128
00:09:22.180 --> 00:09:26.790
here we begin in the time zero and every next

129
00:09:26.790 --> 00:09:31.710
package that Wireshark is getting has this

130
00:09:32.150 --> 00:09:34.470
reference time here for the first package here.

131
00:09:34.970 --> 00:09:39.940
So this the first one and the last one is the time, uh,

132
00:09:39.940 --> 00:09:41.660
passing from this first one.

133
00:09:42.320 --> 00:09:46.810
But we can change this in view time from a display

134
00:09:47.840 --> 00:09:52.500
we have here, uh, some options, so automatic from capital five, for example,

135
00:09:53.200 --> 00:09:57.930
and the second, since beginning of capture was the information that,

136
00:09:57.930 --> 00:10:02.410
that I said before. But we can change, for example, for the daytime, uh,

137
00:10:02.590 --> 00:10:06.970
for the universal daytime or the daytime present now.

138
00:10:07.550 --> 00:10:09.850
So we have some, uh, uh, configurations here,

139
00:10:10.200 --> 00:10:14.290
some options available here to help our analysis.

140
00:10:14.590 --> 00:10:19.290
So it depend of your option if for, uh, uh,

141
00:10:19.390 --> 00:10:22.810
get a different reference time. So the,

142
00:10:22.810 --> 00:10:27.700
the full option is very interesting because we are analyzing and

143
00:10:27.700 --> 00:10:32.260
we have like a timeline since the first package that start the,

144
00:10:32.400 --> 00:10:35.900
the first package. So this is the, the full, uh,

145
00:10:36.780 --> 00:10:38.220
configuration for time slice.

146
00:10:40.400 --> 00:10:43.460
The next very interesting option here available in,

147
00:10:43.460 --> 00:10:46.810
in Shart is about the futures.

148
00:10:47.270 --> 00:10:52.170
The future is a strong feature present in this tool

149
00:10:52.480 --> 00:10:55.610
depending on the, the type of filter that you use.

150
00:10:56.160 --> 00:10:59.050
This is help you a lot to get, uh,

151
00:10:59.160 --> 00:11:03.290
more formation about this analysis that you are doing in the,

152
00:11:03.310 --> 00:11:08.170
in the protocols. So in Wireshark we have two types of filters.

153
00:11:08.700 --> 00:11:11.730
First one is about a display filter.

154
00:11:12.310 --> 00:11:15.960
That's mean that in this bar here, uh, we,

155
00:11:16.100 --> 00:11:20.850
we can use a lot of different filters.

156
00:11:21.070 --> 00:11:25.890
We can type in filters here or we can use this button here

157
00:11:26.550 --> 00:11:31.090
and, uh, start to write, uh, more details filter.

158
00:11:31.790 --> 00:11:33.850
But a first uh,

159
00:11:34.030 --> 00:11:38.690
way to put a filter is type here directly in this, in this part. For example,

160
00:11:39.030 --> 00:11:42.130
we saw that we have a lot of package here,

161
00:11:44.700 --> 00:11:46.590
more than 7,000 package here.

162
00:11:47.550 --> 00:11:50.840
So this is confusing if, for example,

163
00:11:51.340 --> 00:11:55.120
if you want to get a specific package to avoid this.

164
00:11:55.940 --> 00:12:00.630
For example, we are looking for H T T P protocols here.

165
00:12:00.890 --> 00:12:05.030
We can filter here in H T T P, uh, the,

166
00:12:05.210 --> 00:12:07.750
the background color change. That's mean that, okay,

167
00:12:07.750 --> 00:12:12.500
this filter is we have package, we have,

168
00:12:12.560 --> 00:12:15.620
uh, a result for this filter. If I

169
00:12:17.600 --> 00:12:19.740
put enter example,

170
00:12:20.380 --> 00:12:25.180
I have a filter only for this kind of protocols. For example,

171
00:12:27.230 --> 00:12:28.290
if I have T C p,

172
00:12:29.050 --> 00:12:33.900
I have T C P only T C P for this filter here,

173
00:12:33.900 --> 00:12:37.740
for example, D C P and, and some protocol related for this.

174
00:12:38.320 --> 00:12:40.220
So this is a display filter.

175
00:12:41.730 --> 00:12:46.270
Other option here is when we start to

176
00:12:47.050 --> 00:12:50.640
create a new kind of capture, for example,

177
00:12:50.710 --> 00:12:52.440
here I have a capture filter.

178
00:12:52.900 --> 00:12:56.050
That's mean that our shark will,

179
00:12:56.120 --> 00:13:01.050
will capture only this kind of protocol.

180
00:13:01.630 --> 00:13:04.320
They're gonna use this filter as, uh, uh,

181
00:13:04.530 --> 00:13:08.880
input when we are doing a live capturing. So for example,

182
00:13:09.100 --> 00:13:12.200
if I want to capture only T C P protocols,

183
00:13:13.400 --> 00:13:18.200
I put this, this information here in capital filter box, I select

184
00:13:19.850 --> 00:13:23.160
my interface and start.

185
00:13:25.730 --> 00:13:28.310
So, and I will start a browser, for example,

186
00:13:29.890 --> 00:13:30.990
and start and look.

187
00:13:32.320 --> 00:13:36.580
The wire sh will capture only T C P filter TCP protocols.

188
00:13:37.640 --> 00:13:39.180
So this could be more

189
00:13:41.140 --> 00:13:45.450
interesting about kinds of, uh, resource.

190
00:13:46.910 --> 00:13:51.850
I'm not looking for every kind of package, for example, and collecting.

191
00:13:52.030 --> 00:13:54.410
I'm only looking for a specific package.

192
00:13:57.410 --> 00:14:01.430
Next, another very interesting, uh,

193
00:14:01.500 --> 00:14:02.870
options that we have here.

194
00:14:03.550 --> 00:14:08.110
Features that we have here in arch is about to see all the

195
00:14:08.350 --> 00:14:12.790
communication, all the conversation between the machines,

196
00:14:12.790 --> 00:14:15.110
the nodes, because in the network,

197
00:14:15.290 --> 00:14:20.030
we saw in the last videos that in the the network communication,

198
00:14:21.240 --> 00:14:26.200
we are talking about one machine or one node talking with another

199
00:14:26.390 --> 00:14:27.760
machine. Okay?

200
00:14:27.760 --> 00:14:32.360
So one device is connecting to one to another device

201
00:14:32.780 --> 00:14:37.680
or multiple devices to get some information to exchange some

202
00:14:37.680 --> 00:14:40.200
information. Information. So for this,

203
00:14:40.340 --> 00:14:43.800
we have some interesting options here to,

204
00:14:44.140 --> 00:14:47.610
to solve and to understand all this communication.

205
00:14:48.590 --> 00:14:51.920
So let's start a new life capturing here,

206
00:14:54.240 --> 00:14:56.820
the ethernet interface here and start.

207
00:15:00.700 --> 00:15:04.980
Okay, so we are capturing all the, the,

208
00:15:05.480 --> 00:15:09.060
the information of the package here, let me open a,

209
00:15:12.600 --> 00:15:17.250
a browser, okay? And we have a lot of package

210
00:15:19.300 --> 00:15:23.440
and, uh, let's start to see the, the endpoint here.

211
00:15:26.030 --> 00:15:27.870
So we have

212
00:15:29.470 --> 00:15:33.550
features to solve the endpoint. So that's mean that all the devices,

213
00:15:36.050 --> 00:15:40.390
our list of devices in this capturing and a conversation

214
00:15:42.210 --> 00:15:44.500
flow. So let's start with end points.

215
00:15:46.150 --> 00:15:51.090
So this interface here is showing about, uh,

216
00:15:51.200 --> 00:15:54.770
some package. For example, if I select the

217
00:15:56.760 --> 00:15:58.770
IP four, uh,

218
00:15:59.310 --> 00:16:04.090
the wire chart will give me a list of all the devices, all, all the,

219
00:16:04.090 --> 00:16:08.550
any points that was participating of the,

220
00:16:08.850 --> 00:16:13.590
the capturing that that we did. For example, here we have some ips,

221
00:16:13.930 --> 00:16:18.830
we have some local ips here about my network here.

222
00:16:19.530 --> 00:16:20.760
And for example,

223
00:16:21.420 --> 00:16:26.260
for this device that has this IP here,

224
00:16:27.280 --> 00:16:28.010
we,

225
00:16:28.010 --> 00:16:32.570
this device are exchanged 25 at is moment

226
00:16:32.570 --> 00:16:35.410
25 package. The number of bytes,

227
00:16:38.230 --> 00:16:43.000
the bytes that was exchanging and if wire shark

228
00:16:44.690 --> 00:16:49.600
could be able to translate some formation to get the counter ct.

229
00:16:49.620 --> 00:16:53.960
For example, if I change for D C P, it's the same. So

230
00:16:55.530 --> 00:17:00.500
this device here has exchange. Some package is some, uh,

231
00:17:00.540 --> 00:17:04.190
D C P package. Uh, use this port here for example,

232
00:17:05.110 --> 00:17:09.780
and X exchange package mean this bytes for example.

233
00:17:10.800 --> 00:17:14.820
And this is the same for another protocol called E D P, for example.

234
00:17:15.400 --> 00:17:16.980
So this is very powerful because

235
00:17:19.070 --> 00:17:23.410
in this view I'm able to get some informations

236
00:17:23.860 --> 00:17:25.090
about the end points

237
00:17:26.740 --> 00:17:29.400
not referring interesting information about conversation.

238
00:17:30.340 --> 00:17:35.140
That's mean that we have a conversation from one, uh,

239
00:17:35.140 --> 00:17:37.700
device to another device. For example,

240
00:17:39.990 --> 00:17:43.170
at this moment here, I have this one here,

241
00:17:43.480 --> 00:17:45.730
this device here address A, for example,

242
00:17:47.220 --> 00:17:51.480
this device had a communication with address B for this IP.

243
00:17:51.480 --> 00:17:56.080
Here they exchange the number of package, the,

244
00:17:56.700 --> 00:17:58.320
the size of bytes. For example,

245
00:18:00.790 --> 00:18:01.760
from this direction,

246
00:18:01.950 --> 00:18:05.960
package A to B was 54.

247
00:18:08.540 --> 00:18:12.390
This moment we don't have package from the inverse

248
00:18:13.620 --> 00:18:15.510
flow B to a, for example,

249
00:18:16.700 --> 00:18:19.020
the duration and the beat.

250
00:18:19.980 --> 00:18:21.960
So with this veer here,

251
00:18:22.060 --> 00:18:26.800
we are able to identify the conversations between the, the devices.

252
00:18:28.540 --> 00:18:31.320
And this is very interesting because imagine that the,

253
00:18:31.320 --> 00:18:36.250
your machine is sending information from unknown

254
00:18:36.550 --> 00:18:41.290
ip, for example. So in this view here, we gonna see this,

255
00:18:41.630 --> 00:18:46.210
we are gonna say, hey, we have some, uh, some conversation, some exchange,

256
00:18:46.630 --> 00:18:50.210
and we have a list of unknown ips, for example.

257
00:18:51.620 --> 00:18:55.040
So this interesting to start, uh,

258
00:18:55.180 --> 00:18:59.360
an investigation more further. For,

259
00:18:59.460 --> 00:19:00.840
for one case. For example,

260
00:19:02.890 --> 00:19:07.620
a great feature present in the wire shark is about following

261
00:19:07.620 --> 00:19:08.453
streams.

262
00:19:09.400 --> 00:19:14.300
So wire sharkk is able to resemble data from multiple package into a

263
00:19:14.540 --> 00:19:17.340
consolidate format called a packet transcript.

264
00:19:18.590 --> 00:19:23.380
So that's mean that between all the communications, uh,

265
00:19:23.440 --> 00:19:24.120
and all the,

266
00:19:24.120 --> 00:19:28.860
the package that wack is able to capture wack is,

267
00:19:30.120 --> 00:19:34.980
uh, able to get the flow for some package

268
00:19:35.840 --> 00:19:38.460
and reassemble to give you

269
00:19:40.190 --> 00:19:43.470
a logical flow, a logical, uh, stream

270
00:19:45.040 --> 00:19:48.910
for the communication, uh, between the devices,

271
00:19:49.570 --> 00:19:51.590
the networks. So for example,

272
00:19:52.480 --> 00:19:56.980
let's open a web browser here and let access,

273
00:19:57.960 --> 00:20:01.730
for example, this, this website here. Okay,

274
00:20:02.510 --> 00:20:06.940
so now let's put a filter for H T P and we have

275
00:20:07.850 --> 00:20:12.200
some filters here. And now we have this option for follow.

276
00:20:13.300 --> 00:20:17.600
So for this package is able to follow T C P

277
00:20:18.420 --> 00:20:22.500
or follow our H T T P for in HTT p here

278
00:20:23.430 --> 00:20:26.090
we have different colors. The first one

279
00:20:27.740 --> 00:20:31.020
was from my device here, and the,

280
00:20:31.480 --> 00:20:36.180
the blue here was the, the result. So for example,

281
00:20:36.780 --> 00:20:41.730
I have the start communication here. And look, there's, uh, a flow

282
00:20:44.090 --> 00:20:48.320
for, for example here we start and we have have the, the result here.

283
00:20:49.380 --> 00:20:51.320
So the red, uh, option here,

284
00:20:51.380 --> 00:20:56.180
the red result here is about the flow that start from my

285
00:20:56.180 --> 00:21:00.750
machine and the, the blue here was the result.

286
00:21:01.370 --> 00:21:03.670
So when this option here is able to get

287
00:21:05.880 --> 00:21:10.560
a flow and we can understand all the exchange of,

288
00:21:10.700 --> 00:21:14.480
of information. So let, let's put here another,

289
00:21:15.660 --> 00:21:17.640
not a filter. For T C P for example,

290
00:21:20.340 --> 00:21:23.740
I would choose a random, uh,

291
00:21:23.740 --> 00:21:28.450
package and put a follow for T C P and was the same.

292
00:21:29.270 --> 00:21:33.050
We have the workflow look for the, the,

293
00:21:33.190 --> 00:21:34.570
the link that we asked us.

294
00:21:36.190 --> 00:21:39.170
So this start from my device

295
00:21:40.820 --> 00:21:45.790
and this was the result that I received it from the,

296
00:21:45.820 --> 00:21:48.490
from the server. So

297
00:21:50.930 --> 00:21:54.660
this is interesting to, to get the, to understand the flow.

298
00:21:55.360 --> 00:21:59.720
So we have to choose some package to get

299
00:22:00.580 --> 00:22:03.700
the, to understand the,

300
00:22:05.290 --> 00:22:08.370
the information that we are receiving here.

301
00:22:10.780 --> 00:22:12.640
But with this information here is able,

302
00:22:13.340 --> 00:22:17.480
we are able to understand all this kind of

303
00:22:19.160 --> 00:22:21.640
exchange. So we have some, some package

304
00:22:24.320 --> 00:22:27.490
and we have, uh, this option to,

305
00:22:27.590 --> 00:22:29.690
for every package get the,

306
00:22:31.530 --> 00:22:34.390
the flow this package to another one.

307
00:22:34.970 --> 00:22:39.550
So to understand all the, the information we have to choose some, uh,

308
00:22:39.830 --> 00:22:42.390
specific package and, uh,

309
00:22:42.950 --> 00:22:47.070
assemble this information to get all the, all the information.

310
00:22:49.470 --> 00:22:50.303
P c p,

311
00:22:53.430 --> 00:22:56.410
we don't have nothing for DL to D L Ss,

312
00:22:57.720 --> 00:22:58.553
but that's it.

313
00:22:59.950 --> 00:23:04.850
In this video we saw an introduction to Wireshark and we

314
00:23:04.870 --> 00:23:08.340
saw you some features present in this tool.

315
00:23:09.270 --> 00:23:13.330
The next video, we'll take a look at the network OZY model.

316
00:23:14.460 --> 00:23:16.720
So I hope to see you, to see you there.
