WEBVTT - This file was automatically generated by VIMEO

0
00:00:17.100 --> 00:00:20.700
Hello everyone in this lesson. I will tell you the IP fragmentation

1
00:00:20.700 --> 00:00:22.400
 and three assembly process.

2
00:00:24.100 --> 00:00:27.700
In order to understand the importance of the IP fragmentation

3
00:00:27.700 --> 00:00:31.300
 and TCP segmentation and MTU Concepts.

4
00:00:30.300 --> 00:00:33.400
 We will first talk about Network

5
00:00:33.400 --> 00:00:35.600
 traffic on an example of topology.

6
00:00:36.600 --> 00:00:39.900
And we will cover the factors that affect Network

7
00:00:39.900 --> 00:00:41.800
 performance and CP.

8
00:00:45.200 --> 00:00:48.700
Here, we have a client and a server talking

9
00:00:48.700 --> 00:00:51.800
 to each other over the internet and we

10
00:00:51.800 --> 00:00:54.400
 are thinking of this browser here as our

11
00:00:54.400 --> 00:00:57.800
 client and thinking of the web server this

12
00:00:57.800 --> 00:01:00.000
 web server as our server.

13
00:01:00.800 --> 00:01:04.000
Imagine that a user is typing a

14
00:01:03.200 --> 00:01:07.300
 website URL such as wireshark.org and

15
00:01:07.300 --> 00:01:09.000
 then clicking on the enter button.

16
00:01:09.900 --> 00:01:12.600
As soon as the user hit the enter button, the

17
00:01:12.600 --> 00:01:15.100
 browser sends a request package to

18
00:01:15.100 --> 00:01:16.100
 the web server.

19
00:01:16.600 --> 00:01:19.800
But before sending the user request here,

20
00:01:19.800 --> 00:01:21.000
 we have a process.

21
00:01:22.500 --> 00:01:26.100
A question, which they browser process the

22
00:01:25.100 --> 00:01:28.400
 user request this process starts

23
00:01:28.400 --> 00:01:31.200
 from the moment. The user clicks on the enter button

24
00:01:31.200 --> 00:01:35.000
 and throughout this process the browser spans

25
00:01:34.500 --> 00:01:37.800
 sometime to handle it the handle

26
00:01:37.800 --> 00:01:39.500
 the request process.

27
00:01:41.500 --> 00:01:44.900
We are calling it as a client time

28
00:01:44.900 --> 00:01:47.400
 in this illustration. We can

29
00:01:47.400 --> 00:01:50.300
 think of it as a client time which is

30
00:01:50.300 --> 00:01:54.400
 spanned for processing the request on the browser. And

31
00:01:53.400 --> 00:01:56.400
 this also may be able to affect

32
00:01:56.400 --> 00:02:00.700
 the network performance and responsibility experienced

33
00:01:59.700 --> 00:02:01.800
 by the user.

34
00:02:02.500 --> 00:02:04.200
So after the browser.

35
00:02:05.800 --> 00:02:08.400
Process the user request it's gonna send the

36
00:02:08.400 --> 00:02:09.800
 request to the server.

37
00:02:13.800 --> 00:02:16.700
At this point because the request package

38
00:02:16.700 --> 00:02:19.200
 has too much too much size to

39
00:02:19.200 --> 00:02:21.200
 fit in a single package.

40
00:02:21.900 --> 00:02:24.600
It may be divided to a number of packages

41
00:02:24.600 --> 00:02:27.300
 as you can see here and you can

42
00:02:27.300 --> 00:02:29.000
 think of this packages.

43
00:02:29.900 --> 00:02:32.100
as the request pdu 1

44
00:02:33.300 --> 00:02:36.900
that request pdu3 so if the

45
00:02:36.900 --> 00:02:39.300
 process that has happened so far is considered

46
00:02:39.300 --> 00:02:42.200
 through the OSI model. It's like that

47
00:02:42.200 --> 00:02:45.700
 when data is sent from an application to

48
00:02:45.700 --> 00:02:48.200
 the network this first pass to

49
00:02:48.200 --> 00:02:51.400
 the TCP layer Regional which breaks the data into

50
00:02:51.400 --> 00:02:55.400
 smaller chunks called segments each

51
00:02:54.400 --> 00:02:57.800
 segment contains a portion

52
00:02:57.800 --> 00:02:59.800
 a part of the application date.

53
00:03:00.700 --> 00:03:03.300
Long feet additional information such as

54
00:03:03.300 --> 00:03:06.800
 the source and destination port numbers the sequence

55
00:03:06.800 --> 00:03:09.100
 number and the acknowledgment number.

56
00:03:09.800 --> 00:03:12.300
So this segments are then passed to

57
00:03:12.300 --> 00:03:15.800
 the network layer where they are in capsulated

58
00:03:15.800 --> 00:03:18.600
 as packets. So at this

59
00:03:18.600 --> 00:03:21.300
 point the data is segmented by TCP.

60
00:03:22.600 --> 00:03:25.400
And sent to the network layer.

61
00:03:26.100 --> 00:03:30.300
And at the network layer, the segments are incapsulated by

62
00:03:30.300 --> 00:03:33.700
 IP protocols adding the IP headers.

63
00:03:33.700 --> 00:03:36.700
 We are calling each one of them as packets.

64
00:03:37.300 --> 00:03:40.200
We know already our traffics in

65
00:03:40.200 --> 00:03:43.600
 Wireshark. We have observed many times

66
00:03:43.600 --> 00:03:46.300
 in Wireshark the packets in

67
00:03:46.300 --> 00:03:49.600
 the packet this pane as you know, and then

68
00:03:49.600 --> 00:03:52.500
 these segmented pdus are sent to

69
00:03:52.500 --> 00:03:54.600
 the destination as X.

70
00:03:56.900 --> 00:03:59.500
Is like in here write at

71
00:03:59.500 --> 00:04:02.200
 this point when packets are sent over a network.

72
00:04:02.200 --> 00:04:05.500
 They may need to be broken into smaller units.

73
00:04:05.500 --> 00:04:08.800
 They may need to be broken into

74
00:04:08.800 --> 00:04:12.400
 a similar chunks called fragments

75
00:04:11.400 --> 00:04:14.900
 in order to Traverse through

76
00:04:14.900 --> 00:04:17.600
 different networks with different maximum transmission

77
00:04:17.600 --> 00:04:18.500
 unit sizes.

78
00:04:19.200 --> 00:04:22.600
With the different MTU sizes, each fragment

79
00:04:22.600 --> 00:04:25.100
 contains a portion of

80
00:04:25.100 --> 00:04:28.700
 the original packet along with additional information such

81
00:04:28.700 --> 00:04:32.100
 as source and destination IP addresses the

82
00:04:31.100 --> 00:04:35.000
 dtl values and the argument

83
00:04:34.600 --> 00:04:37.400
 offset values and if

84
00:04:37.400 --> 00:04:40.300
 the IP fragmentation happens while the

85
00:04:40.300 --> 00:04:44.000
 request package is sent it

86
00:04:43.400 --> 00:04:46.500
 causes delays in reassembling the

87
00:04:46.500 --> 00:04:49.600
 original packet because the original packet is

88
00:04:49.600 --> 00:04:53.500
 split into multiple smaller packets

89
00:04:52.500 --> 00:04:55.700
 and each fragment must

90
00:04:55.700 --> 00:04:58.100
 include its own either.

91
00:04:58.900 --> 00:05:01.500
So pet MTU Discovery is

92
00:05:01.500 --> 00:05:04.600
 used to determine pet MTO Discovery

93
00:05:04.600 --> 00:05:08.200
 is used to determine the smallest MTU

94
00:05:07.200 --> 00:05:10.300
 along the pad for a

95
00:05:10.300 --> 00:05:14.100
 destination host. It's used to avoid fragmentation

96
00:05:13.100 --> 00:05:16.800
 and to improve the efficiency of

97
00:05:16.800 --> 00:05:20.100
 data transfer. It's performed. Dynamically

98
00:05:19.100 --> 00:05:22.200
 the pet enter you

99
00:05:22.200 --> 00:05:25.700
 Discovery process is performed dynamically and

100
00:05:25.700 --> 00:05:29.200
 adapts to change in network conditions. So

101
00:05:28.200 --> 00:05:31.500
 we will talk about the pattern to Discovery

102
00:05:31.500 --> 00:05:34.900
 in more detail on the next lesson. It's generally recommended

103
00:05:34.900 --> 00:05:36.400
 to should know this.

104
00:05:37.100 --> 00:05:40.400
At this moment, it's generally recommended to avoid

105
00:05:40.400 --> 00:05:43.500
 fragmentation by using a Network that

106
00:05:43.500 --> 00:05:46.600
 has a large enough MTU or by using

107
00:05:46.600 --> 00:05:49.400
 a protocol that can segment the data

108
00:05:49.400 --> 00:05:51.700
 at a higher level such as TCP.

109
00:05:52.300 --> 00:05:55.700
So in here in our sample traffic,

110
00:05:55.700 --> 00:05:58.800
 we are thinking of the request it used

111
00:05:58.800 --> 00:06:00.300
 as the TCP segments.

112
00:06:01.300 --> 00:06:04.300
And we will also see that the packets are being

113
00:06:04.300 --> 00:06:08.400
 sent using TCP segmentation instead

114
00:06:07.400 --> 00:06:11.200
 of fragmentation in real example

115
00:06:10.200 --> 00:06:13.500
 traffic over Wireshark soon.

116
00:06:17.100 --> 00:06:20.400
So if the request packets come in segments as

117
00:06:20.400 --> 00:06:24.000
 different pdus it will be reassembled

118
00:06:23.500 --> 00:06:26.100
 on the server side as you

119
00:06:26.100 --> 00:06:27.100
 can see in here.

120
00:06:28.900 --> 00:06:29.200
and

121
00:06:30.400 --> 00:06:33.400
We can call the time which is spanned for

122
00:06:33.400 --> 00:06:36.900
 sending the request pdus as

123
00:06:36.900 --> 00:06:39.900
 in here to the server as request time.

124
00:06:39.900 --> 00:06:42.800
 If there is an IP fragmentation together

125
00:06:42.800 --> 00:06:45.600
 with segmentation process, we can

126
00:06:45.600 --> 00:06:49.000
 predict that the request time will increase

127
00:06:48.300 --> 00:06:49.600
 even more.

128
00:06:50.400 --> 00:06:54.700
Because with IP fragmentation the reassembling

129
00:06:53.700 --> 00:06:56.300
 process would have increased.

130
00:06:58.600 --> 00:07:02.700
So after the server received the request reassembling

131
00:07:01.700 --> 00:07:03.800
 the pdus.

132
00:07:04.600 --> 00:07:07.600
It may need to sometime in order to fetch the

133
00:07:07.600 --> 00:07:10.300
 required data that has been requested by the

134
00:07:10.300 --> 00:07:14.200
 client of from the moment. The request

135
00:07:13.200 --> 00:07:16.500
 packet is received on the

136
00:07:16.500 --> 00:07:19.800
 server side to the time the data is sent.

137
00:07:20.700 --> 00:07:23.100
We can call it service time.

138
00:07:23.900 --> 00:07:26.800
That is the time taken for patching.

139
00:07:26.800 --> 00:07:29.400
 The data is the service time.

140
00:07:29.900 --> 00:07:32.800
During this time the web server

141
00:07:32.800 --> 00:07:35.700
 may be talking to another server. For example a

142
00:07:35.700 --> 00:07:39.400
 DB server as you can see in here web

143
00:07:38.400 --> 00:07:41.200
 server maybe talking to

144
00:07:41.200 --> 00:07:44.600
 an external service during the service time.

145
00:07:45.400 --> 00:07:48.300
So keep in mind that and we are

146
00:07:48.300 --> 00:07:49.100
 moving on.

147
00:07:51.100 --> 00:07:55.500
Then at the end of this conversation of fetching

148
00:07:54.500 --> 00:07:56.000
 the data.

149
00:07:58.400 --> 00:08:01.700
The server receives the data and it starts

150
00:08:01.700 --> 00:08:03.700
 sending this data to the client.

151
00:08:04.500 --> 00:08:07.900
So it will most likely send the data as multiple

152
00:08:07.900 --> 00:08:10.300
 pdus as in here, which

153
00:08:10.300 --> 00:08:13.600
 are the components of the requested data.

154
00:08:17.200 --> 00:08:20.900
We can name the time which spanned for sending the

155
00:08:20.900 --> 00:08:23.100
 response as response time.

156
00:08:24.100 --> 00:08:27.900
And note that the response time is the time takes

157
00:08:27.900 --> 00:08:30.400
 to transfer the data from the web server to

158
00:08:30.400 --> 00:08:33.200
 the client to the browser.

159
00:08:33.800 --> 00:08:35.000
So and then

160
00:08:35.600 --> 00:08:39.200
we can give a name as a pdu

161
00:08:38.200 --> 00:08:42.300
 response time the entire period

162
00:08:41.300 --> 00:08:44.600
 starting with sanding the request

163
00:08:44.600 --> 00:08:47.600
 until the whole response receiving

164
00:08:47.600 --> 00:08:49.600
 by the client.

165
00:08:51.600 --> 00:08:54.000
And it may take a Time depends on

166
00:08:54.300 --> 00:08:57.300
 the browser for rendering onto the

167
00:08:57.300 --> 00:08:59.800
 page is ready to represent to the user.

168
00:09:02.700 --> 00:09:05.600
At the end the data can be seen or

169
00:09:05.600 --> 00:09:08.600
 displayed by the user on its browser.

170
00:09:10.800 --> 00:09:13.200
Well to sum up let's talk about the

171
00:09:13.200 --> 00:09:16.200
 turbo shooting base on slow networks looking

172
00:09:16.200 --> 00:09:19.800
 at the entire picture here now does

173
00:09:19.800 --> 00:09:22.300
 we can put the puzzle pieces together?

174
00:09:23.200 --> 00:09:26.200
And first of all in order to discover the

175
00:09:26.200 --> 00:09:29.800
 reason and a source of network latencies, you

176
00:09:29.800 --> 00:09:32.900
 need to capture the network traffic at each

177
00:09:32.900 --> 00:09:36.500
 point of the topology separately.

178
00:09:37.400 --> 00:09:40.200
But namely you must have the

179
00:09:40.200 --> 00:09:43.400
 traces from each point. It means

180
00:09:43.400 --> 00:09:46.500
 that you should plug in version to the

181
00:09:46.500 --> 00:09:49.500
 client and to the web server and

182
00:09:49.500 --> 00:09:52.900
 even to the database server when

183
00:09:52.900 --> 00:09:55.800
 it is necessary if you get praise

184
00:09:55.800 --> 00:09:57.300
 from only the client.

185
00:09:58.100 --> 00:10:01.600
You can't find the reason of the latency sourcing from

186
00:10:01.600 --> 00:10:04.200
 the server. Maybe you can see

187
00:10:04.200 --> 00:10:07.400
 only that the latency sourcing from the server.

188
00:10:07.400 --> 00:10:10.300
 However, if we have a trace from

189
00:10:10.300 --> 00:10:13.500
 the server we can discover whether the

190
00:10:13.500 --> 00:10:16.100
 latency is sourcing when it talks

191
00:10:16.100 --> 00:10:19.900
 to a database server or any external

192
00:10:19.900 --> 00:10:22.500
 service or if there may

193
00:10:22.500 --> 00:10:24.500
 be a part where problem.

194
00:10:25.200 --> 00:10:28.700
We can have an idea about it. But at first

195
00:10:28.700 --> 00:10:32.400
 glance if we have a high pdu response

196
00:10:31.400 --> 00:10:32.600
 time.

197
00:10:33.500 --> 00:10:35.300
Then there is some sort of issue.

198
00:10:36.200 --> 00:10:37.300
We can be sure about.

199
00:10:38.200 --> 00:10:40.900
In order to discover where the issue is.

200
00:10:41.800 --> 00:10:45.300
We should look at the time Parts as

201
00:10:44.300 --> 00:10:47.500
 client-time request time

202
00:10:47.500 --> 00:10:50.100
 and the response time.

203
00:10:50.900 --> 00:10:53.700
So if we have a high service

204
00:10:53.700 --> 00:10:56.300
 time, then we can say that the issue

205
00:10:56.300 --> 00:10:57.700
 is sourcing from the vector.

206
00:10:58.300 --> 00:11:00.500
And we should focus on the server side.

207
00:11:01.800 --> 00:11:04.600
In order to solve the trouble

208
00:11:04.600 --> 00:11:05.500
 on our Network.

209
00:11:06.300 --> 00:11:09.700
But if we have a high request time by

210
00:11:09.700 --> 00:11:13.100
 request sending a duration or high

211
00:11:12.100 --> 00:11:15.800
 response sending time, we

212
00:11:15.800 --> 00:11:18.400
 can say that the issue is in the

213
00:11:18.400 --> 00:11:21.800
 network namely intermediary Network

214
00:11:21.800 --> 00:11:24.800
 namely intermediary network

215
00:11:24.800 --> 00:11:27.900
 devices such as routers switches or

216
00:11:27.900 --> 00:11:30.400
 firewalls and even the cables.

217
00:11:31.200 --> 00:11:34.800
However, if the entire pdu response

218
00:11:34.800 --> 00:11:38.100
 time is small but experience Time

219
00:11:37.100 --> 00:11:40.400
 by user to get the data is large

220
00:11:40.400 --> 00:11:43.400
 then the problem is in the client

221
00:11:43.400 --> 00:11:43.500
 side.

222
00:11:44.900 --> 00:11:47.300
And that is in the browser itself.

223
00:11:47.300 --> 00:11:50.800
 Of course, maybe they browser is spending too

224
00:11:50.800 --> 00:11:53.400
 much time and should be to render the

225
00:11:53.400 --> 00:11:56.800
 page or display the data so that

226
00:11:56.800 --> 00:11:59.700
 may also cause to increase the response time

227
00:11:59.700 --> 00:12:01.200
 experienced by the user.

228
00:12:04.900 --> 00:12:07.900
Now, let's look at a similar traffic in

229
00:12:07.900 --> 00:12:08.500
 the version.

230
00:12:19.200 --> 00:12:22.500
in this sample Network traffic PK file we can

231
00:12:22.500 --> 00:12:25.800
 observe this firstly with the

232
00:12:25.800 --> 00:12:26.900
 packet 48

233
00:12:27.600 --> 00:12:30.800
I will look at this conversation in this

234
00:12:30.800 --> 00:12:31.800
 PK file.

235
00:12:33.200 --> 00:12:36.600
There's a request packet with the HTTP get

236
00:12:36.600 --> 00:12:36.900
 message.

237
00:12:37.900 --> 00:12:41.400
And after this request server is

238
00:12:41.400 --> 00:12:45.000
 sending the response as an

239
00:12:44.100 --> 00:12:47.600
 image file because it contains the

240
00:12:47.600 --> 00:12:51.000
 request contains an image file as

241
00:12:50.500 --> 00:12:51.600
 a request.

242
00:12:52.300 --> 00:12:56.000
And we will investigate this conversation in here.

243
00:12:56.800 --> 00:13:00.600
And with the packet 48 declined

244
00:12:59.600 --> 00:13:02.700
 is sending a request to

245
00:13:02.700 --> 00:13:06.500
 the web server to the HTTP server,

246
00:13:05.500 --> 00:13:09.200
 but not that here. The

247
00:13:08.200 --> 00:13:11.300
 request is sent as a single

248
00:13:11.300 --> 00:13:11.800
 pack.

249
00:13:13.600 --> 00:13:17.000
So it was sent without segmentation or

250
00:13:16.900 --> 00:13:19.300
 the fragmentation then the server

251
00:13:19.300 --> 00:13:23.400
 sends an egg message in here informed

252
00:13:22.400 --> 00:13:23.700
 that.

253
00:13:24.500 --> 00:13:27.400
It has received the request with this

254
00:13:27.400 --> 00:13:30.600
 act message. The web server says hey, I

255
00:13:30.600 --> 00:13:33.500
 have received your request. It's okay informed.

256
00:13:34.500 --> 00:13:37.200
Then after the request has been received by

257
00:13:37.200 --> 00:13:39.100
 the vector at this point.

258
00:13:41.100 --> 00:13:44.700
Web server may talk to the another server such

259
00:13:44.700 --> 00:13:48.000
 as a database server or an external

260
00:13:47.600 --> 00:13:50.100
 service for a while in order

261
00:13:50.100 --> 00:13:51.900
 to fetch the request data.

262
00:13:52.800 --> 00:13:55.200
and by the way as a feature

263
00:13:55.200 --> 00:13:56.700
 of Wireshark

264
00:13:57.800 --> 00:14:00.400
You can you can add a Delta

265
00:14:00.400 --> 00:14:00.600
 time.

266
00:14:01.200 --> 00:14:04.300
Adult time column to the packet list Pane

267
00:14:04.300 --> 00:14:07.400
 and the Delta time column is a

268
00:14:07.400 --> 00:14:10.600
 feature of Wireshark displays the time difference

269
00:14:10.600 --> 00:14:14.000
 between sequential packets.

270
00:14:14.800 --> 00:14:17.800
And we can observe the time

271
00:14:17.800 --> 00:14:19.500
 between The Pact.

272
00:14:20.700 --> 00:14:23.400
To sum up the Delta time column in

273
00:14:23.400 --> 00:14:26.300
 Wireshark displays the time difference

274
00:14:26.300 --> 00:14:29.700
 between the sequential packets in

275
00:14:29.700 --> 00:14:30.200
 a capture.

276
00:14:31.700 --> 00:14:34.400
And this will be useful to investigate the

277
00:14:34.400 --> 00:14:37.400
 traffic by observing the time which takes between

278
00:14:37.400 --> 00:14:40.800
 the packets. For example, if the Delta time value is

279
00:14:40.800 --> 00:14:44.900
 large between two sequential packet

280
00:14:43.900 --> 00:14:46.800
 as in here, maybe.

281
00:14:47.800 --> 00:14:51.300
They may have a large time between these

282
00:14:50.300 --> 00:14:53.800
 packets, but this is not so

283
00:14:53.800 --> 00:14:54.100
 much time.

284
00:14:55.400 --> 00:14:56.100
between the packets

285
00:14:56.600 --> 00:14:59.800
And if the Delta time value is large between two

286
00:14:59.800 --> 00:15:02.500
 special packets, it could indicate that

287
00:15:02.500 --> 00:15:06.000
 there is high latency or packet loss

288
00:15:05.100 --> 00:15:06.400
 on the network.

289
00:15:07.100 --> 00:15:09.800
It's worth noting that the Delta time column.

290
00:15:10.300 --> 00:15:13.800
Isn't displayed by default in Virtual. You

291
00:15:13.800 --> 00:15:16.900
 need to add it to the Wireshark columns and

292
00:15:16.900 --> 00:15:20.300
 it's useful for identifying and analyzing

293
00:15:19.300 --> 00:15:22.400
 Network performance issues such

294
00:15:22.400 --> 00:15:25.400
 as latency or packet loss.

295
00:15:26.800 --> 00:15:27.500
so here

296
00:15:28.200 --> 00:15:31.600
by examining by investigating the Delta

297
00:15:31.600 --> 00:15:34.800
 time periods between the request packet and the

298
00:15:34.800 --> 00:15:36.400
 response packet.

299
00:15:36.900 --> 00:15:40.400
The response packet is Packet 61

300
00:15:39.400 --> 00:15:42.300
 and you can

301
00:15:42.300 --> 00:15:44.300
 calculate the time.

302
00:15:45.300 --> 00:15:46.000
spending

303
00:15:46.900 --> 00:15:48.000
for the response

304
00:15:48.700 --> 00:15:51.800
and you can analyze the time

305
00:15:51.800 --> 00:15:54.500
 between the request packet and

306
00:15:54.500 --> 00:15:57.600
 the response packet using these values

307
00:15:57.600 --> 00:15:59.000
 these Delta values.

308
00:16:01.600 --> 00:16:04.400
By investigating the Delta time. I want

309
00:16:04.400 --> 00:16:07.700
 emphasize that by examining the Delta

310
00:16:07.700 --> 00:16:10.400
 time periods between the request packet and

311
00:16:10.400 --> 00:16:11.800
 response packet.

312
00:16:12.300 --> 00:16:15.300
We can find out how much time must spend

313
00:16:15.300 --> 00:16:17.000
 to bring the necessary data.

314
00:16:17.400 --> 00:16:20.900
And as you remember we named this period

315
00:16:20.900 --> 00:16:22.700
 as service time.

316
00:16:23.300 --> 00:16:26.900
After the required data has been obtained

317
00:16:26.900 --> 00:16:29.700
 or prepared at this

318
00:16:29.700 --> 00:16:29.700
 point.

319
00:16:30.800 --> 00:16:34.000
The server begins to send the data as

320
00:16:33.800 --> 00:16:36.900
 response with the packet if

321
00:16:36.900 --> 00:16:37.700
 the two.

322
00:16:39.900 --> 00:16:42.600
And when we see some pdus which

323
00:16:42.600 --> 00:16:45.600
 are components or portions of

324
00:16:45.600 --> 00:16:48.500
 the image file requested by

325
00:16:48.500 --> 00:16:49.800
 the client.

326
00:16:50.500 --> 00:16:53.500
and so in order to see this process in

327
00:16:53.500 --> 00:16:56.500
 our traffic, let's look at the packet 502

328
00:16:58.200 --> 00:17:00.600
I will expand the detail.

329
00:17:01.700 --> 00:17:04.300
associated with the TCP protocol

330
00:17:04.300 --> 00:17:05.400
 as in here

331
00:17:08.100 --> 00:17:09.500
Let me resize that.

332
00:17:14.900 --> 00:17:17.700
Combine the packet 52 it

333
00:17:17.700 --> 00:17:20.900
 starts to send the response packets the

334
00:17:20.900 --> 00:17:24.200
 server starts to send the response packets

335
00:17:23.200 --> 00:17:26.800
 and these packets are being sent with

336
00:17:26.800 --> 00:17:29.800
 only making TC segmentation.

337
00:17:29.800 --> 00:17:33.100
 There is no IP fragmentation and

338
00:17:32.100 --> 00:17:36.100
 we can see the TCP protocol

339
00:17:35.100 --> 00:17:38.700
 as the packet protocol in

340
00:17:38.700 --> 00:17:42.200
 here because of that I'm expanding.

341
00:17:43.200 --> 00:17:45.600
the IP field first a

342
00:17:46.200 --> 00:17:50.000
and as you can see in here at some

343
00:17:49.300 --> 00:17:52.400
 Flex value, we have some Flex

344
00:17:52.400 --> 00:17:52.700
 value.

345
00:17:53.500 --> 00:17:56.300
and when we look at the flag values

346
00:17:57.300 --> 00:18:01.300
we can see the don't fragment the

347
00:18:00.300 --> 00:18:04.700
 deity value is set so

348
00:18:03.700 --> 00:18:06.200
 don't fragment bit

349
00:18:06.200 --> 00:18:09.900
 is set it is set to 1 this means

350
00:18:09.900 --> 00:18:13.400
 don't use IP fragmentation sending

351
00:18:12.400 --> 00:18:14.300
 this packet.

352
00:18:14.700 --> 00:18:17.500
In most of the real Network traffic we see

353
00:18:17.500 --> 00:18:21.200
 that the data is divided into ideal sizes in

354
00:18:20.200 --> 00:18:23.400
 the TCP segmentation stage to avoid

355
00:18:23.400 --> 00:18:25.900
 IP fragmentation in this way.

356
00:18:26.500 --> 00:18:30.300
And you will see this setting in the other response

357
00:18:29.300 --> 00:18:31.200
 packets as well.

358
00:18:31.900 --> 00:18:34.700
When you look at the other response packets,

359
00:18:34.700 --> 00:18:36.900
 for example the next packet.

360
00:18:38.400 --> 00:18:41.300
You can see the don't fragment pit

361
00:18:41.300 --> 00:18:41.800
 is set.

362
00:18:42.400 --> 00:18:44.200
as well and the

363
00:18:45.100 --> 00:18:46.700
next packet

364
00:18:47.300 --> 00:18:48.200
next video

365
00:18:49.500 --> 00:18:52.300
also is set to the

366
00:18:52.300 --> 00:18:53.300
 one.

367
00:18:54.400 --> 00:18:57.200
And we can see the same in the

368
00:18:57.200 --> 00:19:00.300
 other packets in the other videos, but now

369
00:19:00.300 --> 00:19:03.900
 turn back to the first edu associated with

370
00:19:03.900 --> 00:19:05.800
 the requested data.

371
00:19:07.700 --> 00:19:10.700
And you will see this setting all the

372
00:19:10.700 --> 00:19:13.800
 other response packets as well if there would

373
00:19:13.800 --> 00:19:16.000
 be a IP fragmentation.

374
00:19:17.300 --> 00:19:21.500
You would have seen that the bits of the more fragments and

375
00:19:20.500 --> 00:19:24.000
 fragment offset parameter

376
00:19:23.600 --> 00:19:26.500
 values change. So there

377
00:19:26.500 --> 00:19:29.800
 is only TCP segmentation sanding response

378
00:19:29.800 --> 00:19:32.300
 to the client furthermore when you

379
00:19:32.300 --> 00:19:33.500
 look at the TCP field.

380
00:19:34.800 --> 00:19:36.100
Let me show you.

381
00:19:38.600 --> 00:19:40.100
And scrolling down.

382
00:19:41.100 --> 00:19:44.700
You can see another expression in the TCP field.

383
00:19:44.700 --> 00:19:48.200
 You can see another expression representing that

384
00:19:47.200 --> 00:19:50.800
 this video is the part of a packet

385
00:19:50.800 --> 00:19:53.700
 and it says with this expiration

386
00:19:53.700 --> 00:19:56.700
 a this packet this pdu or

387
00:19:56.700 --> 00:19:59.400
 this pdu is resembled in

388
00:19:59.400 --> 00:20:01.300
 playing 61.

389
00:20:02.400 --> 00:20:05.400
So this video is reassembled in

390
00:20:05.400 --> 00:20:07.400
 the packet 61.

391
00:20:08.700 --> 00:20:11.500
Okay, you can look at the packet.

392
00:20:12.100 --> 00:20:15.700
Because the pdus are reassembled in

393
00:20:15.700 --> 00:20:19.000
 the packet 61 we can

394
00:20:18.300 --> 00:20:21.100
 understand that this packet.

395
00:20:22.200 --> 00:20:25.600
Is our real original data packet?

396
00:20:26.100 --> 00:20:30.300
And it contains some reassembled pdus.

397
00:20:31.300 --> 00:20:32.200
within itself

398
00:20:32.900 --> 00:20:33.200
and

399
00:20:34.300 --> 00:20:37.200
you can look at the packet 61 in order to

400
00:20:37.200 --> 00:20:40.500
 see the reassembled version as a packet.

401
00:20:41.200 --> 00:20:45.100
So furthermore when we click on packet

402
00:20:44.100 --> 00:20:46.400
 60 one.

403
00:20:47.500 --> 00:20:50.800
As an advantage of using partial we

404
00:20:50.800 --> 00:20:53.700
 can see the components of this.

405
00:20:55.200 --> 00:20:58.600
the reassembled components in here

406
00:21:02.400 --> 00:21:05.500
and you can also see the components of

407
00:21:05.500 --> 00:21:07.600
 this reassembled packet.

408
00:21:08.700 --> 00:21:11.800
In the packet list pane as small gray

409
00:21:11.800 --> 00:21:14.900
 points, you can see the components each

410
00:21:14.900 --> 00:21:17.500
 component of this reassembled packet.

411
00:21:17.500 --> 00:21:21.200
 When you click on this packet, you

412
00:21:20.200 --> 00:21:24.700
 can see the reassembled packets

413
00:21:23.700 --> 00:21:26.700
 one by one as

414
00:21:26.700 --> 00:21:29.600
 small gray points as you

415
00:21:29.600 --> 00:21:29.700
 can see.

416
00:21:31.100 --> 00:21:34.700
The reassembled packets the components

417
00:21:34.700 --> 00:21:36.700
 of the actual data.

418
00:21:37.900 --> 00:21:41.000
Are being represented with degree

419
00:21:40.900 --> 00:21:43.100
 points as you can see

420
00:21:43.100 --> 00:21:43.700
 in here.

421
00:21:45.200 --> 00:21:46.500
by the Wireshark

422
00:21:47.100 --> 00:21:49.700
and as a Wireshark feature

423
00:21:50.700 --> 00:21:50.900
so

424
00:21:52.800 --> 00:21:55.500
and this great points are being

425
00:21:55.500 --> 00:21:58.400
 used to point out that

426
00:21:58.400 --> 00:22:01.800
 the packet 52 and the 53

427
00:22:01.800 --> 00:22:04.900
 and the if the six and

428
00:22:04.900 --> 00:22:08.700
 58 and 59 are

429
00:22:08.700 --> 00:22:12.000
 the components of the packet 61

430
00:22:11.600 --> 00:22:13.300
 we can understand that.

431
00:22:14.200 --> 00:22:18.100
So and of course, you can see the reassembling

432
00:22:17.100 --> 00:22:21.100
 process when you expand the

433
00:22:20.100 --> 00:22:23.300
 details in the packet.

434
00:22:23.600 --> 00:22:26.500
61 as in here under the

435
00:22:26.500 --> 00:22:27.400
 TCP field.

436
00:22:28.700 --> 00:22:30.500
So look at this it says.

437
00:22:31.300 --> 00:22:35.300
There are six packets have been reassembled and

438
00:22:34.300 --> 00:22:37.400
 they consist of the image file

439
00:22:37.400 --> 00:22:39.700
 which you can see under the TCP field.

440
00:22:40.700 --> 00:22:44.400
as JPEG file interchange format

441
00:22:44.900 --> 00:22:47.200
So with this packets we have

442
00:22:47.200 --> 00:22:50.300
 seen that the pdus have been sent to the

443
00:22:50.300 --> 00:22:53.400
 client by the server as in

444
00:22:53.400 --> 00:22:53.700
 here.

445
00:22:54.700 --> 00:22:57.600
In this way, we have seen an example traffic

446
00:22:57.600 --> 00:23:00.700
 use a TCP segmentation instead of

447
00:23:00.700 --> 00:23:02.400
 Ip fragmentation.

448
00:23:07.300 --> 00:23:10.400
Now let's focus on and investigate the IP

449
00:23:10.400 --> 00:23:13.200
 fragmentation process over the OSI model.

450
00:23:15.100 --> 00:23:18.500
As you know IP fragmentation arises at the

451
00:23:18.500 --> 00:23:21.600
 network layer of the OSI model specifically at

452
00:23:21.600 --> 00:23:22.800
 the IP protocol.

453
00:23:23.700 --> 00:23:26.700
And when a packet is generated by an application.

454
00:23:27.700 --> 00:23:31.600
It is passed down to the transport layer firstly

455
00:23:30.600 --> 00:23:34.300
 where it is segmented if

456
00:23:33.300 --> 00:23:34.600
 necessary.

457
00:23:35.300 --> 00:23:38.100
And the segments are then passed down to the

458
00:23:38.100 --> 00:23:42.000
 network layer where the IP protocol at its own header. The

459
00:23:41.600 --> 00:23:44.800
 resulting packet called an IP

460
00:23:44.800 --> 00:23:47.000
 packet is then passed down

461
00:23:47.100 --> 00:23:51.500
 to the data link layer and where

462
00:23:50.500 --> 00:23:53.600
 it is encapsulated in a

463
00:23:53.600 --> 00:23:57.200
 frame as you know in a frame and transmitted

464
00:23:56.200 --> 00:23:59.700
 over the network. When an

465
00:23:59.700 --> 00:24:02.400
 IP a packet is sent over a

466
00:24:02.400 --> 00:24:05.900
 network if the size of the IP datagram

467
00:24:05.900 --> 00:24:09.400
 exceeds the maximum transmission

468
00:24:08.400 --> 00:24:11.500
 unit exits. The

469
00:24:11.500 --> 00:24:15.000
 MTU value of the network is divided

470
00:24:14.300 --> 00:24:17.600
 into smaller chance called as

471
00:24:17.600 --> 00:24:21.300
 fragments or not that the NTU

472
00:24:20.300 --> 00:24:24.100
 is the largest packet size that

473
00:24:23.100 --> 00:24:26.400
 the network. I can't transmit without

474
00:24:26.400 --> 00:24:29.700
 fragmentation on the other hand IP fragmentation

475
00:24:29.700 --> 00:24:32.700
 is the process of breaking down a

476
00:24:32.700 --> 00:24:34.900
 large IP packet into smaller packets.

477
00:24:35.300 --> 00:24:38.100
Can be transmitted over a Network that has a

478
00:24:38.100 --> 00:24:41.500
 smaller maximum packet size. This is

479
00:24:41.500 --> 00:24:45.300
 necessary when the packet size exceeds the

480
00:24:44.300 --> 00:24:47.600
 maximum transmission unit

481
00:24:47.600 --> 00:24:48.900
 of the network.

482
00:24:49.700 --> 00:24:53.000
But when a large packet is encountered the

483
00:24:52.500 --> 00:24:56.100
 fragmentation processes initiated by

484
00:24:55.100 --> 00:24:58.400
 the standard typically at the

485
00:24:58.400 --> 00:25:01.600
 network layer the sander breaks the large packet

486
00:25:01.600 --> 00:25:04.300
 into smaller chunks smaller packets called

487
00:25:04.300 --> 00:25:07.500
 fragments and a size a

488
00:25:07.500 --> 00:25:10.600
 unique identification number to each fragment.

489
00:25:11.200 --> 00:25:14.900
So the sender also includes information in each fragments either

490
00:25:14.900 --> 00:25:17.000
 that indicates the total number of

491
00:25:17.700 --> 00:25:20.600
 fragments the fragment of set and the

492
00:25:20.600 --> 00:25:23.400
 original packets identification number.

493
00:25:24.100 --> 00:25:27.400
So the fragments are then transmitted over the network

494
00:25:27.400 --> 00:25:30.800
 and reassembled by the receiver. The

495
00:25:30.800 --> 00:25:33.600
 receiver uses the information in the fragment

496
00:25:33.600 --> 00:25:37.300
 heaters to reassemble the original Act.

497
00:25:38.700 --> 00:25:41.100
Now, let's investigate a sample Network

498
00:25:41.100 --> 00:25:44.000
 traffic used IP fragmentation.

499
00:25:50.600 --> 00:25:54.100
In order to observe the IP fragmentation process

500
00:25:53.100 --> 00:25:56.200
 in a real Network topic. I

501
00:25:56.200 --> 00:25:59.700
 have created a network traffic before in a

502
00:25:59.700 --> 00:26:00.500
 lab environment.

503
00:26:01.300 --> 00:26:04.600
I will show you in the next lesson how I created

504
00:26:04.600 --> 00:26:07.500
 the traffic in order to describe the pet

505
00:26:07.500 --> 00:26:11.000
 MTU Discovery process. Let's investigate only

506
00:26:10.500 --> 00:26:13.100
 the traffic packets to understand

507
00:26:13.100 --> 00:26:16.700
 IP fragmentation of and look

508
00:26:16.700 --> 00:26:18.600
 at this fragmented pack.

509
00:26:19.800 --> 00:26:21.200
the packet 13

510
00:26:23.600 --> 00:26:27.100
and let me show you the IP details IP

511
00:26:26.100 --> 00:26:28.300
 field details in here.

512
00:26:29.900 --> 00:26:32.700
And resizing the back details

513
00:26:32.700 --> 00:26:33.000
 window.

514
00:26:37.400 --> 00:26:40.600
So when we look at the black values in this

515
00:26:40.600 --> 00:26:43.100
 topic, as you know, we have

516
00:26:43.100 --> 00:26:47.000
 seen that the DF don't fragment

517
00:26:46.300 --> 00:26:49.900
 flag value this black

518
00:26:49.900 --> 00:26:53.000
 value bit is set to one in

519
00:26:52.200 --> 00:26:55.100
 the previous traffic that we have

520
00:26:55.100 --> 00:26:58.600
 investigate before the previous pickup file

521
00:26:58.600 --> 00:27:01.500
 the HTTP traffic pick a file where

522
00:27:01.500 --> 00:27:05.300
 the packet size is a adjusted by performing TCP

523
00:27:04.300 --> 00:27:07.800
 segmentation in that traffic. We

524
00:27:07.800 --> 00:27:11.300
 have seen the F value is set

525
00:27:10.300 --> 00:27:13.500
 to one but in this traffic

526
00:27:14.200 --> 00:27:18.100
We are seeing the DF value isn't set

527
00:27:18.100 --> 00:27:20.700
 and its value is zero.

528
00:27:21.700 --> 00:27:21.900
so

529
00:27:23.400 --> 00:27:26.500
because it isn't desirable to split the

530
00:27:26.500 --> 00:27:29.700
 packets into fragments using IP fragmentation.

531
00:27:31.100 --> 00:27:34.300
In the previous pickup file. We have seen the

532
00:27:34.300 --> 00:27:37.600
 DF value as one in order

533
00:27:37.600 --> 00:27:40.500
 to avoid the IP fragmentation to

534
00:27:40.500 --> 00:27:44.600
 prevent the fragmentation process. It

535
00:27:44.600 --> 00:27:47.900
 is preferred to adjust the packet length using

536
00:27:47.900 --> 00:27:50.300
 TCP segmentation in order

537
00:27:50.300 --> 00:27:53.200
 to have a good performance the good

538
00:27:53.200 --> 00:27:56.500
 Network performance and security, but now you

539
00:27:56.500 --> 00:27:59.600
 see the dfp is not set in here.

540
00:28:00.600 --> 00:28:02.700
And its value is zero.

541
00:28:03.900 --> 00:28:06.700
But it means this packet can

542
00:28:06.700 --> 00:28:09.000
 be fragmented and we look at

543
00:28:09.100 --> 00:28:11.300
 the more fragments value.

544
00:28:11.800 --> 00:28:12.700
It is said.

545
00:28:13.400 --> 00:28:16.300
And its value is 1 so.

546
00:28:17.400 --> 00:28:20.700
The MF leg the more fragments like

547
00:28:20.700 --> 00:28:23.700
 is used as part of the IP

548
00:28:23.700 --> 00:28:24.800
 fragmentation process.

549
00:28:25.600 --> 00:28:28.300
The more fragments of black is a

550
00:28:28.300 --> 00:28:31.600
 bit in the heater an IP packet

551
00:28:31.600 --> 00:28:34.400
 that is used to indicate whether effect is a fragment

552
00:28:34.400 --> 00:28:38.000
 of a larger packet or the only packet

553
00:28:37.200 --> 00:28:38.600
 being set.

554
00:28:39.300 --> 00:28:43.200
If the MF black if the more fragments select

555
00:28:42.200 --> 00:28:45.500
 is set to 1 as in

556
00:28:45.500 --> 00:28:45.600
 here.

557
00:28:46.600 --> 00:28:49.600
It indicates that there are more fragments of

558
00:28:49.600 --> 00:28:51.200
 the original packet to come.

559
00:28:52.300 --> 00:28:55.700
If the MF flag is set to 0 it indicates

560
00:28:55.700 --> 00:28:58.400
 that this is the last fragment of the packet.

561
00:28:59.100 --> 00:29:03.700
So here more fragments is set to 1 note

562
00:29:02.700 --> 00:29:05.500
 that and then this

563
00:29:05.500 --> 00:29:08.700
 is a fragment of a larger packet.

564
00:29:09.200 --> 00:29:12.300
And this is a component of a larger packet.

565
00:29:13.300 --> 00:29:16.600
So the fragment offset value the next

566
00:29:16.600 --> 00:29:20.100
 value you can see the fragment

567
00:29:19.100 --> 00:29:22.800
 offset is a value that indicates

568
00:29:22.800 --> 00:29:26.000
 the position of a fragment

569
00:29:25.700 --> 00:29:28.400
 relative to the beginning of the

570
00:29:28.400 --> 00:29:29.600
 original pack.

571
00:29:30.300 --> 00:29:31.800
and this information is

572
00:29:33.300 --> 00:29:37.200
pregnant offset information is used by the

573
00:29:37.200 --> 00:29:41.000
 receiver to reassemble the fragments in

574
00:29:40.300 --> 00:29:41.800
 the correct order.

575
00:29:42.700 --> 00:29:46.400
But it is used by the receiver reassemble

576
00:29:45.400 --> 00:29:49.000
 the fragments in the correct order. Keep

577
00:29:48.200 --> 00:29:51.800
 in mind that associated with the pregnant

578
00:29:51.800 --> 00:29:55.000
 offset information the destination

579
00:29:54.700 --> 00:29:58.100
 host reassembles the fragments

580
00:29:57.100 --> 00:30:00.900
 by using the information in

581
00:30:00.900 --> 00:30:03.800
 the fragment heaters. So the fragments

582
00:30:03.800 --> 00:30:06.800
 are reassembled in order based on

583
00:30:06.800 --> 00:30:10.600
 the fragment offset value and original

584
00:30:09.600 --> 00:30:12.400
 packets identification number

585
00:30:12.400 --> 00:30:13.800
 packet ID.

586
00:30:14.900 --> 00:30:15.800
is in here

587
00:30:17.800 --> 00:30:20.700
but here the fragment offset value

588
00:30:20.700 --> 00:30:21.900
 is zero.

589
00:30:23.600 --> 00:30:26.900
And it means the beginning part of this packet is

590
00:30:26.900 --> 00:30:27.000
 zero.

591
00:30:27.900 --> 00:30:29.400
and scrolling on

592
00:30:32.700 --> 00:30:36.300
so also you can see the expression

593
00:30:35.300 --> 00:30:39.000
 which says this in

594
00:30:38.400 --> 00:30:41.900
 here you can see this expression in

595
00:30:41.900 --> 00:30:42.300
 here.

596
00:30:43.200 --> 00:30:47.000
This expression which says this packet fragment is reassembled

597
00:30:46.500 --> 00:30:49.400
 by IP version 4

598
00:30:49.400 --> 00:30:52.800
 in according next

599
00:30:52.800 --> 00:30:55.400
 spec. It means the next pack.

600
00:30:55.400 --> 00:30:59.500
 So this fragment is reassembled

601
00:30:58.500 --> 00:31:02.400
 by people in the

602
00:31:01.400 --> 00:31:05.200
 next pack in the packet 14.

603
00:31:05.900 --> 00:31:09.500
And there is another either parameter

604
00:31:08.500 --> 00:31:10.300
 Maybe.

605
00:31:12.500 --> 00:31:14.900
you can recognize it and

606
00:31:16.200 --> 00:31:19.500
In here, there is another either parameter the

607
00:31:19.500 --> 00:31:22.400
 either check some perimeter. We

608
00:31:22.400 --> 00:31:26.200
 have the heater checksum field contains the

609
00:31:27.800 --> 00:31:30.500
take some value but it is used by

610
00:31:30.500 --> 00:31:34.400
 the destination to check for the Integrity of

611
00:31:34.400 --> 00:31:37.300
 the transmitted data. The size of this

612
00:31:37.300 --> 00:31:39.800
 field is 16 bits.

613
00:31:41.100 --> 00:31:42.400
as you can see the

614
00:31:43.400 --> 00:31:44.900
in the packet bytes

615
00:31:45.500 --> 00:31:48.700
pane when you click on the heater checksum,

616
00:31:48.700 --> 00:31:51.700
 then you will see its value corresponds to

617
00:31:51.700 --> 00:31:53.800
 the 16 bits.

618
00:31:55.600 --> 00:31:58.500
Okay, the heater check some value is calculated by

619
00:31:58.500 --> 00:32:01.300
 the standard and it sent

620
00:32:01.300 --> 00:32:03.100
 along with the IP header.

621
00:32:03.600 --> 00:32:06.800
When the datagram reaches the destination the

622
00:32:06.800 --> 00:32:09.400
 checksum is calculated by the destination by

623
00:32:09.400 --> 00:32:13.000
 using the same method with the source or the

624
00:32:12.400 --> 00:32:15.200
 sender if the value that

625
00:32:15.200 --> 00:32:18.600
 is calculated isn't equal to the specified either

626
00:32:18.600 --> 00:32:22.700
 check some value in the header of datagram the IP

627
00:32:21.700 --> 00:32:24.400
 datagram the packet is

628
00:32:24.400 --> 00:32:28.300
 discarded. So the either check

629
00:32:27.300 --> 00:32:30.600
 some value is calculated only with

630
00:32:30.600 --> 00:32:33.300
 the heater values and not by

631
00:32:33.300 --> 00:32:35.400
 using the data. It's a

632
00:32:36.500 --> 00:32:39.900
So every intermediary device that receives

633
00:32:39.900 --> 00:32:42.400
 the data must calculate the

634
00:32:42.400 --> 00:32:44.600
 header checksum value before forwarding.

635
00:32:46.100 --> 00:32:49.500
Keep in mind and when we look at the next packet.

636
00:32:50.400 --> 00:32:53.400
the reassembled packet the original

637
00:32:53.400 --> 00:32:54.900
 data

638
00:32:56.100 --> 00:33:00.600
We will see some details in here now in

639
00:32:59.600 --> 00:33:02.200
 this packet in the

640
00:33:02.200 --> 00:33:05.900
 packet 14 now we

641
00:33:05.900 --> 00:33:08.500
 can see the icmp field.

642
00:33:09.400 --> 00:33:12.300
Because the fragments are reassembled in

643
00:33:12.300 --> 00:33:15.700
 this packet, so this packet is an icmp pack.

644
00:33:15.700 --> 00:33:19.300
 Now look at the IP Fields firstly.

645
00:33:21.200 --> 00:33:24.900
In the previous packet fragment offset value was

646
00:33:24.900 --> 00:33:25.400
 Zero.

647
00:33:25.800 --> 00:33:26.500
as you can see

648
00:33:27.700 --> 00:33:30.900
the fragment offset value was 0 but now

649
00:33:30.900 --> 00:33:32.500
 we have seen.

650
00:33:34.100 --> 00:33:37.400
a different value for the fragment offset value

651
00:33:38.500 --> 00:33:41.700
as you can see in the packet 14 fragment

652
00:33:41.700 --> 00:33:46.300
 offset is now 1480. It

653
00:33:45.300 --> 00:33:48.200
 means that this package starts with

654
00:33:48.200 --> 00:33:51.300
 this white value with this part

655
00:33:51.300 --> 00:33:55.200
 A 1480 and

656
00:33:54.200 --> 00:33:59.600
 this packet starts with by 1400 80

657
00:34:00.500 --> 00:34:04.300
so as a result first fragment includes the

658
00:34:03.300 --> 00:34:06.700
 first fragment a packet 13

659
00:34:08.300 --> 00:34:14.000
includes bites between 0 and 1479 and

660
00:34:13.600 --> 00:34:17.000
 second fragment as the

661
00:34:16.300 --> 00:34:19.800
 packet 14 includes bytes

662
00:34:19.800 --> 00:34:20.500
 between

663
00:34:21.700 --> 00:34:24.900
1400 and 180 and

664
00:34:24.900 --> 00:34:25.800
 the remaining

665
00:34:26.700 --> 00:34:30.400
it consists of bytes between despite

666
00:34:29.400 --> 00:34:32.700
 and the remaining part if we

667
00:34:32.700 --> 00:34:36.100
 look at the IP version fragments build.

668
00:34:37.700 --> 00:34:41.900
In here IP version fragments field and

669
00:34:40.900 --> 00:34:43.900
 their total size.

670
00:34:43.900 --> 00:34:47.500
 You can see 1500 and

671
00:34:47.500 --> 00:34:48.000
 8.

672
00:34:48.900 --> 00:34:52.000
Oh here it says we have two

673
00:34:51.800 --> 00:34:54.500
 IP version 4 fragments and

674
00:34:54.500 --> 00:34:58.600
 their total size is 1508.

675
00:34:59.200 --> 00:35:01.600
So first one has a payload.

676
00:35:02.200 --> 00:35:05.700
First fragment as a payload with the

677
00:35:05.700 --> 00:35:08.200
 1480 bytes.

678
00:35:09.400 --> 00:35:12.600
And it is located frame frame packet

679
00:35:12.600 --> 00:35:15.700
 frame packet 13 is located in the

680
00:35:15.700 --> 00:35:19.100
 packet 13 and it has the byte

681
00:35:18.100 --> 00:35:23.000
 between 0 and the 1479.

682
00:35:24.200 --> 00:35:28.800
And second one is in frame 14

683
00:35:27.800 --> 00:35:31.600
 and in

684
00:35:31.600 --> 00:35:32.300
 this brain.

685
00:35:32.900 --> 00:35:35.800
It means that in this Frame, so it

686
00:35:35.800 --> 00:35:40.700
 has the bytes between 1480 and

687
00:35:40.700 --> 00:35:42.300
 1507.

688
00:35:42.900 --> 00:35:46.400
And totally 28 bytes.

689
00:35:47.800 --> 00:35:51.000
So it has a payload is a

690
00:35:50.300 --> 00:35:53.100
 payload with 28 bytes.

691
00:35:54.200 --> 00:35:59.000
Since it starts from by the formbyte 1400

692
00:35:57.700 --> 00:36:02.100
 80 it's fragment

693
00:36:01.100 --> 00:36:07.200
 offset value is 1480.

694
00:36:08.300 --> 00:36:11.600
Not that it starts from

695
00:36:11.600 --> 00:36:16.400
 bite for 1480. It's

696
00:36:15.400 --> 00:36:19.400
 fragment offset value is

697
00:36:18.400 --> 00:36:21.800
 1480.

698
00:36:22.500 --> 00:36:23.300
You can see here.

699
00:36:24.200 --> 00:36:28.600
And it says that the fragments are reassembled

700
00:36:27.600 --> 00:36:30.800
 in here in this

701
00:36:30.800 --> 00:36:31.500
 packet.

702
00:36:32.500 --> 00:36:35.000
So when you look at the icmp field.

703
00:36:36.700 --> 00:36:39.200
You can see another information associated with

704
00:36:39.200 --> 00:36:39.700
 the data.

705
00:36:40.600 --> 00:36:41.200
and

706
00:36:43.200 --> 00:36:47.200
you can see this is a pink request Act.

707
00:36:48.200 --> 00:36:51.600
This is the ink request. You can see under

708
00:36:51.600 --> 00:36:53.500
 the icmp field.

709
00:36:54.100 --> 00:36:57.400
Okay to sum up if it needs

710
00:36:57.400 --> 00:37:00.300
 to talk about transmission of the fragments in

711
00:37:00.300 --> 00:37:05.400
 the network. We can say those things. However fragments

712
00:37:03.400 --> 00:37:06.400
 can be lost in

713
00:37:06.400 --> 00:37:09.900
 transit and the reassembling process

714
00:37:09.900 --> 00:37:12.100
 May Fail if any of

715
00:37:12.100 --> 00:37:13.600
 the fragments are missing.

716
00:37:17.400 --> 00:37:20.500
So okay to sum up if it

717
00:37:20.500 --> 00:37:23.300
 needs to talk about the transmission of the

718
00:37:23.300 --> 00:37:26.400
 fragments in a network we can say those things.

719
00:37:27.700 --> 00:37:30.500
Fragments can be lost in transit and the

720
00:37:30.500 --> 00:37:33.300
 reassembling process May Fail if any of

721
00:37:33.300 --> 00:37:34.800
 the fragments are missing.

722
00:37:35.600 --> 00:37:38.200
Also since fragments are

723
00:37:38.200 --> 00:37:41.500
 transmitted separately they may you know

724
00:37:41.500 --> 00:37:42.200
 out of order.

725
00:37:43.400 --> 00:37:46.100
And you can see some Auto folder packets in your

726
00:37:46.100 --> 00:37:49.700
 network in your network traffic file therefore.

727
00:37:50.800 --> 00:37:53.700
The reassembling process must handle missing

728
00:37:53.700 --> 00:37:57.000
 or out of order unordered fragments

729
00:37:56.200 --> 00:37:59.600
 fragmentation can also cause a

730
00:37:59.600 --> 00:38:01.900
 significant increase in overhead.

731
00:38:02.600 --> 00:38:05.600
And reduce the efficiency of an Network.

732
00:38:06.500 --> 00:38:09.500
And for this reason it's generally desirable to

733
00:38:09.500 --> 00:38:12.600
 avoid fragmentation by using a Network that

734
00:38:12.600 --> 00:38:15.600
 has a large enough empty you or by

735
00:38:15.600 --> 00:38:18.200
 using a protocol that can segment the data

736
00:38:18.200 --> 00:38:21.600
 at a higher level such as ECP.

737
00:38:24.700 --> 00:38:27.400
So now let's emphasize that

738
00:38:27.400 --> 00:38:30.800
 once again IP fragmentation can cause

739
00:38:30.800 --> 00:38:33.600
 a significant increase in

740
00:38:33.600 --> 00:38:36.800
 overhead as the original packet is

741
00:38:36.800 --> 00:38:39.900
 simply into multiple smaller chunks and

742
00:38:39.900 --> 00:38:42.900
 each fragment must include its

743
00:38:42.900 --> 00:38:46.800
 own hidden information additionally fragmentation

744
00:38:45.800 --> 00:38:48.900
 can lead the performance issues

745
00:38:48.900 --> 00:38:51.100
 as fragments may be lost

746
00:38:51.100 --> 00:38:54.900
 in transit or AI autofolder causing

747
00:38:54.900 --> 00:38:57.900
 delays in reassembling the original packet.

748
00:38:58.500 --> 00:39:02.100
Another important aspect of Ip fragmentation

749
00:39:01.100 --> 00:39:04.700
 is the handling of fragments at

750
00:39:04.700 --> 00:39:07.800
 the network devices like routers when a

751
00:39:07.800 --> 00:39:10.800
 router receives air fragment, it must

752
00:39:10.800 --> 00:39:13.500
 decide whether to forward the fragment

753
00:39:13.500 --> 00:39:14.400
 or drop it.

754
00:39:15.400 --> 00:39:18.900
The router uses the information in the fragment header

755
00:39:18.900 --> 00:39:20.800
 to make this decision.

756
00:39:21.500 --> 00:39:24.200
If the router determines that the fragment

757
00:39:24.200 --> 00:39:27.300
 is the first fragment it will forward it

758
00:39:27.300 --> 00:39:28.900
 to the next.

759
00:39:30.200 --> 00:39:33.500
But if the rotor receives a non-first fragment,

760
00:39:33.500 --> 00:39:36.400
 it will check its fragment buffer to

761
00:39:36.400 --> 00:39:40.400
 see if it has already received the first fragment.

762
00:39:41.200 --> 00:39:44.600
If the first fragment is present in the buffer the router

763
00:39:44.600 --> 00:39:47.000
 will forward the non-first fragment.

764
00:39:47.600 --> 00:39:51.300
If not, the rotor will drop the non-first

765
00:39:50.300 --> 00:39:51.800
 fragment.

766
00:39:52.800 --> 00:39:56.600
And it is worth noting that IP fragmentation

767
00:39:56.600 --> 00:40:00.200
 can also be exploited in various

768
00:39:59.200 --> 00:40:01.800
 types of attacks.

769
00:40:02.900 --> 00:40:06.200
Such as fragmentation attacks, which

770
00:40:05.200 --> 00:40:08.700
 can be used to evade network security devices

771
00:40:08.700 --> 00:40:11.700
 or cause a denial of service those

772
00:40:11.700 --> 00:40:14.700
 back and therefore net Network

773
00:40:14.700 --> 00:40:17.200
 administrators should be aware of

774
00:40:17.200 --> 00:40:21.900
 the financial risks and take appropriate measures

775
00:40:21.900 --> 00:40:23.400
 to mitigate.

776
00:40:24.500 --> 00:40:25.700
and in summary

777
00:40:26.300 --> 00:40:30.100
IP fragmentation is a process used to

778
00:40:29.100 --> 00:40:32.400
 break down large IP packets into

779
00:40:32.400 --> 00:40:35.900
 smaller packets that can be transmitted over a Network that

780
00:40:35.900 --> 00:40:37.400
 has a smaller MTU.

781
00:40:38.200 --> 00:40:39.900
the fragmentation process is

782
00:40:41.900 --> 00:40:44.400
at the fragments are reassembled by

783
00:40:44.400 --> 00:40:45.000
 the receiver.

784
00:40:46.500 --> 00:40:49.900
However, fragmentation can cause a significant

785
00:40:49.900 --> 00:40:53.100
 increase in overhead lead

786
00:40:52.100 --> 00:40:55.700
 to Performance issues and be

787
00:40:55.700 --> 00:40:59.200
 exploited in various types of attacks. Therefore,

788
00:40:58.200 --> 00:41:02.100
 it's generally recommend to avoid fragmentation

789
00:41:01.100 --> 00:41:05.300
 to avoid IP fragmentation by using

790
00:41:05.300 --> 00:41:06.000
 a network.

791
00:41:07.600 --> 00:41:10.400
There's a enough MTU or by using

792
00:41:10.400 --> 00:41:13.300
 a protocol that can segment the

793
00:41:13.300 --> 00:41:16.400
 data at a higher level such as DCP.

794
00:41:20.800 --> 00:41:23.300
So that's all for now. See you on the

795
00:41:23.300 --> 00:41:23.600
 next video.
