WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.500 --> 00:00:10.300
Hello everyone in this lesson. I will tell you about the

1
00:00:10.300 --> 00:00:12.100
 pet MTU discovery.

2
00:00:13.500 --> 00:00:17.100
Firstly I want to tell you the MSS and MTU

3
00:00:16.100 --> 00:00:17.600
 Concepts.

4
00:00:20.600 --> 00:00:23.900
Here we see an ordinary frame structure as

5
00:00:23.900 --> 00:00:26.600
 you can see a frame as some

6
00:00:26.600 --> 00:00:29.400
 heaters as tcp/ip and ethernet in

7
00:00:29.400 --> 00:00:32.700
 addition to payload which contains actual data

8
00:00:32.700 --> 00:00:35.400
 as you know, when an application data is

9
00:00:35.400 --> 00:00:38.900
 payload goes over the network layers

10
00:00:38.900 --> 00:00:41.600
 from top to down in every layer a

11
00:00:41.600 --> 00:00:44.900
 heater is added to the payload. Let's briefly

12
00:00:44.900 --> 00:00:47.600
 recall. The journey story payload is generated

13
00:00:47.600 --> 00:00:50.800
 in the application layer. There is no iterated

14
00:00:50.800 --> 00:00:53.800
 time of production is alone. Then as

15
00:00:53.800 --> 00:00:56.300
 the application layer starts go down

16
00:00:56.300 --> 00:01:00.100
 either start to be edit and TCP

17
00:00:59.100 --> 00:01:02.900
 heater is added in transport layer

18
00:01:02.900 --> 00:01:05.600
 and it goes down

19
00:01:05.600 --> 00:01:08.700
 to the network layer. Then at the

20
00:01:08.700 --> 00:01:11.600
 network layer and IP heater is added by

21
00:01:11.600 --> 00:01:12.600
 the IP protocol.

22
00:01:13.300 --> 00:01:16.600
So and it goes down to the data

23
00:01:16.600 --> 00:01:19.500
 link layer in the data link layer, the

24
00:01:19.500 --> 00:01:22.700
 internet either is added

25
00:01:22.700 --> 00:01:22.900
 last.

26
00:01:23.600 --> 00:01:26.800
And with the addition of this ethernet header,

27
00:01:26.800 --> 00:01:28.700
 it becomes a frame.

28
00:01:32.500 --> 00:01:35.700
So that's why the structure we see here is now called a

29
00:01:35.700 --> 00:01:38.700
 frame finally. You already know

30
00:01:38.700 --> 00:01:41.700
 that it turns into bits at

31
00:01:41.700 --> 00:01:42.400
 the physical layer.

32
00:01:44.400 --> 00:01:47.800
Now, let's discover the MSS over this structure.

33
00:01:49.700 --> 00:01:52.400
MSS or maximum segment size is

34
00:01:52.400 --> 00:01:55.900
 a parameter used in transmission control protocol or

35
00:01:55.900 --> 00:01:58.500
 use it in TCP to specify the

36
00:01:58.500 --> 00:02:01.600
 maximum size of a data segment

37
00:02:01.600 --> 00:02:05.000
 that can be sent in a single packet and

38
00:02:04.400 --> 00:02:07.600
 it is the maximum amount of data

39
00:02:07.600 --> 00:02:10.400
 that can be carried in a single TCP segment.

40
00:02:10.400 --> 00:02:14.000
 So MSS is used by both

41
00:02:13.400 --> 00:02:17.000
 the Thunder and the receiver to determine the

42
00:02:16.700 --> 00:02:19.600
 maximum size of a packet

43
00:02:19.600 --> 00:02:21.900
 that can be sand without fragmentation.

44
00:02:22.700 --> 00:02:25.700
And the MSS is usually defined as

45
00:02:25.700 --> 00:02:28.700
 the maximum size of a packet that

46
00:02:28.700 --> 00:02:31.600
 can be sent over a particular the network.

47
00:02:31.600 --> 00:02:35.100
 It's calculated by subtracting the

48
00:02:34.100 --> 00:02:38.000
 size of the IP and TCP heaters

49
00:02:37.100 --> 00:02:40.500
 setting the MSS too high

50
00:02:40.500 --> 00:02:43.300
 and result in fragmentation can reduce

51
00:02:43.300 --> 00:02:47.100
 speed due to the additional overhead

52
00:02:46.100 --> 00:02:49.500
 of the assembling the packets at the

53
00:02:49.500 --> 00:02:53.200
 destination. So it can also increase

54
00:02:52.200 --> 00:02:56.000
 the risk of packets being dropped and

55
00:02:55.800 --> 00:02:58.300
 setting the MSS too low

56
00:02:58.300 --> 00:03:01.600
 can also decrease performance as it limits

57
00:03:01.600 --> 00:03:04.600
 the amount of data that can be sent

58
00:03:04.600 --> 00:03:07.100
 in a single packet leading to

59
00:03:07.100 --> 00:03:10.500
 increase overhead and increased number

60
00:03:10.500 --> 00:03:13.600
 of packets. So a standard and

61
00:03:13.600 --> 00:03:16.000
 specify the MSS the MSS of a

62
00:03:16.700 --> 00:03:19.300
 connection by including the MSS option in

63
00:03:19.300 --> 00:03:22.500
 the TCP sync packet during the connection set.

64
00:03:23.400 --> 00:03:27.000
So the receiver can also specify the MSS

65
00:03:26.200 --> 00:03:29.100
 by including the MSS option in

66
00:03:29.100 --> 00:03:32.900
 the TCP scene aspected and the

67
00:03:32.900 --> 00:03:35.300
 smaller of these two values is used as

68
00:03:35.300 --> 00:03:37.100
 the MSS or the connection.

69
00:03:38.600 --> 00:03:41.600
Setting the MSS too high can cause fragmentation.

70
00:03:42.300 --> 00:03:42.500
so

71
00:03:45.800 --> 00:03:49.900
now let's look at the MTU structure

72
00:03:48.900 --> 00:03:51.500
 in here and the

73
00:03:51.500 --> 00:03:54.400
 maximum transmission unit. As you know,

74
00:03:54.400 --> 00:03:57.800
 MTU means maximum transmission

75
00:03:57.800 --> 00:04:00.300
 unit. And MTU is the

76
00:04:00.300 --> 00:04:03.400
 largest size of a packet that can be transmitted

77
00:04:03.400 --> 00:04:06.800
 over a network without fragmentation. It is

78
00:04:06.800 --> 00:04:09.700
 a network layer perimeter that

79
00:04:09.700 --> 00:04:12.800
 is used to specify the maximum size

80
00:04:12.800 --> 00:04:16.200
 of a packet and sand or particular Network

81
00:04:15.200 --> 00:04:19.200
 in some cases routers may

82
00:04:19.200 --> 00:04:22.900
 also perform fragmentation themselves if the MTU

83
00:04:22.900 --> 00:04:25.500
 of next up next up Network

84
00:04:25.500 --> 00:04:29.000
 smaller than the MTU of

85
00:04:28.300 --> 00:04:31.200
 the current Network and this is

86
00:04:31.200 --> 00:04:34.300
 known as at and you discover

87
00:04:35.200 --> 00:04:35.300
so

88
00:04:36.200 --> 00:04:40.000
how we calculate the payload size and buy

89
00:04:39.700 --> 00:04:42.400
 MTU size or the structure?

90
00:04:45.200 --> 00:04:50.100
Let's suppose that the MDU size of a network is 1500

91
00:04:48.100 --> 00:04:50.500
 bytes.

92
00:04:51.300 --> 00:04:54.700
The size of the IP header can change

93
00:04:54.700 --> 00:04:58.100
 a but a common sizes 20 bytes

94
00:04:57.100 --> 00:05:01.300
 for IP version or and party

95
00:05:00.300 --> 00:05:03.300
 bytes for IP version 6

96
00:05:03.300 --> 00:05:06.500
 and the size of the TCP heater

97
00:05:06.500 --> 00:05:09.700
 can also change but common size of

98
00:05:09.700 --> 00:05:12.700
 the ECP heater is 20 bytes

99
00:05:12.700 --> 00:05:15.100
 as well. So for this example,

100
00:05:15.100 --> 00:05:18.600
 let's assume that we are using IP

101
00:05:18.600 --> 00:05:21.000
 version 4 and the size of

102
00:05:21.100 --> 00:05:24.900
 the IP heater is 20 bytes and the size of the TCP heater

103
00:05:24.900 --> 00:05:27.200
 is again to antibiotes.

104
00:05:27.800 --> 00:05:31.200
So to calculate the MTU size

105
00:05:31.200 --> 00:05:34.300
 we subtract the sizes of

106
00:05:34.300 --> 00:05:35.100
 IP.

107
00:05:37.100 --> 00:05:40.800
And we subtract the TCP headers from

108
00:05:40.800 --> 00:05:43.200
 the mpu size or as well.

109
00:05:45.200 --> 00:05:48.700
Now as you can see, we have subtracted the

110
00:05:48.700 --> 00:05:51.700
 IP header size and it

111
00:05:51.700 --> 00:05:55.000
 isip size from the MTU size

112
00:05:54.400 --> 00:05:59.700
 and the result is 1460

113
00:05:57.700 --> 00:06:01.200
 as payload

114
00:06:00.200 --> 00:06:01.900
 data size.

115
00:06:02.500 --> 00:06:05.500
So in this example the maximum size

116
00:06:05.500 --> 00:06:10.500
 of the data payload in a packet is 1460 bytes

117
00:06:10.500 --> 00:06:13.600
 and any packet with a data payload

118
00:06:13.600 --> 00:06:16.000
 larger than this size.

119
00:06:17.400 --> 00:06:20.400
Larger than 1,460 bytes would

120
00:06:20.400 --> 00:06:23.300
 need to be fragmented or transmission over

121
00:06:23.300 --> 00:06:26.500
 this this network and it is important to

122
00:06:26.500 --> 00:06:29.400
 note that this is just an example and

123
00:06:29.400 --> 00:06:32.700
 actual MTU size and either

124
00:06:32.700 --> 00:06:36.600
 sizes can change depends on which Protocols

125
00:06:35.600 --> 00:06:38.400
 are being used in this

126
00:06:38.400 --> 00:06:42.200
 traffic. So for example, if icmp

127
00:06:41.200 --> 00:06:44.400
 protocol heater is used instead of

128
00:06:44.400 --> 00:06:47.700
 the TCP protocol TCP

129
00:06:47.700 --> 00:06:51.100
 leader, it will occupy eight bytes

130
00:06:50.100 --> 00:06:53.700
 not 20 bytes for this

131
00:06:53.700 --> 00:06:56.500
 part and the payload amount will

132
00:06:56.500 --> 00:06:59.600
 also change accordingly in

133
00:06:59.600 --> 00:07:03.700
 case the empty size 1500 bytes.

134
00:07:03.700 --> 00:07:07.000
 We see the total packet size as

135
00:07:07.900 --> 00:07:11.300
1514 since

136
00:07:10.300 --> 00:07:13.400
 an internet either will

137
00:07:13.400 --> 00:07:16.500
 be added to the packet and when we add

138
00:07:16.500 --> 00:07:19.100
 the internet either size to the

139
00:07:19.100 --> 00:07:23.600
 MTU size will be 1500 and

140
00:07:22.600 --> 00:07:25.800
 14 bytes as

141
00:07:25.800 --> 00:07:29.000
 a packet size. So the result

142
00:07:28.600 --> 00:07:32.300
 will be 1500 14

143
00:07:31.300 --> 00:07:34.500
 bytes. Okay. Now there

144
00:07:34.500 --> 00:07:37.700
 will be some addition bites in total

145
00:07:37.700 --> 00:07:40.800
 packet size and 14 more bites

146
00:07:40.800 --> 00:07:43.700
 are added for the internet either

147
00:07:43.700 --> 00:07:47.300
 and keep in mind that these 14 bites

148
00:07:46.300 --> 00:07:50.800
 are not included event calculating

149
00:07:49.800 --> 00:07:52.400
 the empty you size

150
00:07:52.400 --> 00:07:56.200
 Because the Internet heater isn't included

151
00:07:55.200 --> 00:07:57.800
 in the empty you

152
00:07:58.600 --> 00:08:00.900
and now let's move on.

153
00:08:03.400 --> 00:08:06.900
Okay. Now we will observe how to

154
00:08:06.900 --> 00:08:09.400
 apply the IP fragmentation. Also, we

155
00:08:09.400 --> 00:08:12.200
 will see the pet empty Discovery and

156
00:08:12.200 --> 00:08:15.400
 how to find the maximum payload size

157
00:08:15.400 --> 00:08:19.700
 to do this. We are gonna send some icmp

158
00:08:18.700 --> 00:08:22.300
 pink packets with different packs with

159
00:08:21.300 --> 00:08:25.000
 different packet lengths different

160
00:08:24.800 --> 00:08:27.500
 packet size to a Target

161
00:08:27.500 --> 00:08:30.500
 machine and it means that we

162
00:08:30.500 --> 00:08:33.800
 will change the pink packets. We will

163
00:08:33.800 --> 00:08:36.400
 change the sorry. It means

164
00:08:36.400 --> 00:08:39.700
 that we will change the pink package lengths

165
00:08:39.700 --> 00:08:43.300
 step by step one by one and we

166
00:08:42.300 --> 00:08:46.200
 will increase and decrease the

167
00:08:45.200 --> 00:08:48.200
 size of the pink packets in

168
00:08:48.200 --> 00:08:50.500
 order to see the maximum payload size.

169
00:08:51.300 --> 00:08:55.100
Here we have a topology like as

170
00:08:54.100 --> 00:08:57.700
 you see I have a Windows machine on

171
00:08:57.700 --> 00:09:00.700
 the left side and I have a column

172
00:09:00.700 --> 00:09:03.600
 machine on the other side. So in this lab environment,

173
00:09:03.600 --> 00:09:06.700
 I have done the process include sending

174
00:09:06.700 --> 00:09:09.900
 pink packets in different lengths to the

175
00:09:09.900 --> 00:09:12.500
 Target. I have captured the traffic during

176
00:09:12.500 --> 00:09:15.300
 these steps. So let's take

177
00:09:15.300 --> 00:09:19.900
 a look at these pink steps and network packets

178
00:09:19.900 --> 00:09:20.900
 in Russia.

179
00:09:32.300 --> 00:09:35.600
Now in here we will send pink packets

180
00:09:35.600 --> 00:09:39.000
 from the Windows machine to the Target before

181
00:09:38.300 --> 00:09:41.300
 doing this. We are learning the

182
00:09:41.300 --> 00:09:44.700
 MTU value of our interface and

183
00:09:44.700 --> 00:09:46.100
 you can see

184
00:09:47.100 --> 00:09:50.700
the interface information by this amount

185
00:09:53.600 --> 00:09:56.600
of you can open the windows Powershell and

186
00:09:56.600 --> 00:10:00.200
 type this netsh command. And

187
00:09:59.200 --> 00:10:03.100
 when you click on the enter after typing

188
00:10:02.100 --> 00:10:06.500
 the command will bring interfaces that

189
00:10:05.500 --> 00:10:08.600
 we have and you

190
00:10:08.600 --> 00:10:11.600
 can see the ethernet interface that

191
00:10:11.600 --> 00:10:14.900
 I am using actively and it's empty

192
00:10:14.900 --> 00:10:18.600
 size is 1500 bytes

193
00:10:17.600 --> 00:10:19.500
 as usual.

194
00:10:20.600 --> 00:10:24.800
So now we have the information about MTU length

195
00:10:23.800 --> 00:10:26.400
 in here. We have

196
00:10:26.400 --> 00:10:30.600
 the MTU size as 1500 bytes.

197
00:10:31.900 --> 00:10:34.200
Let's start sending pink packets now.

198
00:10:37.300 --> 00:10:40.600
Firstly I sent a standard pink packet in

199
00:10:40.600 --> 00:10:43.900
 here as you can see and it has

200
00:10:43.900 --> 00:10:46.200
 32 bytes packets.

201
00:10:46.200 --> 00:10:49.200
 Let's see these packets in Wireshark now.

202
00:10:49.800 --> 00:10:52.700
in here as you can see, so here

203
00:10:52.700 --> 00:10:56.200
 is decent or pink pink

204
00:10:55.200 --> 00:10:57.700
 request packets and

205
00:10:59.600 --> 00:11:03.500
We will be receiving four pink five

206
00:11:02.500 --> 00:11:06.000
 packets as response. And

207
00:11:05.200 --> 00:11:08.600
 for this reason first eight

208
00:11:08.600 --> 00:11:10.700
 packets belong to this pink.

209
00:11:11.300 --> 00:11:12.100
conversation

210
00:11:12.800 --> 00:11:15.500
so we send pink packets which has

211
00:11:15.500 --> 00:11:17.300
 32 bytes data.

212
00:11:18.800 --> 00:11:20.600
As you can see in here.

213
00:11:21.900 --> 00:11:25.200
But we see their length in Wireshark

214
00:11:24.200 --> 00:11:27.700
 as 74 bytes why

215
00:11:27.700 --> 00:11:30.700
 let's look at the first packet

216
00:11:30.700 --> 00:11:34.500
 details in order to understand this difference.

217
00:11:36.100 --> 00:11:36.200
So

218
00:11:37.700 --> 00:11:41.200
I'm expanding the isi icmp protocol

219
00:11:40.200 --> 00:11:43.400
 field in here and we can

220
00:11:43.400 --> 00:11:46.200
 see the data built in the details.

221
00:11:47.400 --> 00:11:51.400
So look, our data size is again 32

222
00:11:50.400 --> 00:11:54.100
 bytes as it should be. So this

223
00:11:53.100 --> 00:11:57.700
 means the payload part is 32

224
00:11:56.700 --> 00:11:59.300
 bytes, but when you

225
00:11:59.300 --> 00:12:00.800
 click on the icmp field

226
00:12:01.600 --> 00:12:05.300
You see that the total size of the icmp

227
00:12:04.300 --> 00:12:07.900
 field is 40 bytes. Yes,

228
00:12:07.900 --> 00:12:10.500
 because total icmp header size

229
00:12:10.500 --> 00:12:13.300
 is 8 bytes. We should know that

230
00:12:13.300 --> 00:12:16.700
 an icmp packet consists of the payload and

231
00:12:16.700 --> 00:12:17.400
 the heater.

232
00:12:17.900 --> 00:12:20.600
I mean the icmp components

233
00:12:20.600 --> 00:12:23.800
 are as the header and the payload

234
00:12:23.800 --> 00:12:26.200
 part and Hider part is

235
00:12:26.200 --> 00:12:29.400
 8 bytes. The heater part.

236
00:12:29.400 --> 00:12:32.600
 The size is 8 bytes. And the

237
00:12:32.600 --> 00:12:35.900
 payload part is 32 bytes as

238
00:12:35.900 --> 00:12:36.500
 in here.

239
00:12:37.100 --> 00:12:41.000
So the icmp field is portabytes in

240
00:12:40.000 --> 00:12:41.100
 total.

241
00:12:42.200 --> 00:12:44.600
now move on to calculate

242
00:12:46.700 --> 00:12:49.200
Let me click on the IP field

243
00:12:49.200 --> 00:12:51.300
 as you can see in here.

244
00:12:52.600 --> 00:12:55.500
When you click on the IP field you can see this part

245
00:12:55.500 --> 00:12:58.400
 has 20 bytes or IP.

246
00:13:00.400 --> 00:13:03.200
So and we already have party bytes or

247
00:13:03.200 --> 00:13:06.600
 icmp now adding this 20 bytes

248
00:13:06.600 --> 00:13:10.300
 for IP. The result will be 60 bytes.

249
00:13:10.300 --> 00:13:13.700
 So okay with the IP field we have

250
00:13:13.700 --> 00:13:14.800
 60 bytes now.

251
00:13:15.900 --> 00:13:18.500
and when we click on the ethernet field

252
00:13:19.200 --> 00:13:22.400
We see that the internet either size is

253
00:13:22.400 --> 00:13:25.700
 14 bytes. So this was the

254
00:13:25.700 --> 00:13:28.300
 last either part and with the internet

255
00:13:28.300 --> 00:13:32.400
 60 bytes plus 14 bytes

256
00:13:31.400 --> 00:13:36.000
 is equal to 70 or

257
00:13:35.900 --> 00:13:39.000
 bytes. So in this way total packet

258
00:13:38.100 --> 00:13:41.100
 size is 74 bytes.

259
00:13:41.700 --> 00:13:45.100
And now let's change the pink data

260
00:13:44.100 --> 00:13:46.900
 size to different value.

261
00:13:48.400 --> 00:13:52.600
We will change the payload size from 32

262
00:13:51.600 --> 00:13:54.100
 to different value.

263
00:13:56.500 --> 00:13:59.800
In order to arrange the payload data

264
00:13:59.800 --> 00:14:03.600
 size. We used even LC

265
00:14:02.600 --> 00:14:06.000
 which means length and

266
00:14:05.500 --> 00:14:09.000
 I have set the payload size as

267
00:14:08.600 --> 00:14:11.200
 1500 bytes this

268
00:14:11.200 --> 00:14:11.600
 time.

269
00:14:12.400 --> 00:14:15.800
So, you know MTU was the

270
00:14:15.800 --> 00:14:19.400
 size of the part excluding the ethernet heater

271
00:14:18.400 --> 00:14:22.800
 and with 1500

272
00:14:21.800 --> 00:14:24.700
 bytes for payload.

273
00:14:25.300 --> 00:14:29.200
MTU part is now larger than the size. It

274
00:14:28.200 --> 00:14:31.500
 should as it should be for the

275
00:14:31.500 --> 00:14:34.200
 MTU value has been exceeded.

276
00:14:34.800 --> 00:14:37.400
By this payload value and in

277
00:14:37.400 --> 00:14:41.000
 this case IP fragmentation takes place

278
00:14:40.900 --> 00:14:43.800
 when we are sending the pink

279
00:14:43.800 --> 00:14:46.700
 packets and the pink packet

280
00:14:46.700 --> 00:14:49.700
 is a split into fragments will

281
00:14:49.700 --> 00:14:53.200
 be split into fragments and then

282
00:14:52.200 --> 00:14:55.600
 we'll look at these fragments in Wireshark.

283
00:14:56.900 --> 00:14:58.300
As you can see in here.

284
00:14:59.200 --> 00:15:02.800
it starts from the packet 13 and

285
00:15:03.800 --> 00:15:06.800
we see that each pink packet will

286
00:15:06.800 --> 00:15:09.800
 be split into the two fragment and

287
00:15:09.800 --> 00:15:12.400
 click on the first fragment now.

288
00:15:13.100 --> 00:15:14.800
on the packet 13

289
00:15:17.500 --> 00:15:21.500
you see why shark is pointing the second

290
00:15:20.500 --> 00:15:23.400
 component with a gray

291
00:15:23.400 --> 00:15:23.600
 point.

292
00:15:25.200 --> 00:15:28.400
As usual so when you look at the details for the

293
00:15:28.400 --> 00:15:29.500
 first fragment.

294
00:15:30.600 --> 00:15:34.300
First fragment has 148 bytes

295
00:15:33.300 --> 00:15:36.500
 for the payload data.

296
00:15:37.300 --> 00:15:40.900
And you see that in the IP version

297
00:15:40.900 --> 00:15:43.900
 or field it says

298
00:15:43.900 --> 00:15:46.500
 this fragment has been reassembled in

299
00:15:46.500 --> 00:15:49.700
 packet 14, which is our

300
00:15:49.700 --> 00:15:50.500
 next pack.

301
00:15:51.800 --> 00:15:53.300
in the packet 14

302
00:15:54.600 --> 00:15:57.400
So this first fragment has

303
00:15:57.400 --> 00:16:00.800
 a 1480 bytes data.

304
00:16:05.100 --> 00:16:08.400
as you can see in here and the second one has

305
00:16:10.100 --> 00:16:11.500
28 bytes

306
00:16:12.200 --> 00:16:15.700
so second fragment is 28 Parts

307
00:16:15.700 --> 00:16:19.400
 because it consists of the payload and icmp header.

308
00:16:20.100 --> 00:16:23.500
So payload Parts size is 20 bytes

309
00:16:23.500 --> 00:16:27.100
 and icmp either part is 8

310
00:16:26.100 --> 00:16:29.400
 bytes in total we have

311
00:16:29.400 --> 00:16:30.000
 actually

312
00:16:31.300 --> 00:16:32.400
as you can see in here.

313
00:16:34.200 --> 00:16:37.800
We have actually 1500 bytes per

314
00:16:37.800 --> 00:16:40.500
 payload since two fragments

315
00:16:40.500 --> 00:16:43.800
 are reassembled in this packet VC old

316
00:16:43.800 --> 00:16:44.700
 data in here.

317
00:16:45.400 --> 00:16:48.600
BC first frame a payload

318
00:16:48.600 --> 00:16:51.500
 data and we see

319
00:16:51.500 --> 00:16:54.600
 the second fragment payload data.

320
00:16:55.400 --> 00:16:55.600
and

321
00:16:56.700 --> 00:17:00.200
we see also the icmp either

322
00:16:59.200 --> 00:17:02.100
 data in addition

323
00:17:02.100 --> 00:17:05.700
 to the payload data with the 8

324
00:17:05.700 --> 00:17:08.100
 bytes and let's look at

325
00:17:08.100 --> 00:17:10.000
 the new pink packet.

326
00:17:10.900 --> 00:17:14.200
And let's resize the payload data

327
00:17:13.200 --> 00:17:14.300
 again.

328
00:17:15.100 --> 00:17:18.400
We will be will resize the payload data again.

329
00:17:20.800 --> 00:17:24.100
So this time I have set the payload a

330
00:17:23.100 --> 00:17:27.200
 payload size to 1480 bytes.

331
00:17:26.200 --> 00:17:30.400
 When I click on the packet associated

332
00:17:29.400 --> 00:17:33.800
 with this painting command. We

333
00:17:32.800 --> 00:17:34.700
 will see the details.

334
00:17:35.600 --> 00:17:38.600
I mean here with this packet,

335
00:17:38.600 --> 00:17:41.200
 it starts the new pink packets.

336
00:17:42.500 --> 00:17:45.700
and when I click on the packet to 99

337
00:17:45.700 --> 00:17:47.500
 I see that the

338
00:17:49.500 --> 00:17:54.200
First fragment data size is 14 180

339
00:17:52.200 --> 00:17:55.700
 bytes and it is

340
00:17:55.700 --> 00:17:59.500
 reassembled the impacted 30.

341
00:18:00.500 --> 00:18:03.700
But when you look at the Epic 30,

342
00:18:03.700 --> 00:18:07.300
 you will see the reassembled version

343
00:18:06.300 --> 00:18:09.400
 of the pink egg.

344
00:18:10.000 --> 00:18:10.200
and

345
00:18:11.300 --> 00:18:13.600
click on the packet party now.

346
00:18:14.500 --> 00:18:15.500
Let's look at here.

347
00:18:16.200 --> 00:18:20.100
I see two IP version fragments again.

348
00:18:19.100 --> 00:18:23.500
 First one has payload with

349
00:18:22.500 --> 00:18:25.800
 the 1480 bytes

350
00:18:25.800 --> 00:18:27.100
 and second one.

351
00:18:28.200 --> 00:18:32.200
As the payload with 8 bytes only 8 bytes

352
00:18:31.200 --> 00:18:34.700
 as you get this part contains

353
00:18:34.700 --> 00:18:37.900
 icmp either payload by sampy

354
00:18:37.900 --> 00:18:41.100
 heater part with this 8 bytes and

355
00:18:40.100 --> 00:18:43.200
 it means that if I would have

356
00:18:43.200 --> 00:18:48.100
 arranged the payload size as 1472 instead

357
00:18:47.100 --> 00:18:51.000
 of 1480. It

358
00:18:50.200 --> 00:18:53.600
 wouldn't need to fragmentation. So it

359
00:18:53.600 --> 00:18:56.900
 could send Pink as a single pack because

360
00:18:56.900 --> 00:18:59.500
 this eight parts part is

361
00:18:59.500 --> 00:19:00.500
 Surplus.

362
00:19:01.900 --> 00:19:05.000
Let's arrange the payload size as

363
00:19:04.200 --> 00:19:07.600
 1472 bytes.

364
00:19:10.600 --> 00:19:13.500
So in here we send the pink packets

365
00:19:13.500 --> 00:19:18.500
 with with the payload size 1472

366
00:19:16.500 --> 00:19:19.900
 and

367
00:19:21.400 --> 00:19:25.200
With this payload, we have sent some pink

368
00:19:24.200 --> 00:19:27.200
 packets here. And now let's look

369
00:19:27.200 --> 00:19:29.600
 at these packets in Wireshark.

370
00:19:30.200 --> 00:19:33.400
You can see in here for sending this

371
00:19:33.400 --> 00:19:36.100
 packets. This pink packets. There is

372
00:19:36.100 --> 00:19:39.600
 no need for IP fragmentation. And there

373
00:19:39.600 --> 00:19:43.100
 is no any IP fragment any

374
00:19:42.100 --> 00:19:46.500
 IP fragments in here. Each packets

375
00:19:45.500 --> 00:19:48.300
 is is a single

376
00:19:48.300 --> 00:19:51.400
 pink equal pink

377
00:19:51.400 --> 00:19:55.300
 pack each one each one of them as a

378
00:19:55.300 --> 00:19:58.200
 single pack packet as you can see, there is

379
00:19:58.200 --> 00:20:00.000
 no IP fragments.

380
00:20:00.900 --> 00:20:05.000
Each one of them is single request

381
00:20:03.400 --> 00:20:06.800
 or reply a

382
00:20:06.800 --> 00:20:07.400
 pink pack.

383
00:20:08.100 --> 00:20:11.400
There are no fragments and as you

384
00:20:11.400 --> 00:20:15.600
 can see the pink packets are being sent as single

385
00:20:14.600 --> 00:20:18.300
 packets again because in

386
00:20:17.300 --> 00:20:20.400
 here when we subtract the

387
00:20:20.400 --> 00:20:23.400
 ethernet header size, which is 14 bites.

388
00:20:23.400 --> 00:20:27.300
 We have we have a 1500

389
00:20:26.300 --> 00:20:29.900
 bytes as data as payload

390
00:20:29.900 --> 00:20:34.000
 data and it is equal to MTU size.

391
00:20:33.500 --> 00:20:36.100
 So for this reason, there is

392
00:20:36.100 --> 00:20:39.400
 no need for fragmentation or IP fragmentation,

393
00:20:39.400 --> 00:20:42.700
 even if the increase the payload size

394
00:20:42.700 --> 00:20:45.200
 adding only one byte.

395
00:20:45.900 --> 00:20:49.000
To this payload size again. We

396
00:20:48.100 --> 00:20:51.600
 need IP fragmentation. It means

397
00:20:51.600 --> 00:20:51.900
 that.

398
00:20:53.500 --> 00:20:54.900
Now, let's look at this.

399
00:20:56.300 --> 00:20:58.700
the next pink packet payload

400
00:21:03.500 --> 00:21:06.600
Okay, let's we have increased the

401
00:21:06.600 --> 00:21:10.000
 data payload by only a

402
00:21:09.300 --> 00:21:13.000
 one bite and we have changed the payload

403
00:21:12.200 --> 00:21:17.400
 size from 1470 to

404
00:21:16.400 --> 00:21:20.500
 to the payload size

405
00:21:20.500 --> 00:21:24.000
 1473. So

406
00:21:23.400 --> 00:21:26.900
 we have added only one byte

407
00:21:26.900 --> 00:21:28.300
 to the payload size.

408
00:21:29.200 --> 00:21:32.700
And in this situation when we

409
00:21:32.700 --> 00:21:35.600
 look at the package associated

410
00:21:35.600 --> 00:21:36.900
 with this pink command.

411
00:21:37.600 --> 00:21:41.800
The click on the packet the

412
00:21:40.800 --> 00:21:44.100
 packet 57 we

413
00:21:43.100 --> 00:21:46.200
 have seen the fragments in

414
00:21:46.200 --> 00:21:48.500
 here for this pink packets.

415
00:21:49.900 --> 00:21:50.100
and

416
00:21:52.300 --> 00:21:55.400
look at this first fragment details.

417
00:21:56.600 --> 00:21:58.900
the packet the 57

418
00:22:00.200 --> 00:22:04.200
So this fragment is first fragment has the

419
00:22:03.200 --> 00:22:08.200
 payload sides as 1480 bytes

420
00:22:08.200 --> 00:22:11.100
 and on the next packet.

421
00:22:12.500 --> 00:22:16.300
We have seen the other the another

422
00:22:15.300 --> 00:22:19.100
 fragment payload size

423
00:22:19.100 --> 00:22:21.900
 in here as one byte.

424
00:22:22.400 --> 00:22:25.600
And the extra one byte is sent as

425
00:22:25.600 --> 00:22:27.400
 the second fragment as you can see.

426
00:22:29.500 --> 00:22:32.600
The extra one byte is sent as

427
00:22:32.600 --> 00:22:35.600
 the second fragment. So we

428
00:22:35.600 --> 00:22:38.400
 have needed the IP fragmentation for only this

429
00:22:38.400 --> 00:22:41.600
 extra one byte. Okay. Now let's look

430
00:22:41.600 --> 00:22:44.200
 at what happens when we try to send the

431
00:22:44.200 --> 00:22:47.900
 packets, which is larger than MTU without fragmentation.

432
00:22:53.200 --> 00:22:57.600
To do this, you know, we should set the don't fragment

433
00:22:57.600 --> 00:23:01.100
 speed and in order to set the don't

434
00:23:00.100 --> 00:23:04.500
 fragment speed to one to

435
00:23:03.500 --> 00:23:07.000
 one value as value.

436
00:23:06.600 --> 00:23:09.300
 We have set the

437
00:23:09.300 --> 00:23:13.500
 don't fragment speed to one we

438
00:23:12.500 --> 00:23:15.600
 add in order to in order

439
00:23:15.600 --> 00:23:18.400
 to in order to set the don't

440
00:23:18.400 --> 00:23:22.700
 fragment speed be at the heapon FC

441
00:23:22.700 --> 00:23:25.500
 which into pink command as like

442
00:23:25.500 --> 00:23:25.800
 here.

443
00:23:26.800 --> 00:23:27.500
You can see.

444
00:23:28.200 --> 00:23:31.100
So and but this time.

445
00:23:33.600 --> 00:23:36.500
But this time when we

446
00:23:36.500 --> 00:23:39.800
 try to Scientific packets by this

447
00:23:39.800 --> 00:23:42.800
 pink command, we are receiving returns as

448
00:23:42.800 --> 00:23:46.500
 packets needs to be fragmented to

449
00:23:45.500 --> 00:23:48.800
 be fragmented. But if said

450
00:23:49.300 --> 00:23:52.200
so we couldn't have sent the package without

451
00:23:52.200 --> 00:23:52.900
 fragmentation.

452
00:23:53.900 --> 00:23:56.700
Because the packet size exceeded the

453
00:23:56.700 --> 00:23:59.100
 MTU value to sum up

454
00:23:59.100 --> 00:24:02.900
 we can call this packet tuning process as as

455
00:24:02.900 --> 00:24:05.400
 the path MTU Discovery and

456
00:24:05.400 --> 00:24:09.000
 you can also perform such a pink traffic to understand

457
00:24:08.800 --> 00:24:11.300
 the pet M2 Discovery process.

458
00:24:11.900 --> 00:24:12.900
in addition to this

459
00:24:14.200 --> 00:24:18.500
You can look for icmp warning message

460
00:24:18.500 --> 00:24:21.600
 as fragmentation needed and they

461
00:24:21.600 --> 00:24:24.900
 have set the messages and observe the

462
00:24:24.900 --> 00:24:27.900
 next up and you field in

463
00:24:27.900 --> 00:24:30.600
 the packet details in your traffic. So you

464
00:24:30.600 --> 00:24:33.400
 can see such as

465
00:24:33.400 --> 00:24:37.100
 this type this type

466
00:24:36.100 --> 00:24:40.100
 of warning messages in your icmp

467
00:24:39.100 --> 00:24:43.100
 traffic and now let's discuss

468
00:24:42.100 --> 00:24:45.700
 the most important points once

469
00:24:45.700 --> 00:24:46.100
 more.

470
00:24:48.100 --> 00:24:51.600
In a real traffic over the Internet imagine a

471
00:24:51.600 --> 00:24:55.600
 network environment which includes some intermediary devices

472
00:24:54.600 --> 00:24:59.200
 such as rotors firewalls van

473
00:24:58.200 --> 00:25:00.400
 impact is transmitted.

474
00:25:01.700 --> 00:25:04.400
The sender sets the

475
00:25:04.400 --> 00:25:07.400
 packets don't fragment the fit in the IP

476
00:25:07.400 --> 00:25:07.800
 header.

477
00:25:08.600 --> 00:25:11.700
So and our pivot will have a

478
00:25:11.700 --> 00:25:12.600
 TCP heater.

479
00:25:13.300 --> 00:25:16.600
And TCP level segment data in

480
00:25:16.600 --> 00:25:17.800
 suitable size.

481
00:25:19.200 --> 00:25:22.800
So and our payload will have a

482
00:25:22.800 --> 00:25:23.600
 TCP heater.

483
00:25:24.100 --> 00:25:27.400
TCP will segment the data in suitable sizes.

484
00:25:28.100 --> 00:25:31.700
And the DF bit indicates that

485
00:25:31.700 --> 00:25:35.000
 the packet shouldn't be fragmented that a

486
00:25:34.200 --> 00:25:37.300
 vanity packet reaches Arrow a router

487
00:25:37.300 --> 00:25:40.100
 that has a smaller ampere than the packet size

488
00:25:40.100 --> 00:25:44.500
 the routers hands and icmp message as fragmentation

489
00:25:43.500 --> 00:25:47.000
 needed and the set message

490
00:25:46.200 --> 00:25:48.100
 back to the sender.

491
00:25:48.600 --> 00:25:52.000
Or this message also will contain the MTU

492
00:25:51.200 --> 00:25:54.200
 of the next up in the network.

493
00:25:54.900 --> 00:25:55.200
and

494
00:25:56.600 --> 00:25:59.800
so the path MTU Discovery

495
00:25:59.800 --> 00:26:03.000
 process will perform dynamically by these

496
00:26:02.500 --> 00:26:04.700
 devices such as routers.

497
00:26:05.300 --> 00:26:08.500
But to do this, first of all, the router has

498
00:26:08.500 --> 00:26:11.600
 to be kept has to be capable of doing this

499
00:26:11.600 --> 00:26:14.800
 process, then it can return back the

500
00:26:14.800 --> 00:26:17.500
 empty value of the next hop to the

501
00:26:17.500 --> 00:26:18.900
 packet sander as well.

502
00:26:19.700 --> 00:26:23.100
And so secondly, this MTU

503
00:26:22.100 --> 00:26:25.300
 value is empty your value

504
00:26:25.300 --> 00:26:28.500
 feedback message sent by the router is an

505
00:26:28.500 --> 00:26:29.400
 icmp.

506
00:26:30.200 --> 00:26:34.500
Message so in here therefore the

507
00:26:33.500 --> 00:26:36.600
 endpoint device must also

508
00:26:36.600 --> 00:26:39.500
 allow icmp messages in order to be able

509
00:26:39.500 --> 00:26:42.500
 to receive this feedback from the router.

510
00:26:43.300 --> 00:26:46.900
And because if there is an entire military device such as

511
00:26:46.900 --> 00:26:50.400
 by by such as firewalls, which

512
00:26:49.400 --> 00:26:52.200
 prevents icmp messages

513
00:26:52.200 --> 00:26:55.900
 and the end point cannot receive

514
00:26:55.900 --> 00:26:57.000
 the feedback.

515
00:26:57.700 --> 00:27:00.700
So and in case of cannot receive

516
00:27:00.700 --> 00:27:03.300
 this feedback about MTU by

517
00:27:03.300 --> 00:27:06.900
 endpoint, it cannot reduce or arrange

518
00:27:06.900 --> 00:27:07.700
 the packet size.

519
00:27:09.200 --> 00:27:12.800
So if there is if there is no prevention by

520
00:27:12.800 --> 00:27:16.700
 some devices such as firewalls descender

521
00:27:15.700 --> 00:27:18.200
 turned down reduce the size

522
00:27:18.200 --> 00:27:21.300
 of its packets to avoid fragmentation by

523
00:27:21.300 --> 00:27:24.500
 using its smallest MTU along the

524
00:27:24.500 --> 00:27:24.700
 pad.

525
00:27:25.400 --> 00:27:28.700
And note that today the pet

526
00:27:28.700 --> 00:27:31.700
 M2 Discovery is available as default

527
00:27:31.700 --> 00:27:34.600
 in in almost all most modern

528
00:27:34.600 --> 00:27:37.800
 tcp/ip implementations and

529
00:27:37.800 --> 00:27:40.600
 it is required that your five

530
00:27:40.600 --> 00:27:43.800
 firewalls or packet filtering devices. Don't prevent

531
00:27:43.800 --> 00:27:46.600
 the icmp pattern you

532
00:27:46.600 --> 00:27:50.800
 discover messages and sending host sets.

533
00:27:49.800 --> 00:27:52.400
 They don't fragment the FP

534
00:27:52.400 --> 00:27:53.800
 in the IP theater.

535
00:27:54.400 --> 00:27:57.600
The packet is too large to be a transmitted toward

536
00:27:57.600 --> 00:28:00.700
 the network without fragmentation. It will

537
00:28:00.700 --> 00:28:03.600
 be dropped by a network device along the

538
00:28:03.600 --> 00:28:06.600
 path. The network device will send back

539
00:28:06.600 --> 00:28:09.200
 and and icmp message.

540
00:28:10.100 --> 00:28:13.500
Indicating that the packet was dropped to

541
00:28:13.500 --> 00:28:16.500
 due to due to fragmentation and

542
00:28:16.500 --> 00:28:19.600
 that is smaller packet size is required.

543
00:28:20.600 --> 00:28:24.600
The sanding cost receives the icmp

544
00:28:23.600 --> 00:28:27.500
 message and reduces the

545
00:28:26.500 --> 00:28:29.100
 size of its packets to the

546
00:28:29.100 --> 00:28:31.100
 suggested size.

547
00:28:31.800 --> 00:28:35.500
And the sanding host continues

548
00:28:34.500 --> 00:28:37.600
 to use the new MTU for

549
00:28:37.600 --> 00:28:40.800
 feature Transmissions or that Network at

550
00:28:40.800 --> 00:28:44.400
 if the network path changed the

551
00:28:43.400 --> 00:28:46.200
 pad and to you the pad

552
00:28:46.200 --> 00:28:48.300
 MTU Discovery process will be repeated.

553
00:28:48.900 --> 00:28:51.600
For example, if a network link with

554
00:28:51.600 --> 00:28:54.000
 a lower MTU is added to the

555
00:28:54.100 --> 00:28:57.400
 pad the sander will receive a new

556
00:28:57.400 --> 00:29:01.300
 icmp message indicating the new lower

557
00:29:00.300 --> 00:29:03.500
 MTU or the new

558
00:29:03.500 --> 00:29:06.200
 MTU value and it will

559
00:29:06.200 --> 00:29:09.600
 adjust its packet size accordingly.

560
00:29:10.300 --> 00:29:13.200
Top add M2 Discovery can be used

561
00:29:13.200 --> 00:29:16.900
 to increase the network performance and cpeed

562
00:29:16.900 --> 00:29:19.400
 by allowing access to be transmitted

563
00:29:19.400 --> 00:29:22.600
 at the maximum possible size without fragmentation.

564
00:29:23.400 --> 00:29:25.400
When packets are fragmented.

565
00:29:26.600 --> 00:29:29.800
They must be reassembled at destination which

566
00:29:29.800 --> 00:29:33.000
 can cause delays and increased overhead

567
00:29:32.800 --> 00:29:35.400
 by using pattern you

568
00:29:35.400 --> 00:29:38.300
 Discovery the standard can determine the

569
00:29:38.300 --> 00:29:41.700
 smallest mpu along the

570
00:29:41.700 --> 00:29:44.600
 path to the destination and sand packets that are

571
00:29:44.600 --> 00:29:48.200
 small enough to avoid fragmentation. This

572
00:29:47.200 --> 00:29:50.900
 can result in Faster data

573
00:29:50.900 --> 00:29:52.900
 transfer and lower overhead.

574
00:29:53.600 --> 00:29:56.600
It's worth noting that had empty Discovery

575
00:29:56.600 --> 00:29:59.400
 could be affected by some network devices that

576
00:29:59.400 --> 00:30:02.800
 block icmp error messages. This could

577
00:30:02.800 --> 00:30:05.800
 cause packets to be dropped instead of being fragmented.

578
00:30:05.800 --> 00:30:09.500
 This could lead to connectivity problems

579
00:30:08.500 --> 00:30:11.400
 in your net.

580
00:30:12.200 --> 00:30:15.900
Also pet and you Discovery isn't a standard

581
00:30:15.900 --> 00:30:18.600
 protocol some network

582
00:30:18.600 --> 00:30:21.200
 devices may not support it in your

583
00:30:21.200 --> 00:30:26.000
 over your network at or in

584
00:30:24.400 --> 00:30:27.100
 your network environment.

585
00:30:28.200 --> 00:30:31.100
Now let's talk in more detail about the benefits of

586
00:30:31.100 --> 00:30:34.900
 avoiding IP fragmentation with

587
00:30:34.900 --> 00:30:36.600
 that M2 discovery.

588
00:30:41.800 --> 00:30:44.200
So now we will talk about the advantages of

589
00:30:44.200 --> 00:30:46.000
 the pet M2 discovery.

590
00:30:46.600 --> 00:30:50.200
And the first one is improved efficiency.

591
00:30:50.900 --> 00:30:53.200
A by sounding packets that are small

592
00:30:53.200 --> 00:30:56.800
 enough to avoid fragmentation. You can improve the

593
00:30:56.800 --> 00:30:59.500
 efficiency of data transfer this is

594
00:30:59.500 --> 00:31:03.900
 because the packets will not need to be reassembled a

595
00:31:03.900 --> 00:31:07.000
 destination which can save time and reduce

596
00:31:06.000 --> 00:31:08.200
 delays.

597
00:31:08.900 --> 00:31:11.900
So the second one is reduced

598
00:31:11.900 --> 00:31:14.600
 overhead and band pickets are

599
00:31:14.600 --> 00:31:18.400
 fragmented. They must include additional hidden

600
00:31:17.400 --> 00:31:21.600
 information such as additional IP

601
00:31:20.600 --> 00:31:23.700
 heater and which increases

602
00:31:23.700 --> 00:31:26.900
 the size of the packet and increases

603
00:31:26.900 --> 00:31:29.900
 overhead by avoiding fragmentation.

604
00:31:29.900 --> 00:31:33.100
 You can reduce the overhead overhead

605
00:31:32.100 --> 00:31:35.700
 and improve the overall performance of

606
00:31:35.700 --> 00:31:36.300
 the network.

607
00:31:38.100 --> 00:31:41.800
But the third one is better reliability and

608
00:31:41.800 --> 00:31:44.700
 when packets are fragmented, they

609
00:31:44.700 --> 00:31:47.200
 can be lost in transit it can cause

610
00:31:47.200 --> 00:31:51.100
 the reassembling process to fail by avoiding

611
00:31:50.100 --> 00:31:53.400
 fragmentation. You can improve the

612
00:31:53.400 --> 00:31:56.900
 reliability of the network and ensure

613
00:31:56.900 --> 00:32:00.000
 that a data is transmitted correctly and

614
00:31:59.500 --> 00:32:02.800
 the other advantage of the ATM to

615
00:32:02.800 --> 00:32:06.500
 you Discovery is better security fragmentation can

616
00:32:06.500 --> 00:32:10.400
 be exploited in various types

617
00:32:09.400 --> 00:32:12.200
 of attacks such as

618
00:32:12.200 --> 00:32:15.700
 fragmentation attacks, which can be used to evade network

619
00:32:15.700 --> 00:32:18.300
 security devices or call the

620
00:32:18.300 --> 00:32:21.700
 denial of service those attack by

621
00:32:21.700 --> 00:32:24.100
 avoiding fragmentation. You can reduce

622
00:32:24.100 --> 00:32:26.100
 the risk of these types of attacks.

623
00:32:27.200 --> 00:32:31.200
And the other one is better quality of service pet empty

624
00:32:30.200 --> 00:32:34.200
 Discovery can help ensure that important traffic

625
00:32:33.200 --> 00:32:36.400
 such as real-time voice and video can

626
00:32:36.400 --> 00:32:39.600
 be transmitted at the highest possible quality

627
00:32:39.600 --> 00:32:41.700
 by avoiding fragmentation.

628
00:32:42.400 --> 00:32:45.600
So it's worth noting that pet M2 Discovery

629
00:32:45.600 --> 00:32:48.700
 works best when it is able to dynamically adjust

630
00:32:48.700 --> 00:32:51.500
 the packet size to the smallest mu along

631
00:32:51.500 --> 00:32:52.000
 the pad.

632
00:32:52.600 --> 00:32:55.900
So it is also important to keep in mind that there

633
00:32:55.900 --> 00:32:58.500
 could be other factors that could affect the

634
00:32:58.500 --> 00:33:02.000
 network performance such as Network congestion and

635
00:33:01.300 --> 00:33:04.400
 it will be best to

636
00:33:04.400 --> 00:33:07.800
 monitor the network performance regularly and

637
00:33:07.800 --> 00:33:10.800
 troubleshoot any issues that may arise.

638
00:33:11.400 --> 00:33:14.600
Now I want to talk about how to determine the

639
00:33:14.600 --> 00:33:17.300
 causes of slow Network in summary.

640
00:33:19.200 --> 00:33:22.800
So here are some ways for detecting causes

641
00:33:22.800 --> 00:33:25.400
 in slow networks. And first one

642
00:33:25.400 --> 00:33:28.800
 is monitor the network performance. You

643
00:33:28.800 --> 00:33:31.700
 can use a network monitoring tools

644
00:33:31.700 --> 00:33:34.700
 such as Wireshark capture and analyze Network

645
00:33:34.700 --> 00:33:37.700
 traffic and you can look for patterns and

646
00:33:37.700 --> 00:33:40.700
 anomalies that may indicate problems such

647
00:33:40.700 --> 00:33:44.000
 as I packed those High latency or

648
00:33:43.700 --> 00:33:45.300
 low throughput

649
00:33:46.200 --> 00:33:50.000
And the second one is checking at MTU

650
00:33:49.500 --> 00:33:53.000
 Discovery. You can use Wireshark

651
00:33:52.100 --> 00:33:55.700
 to observe the icmp fragmentation

652
00:33:55.700 --> 00:33:58.900
 needed and we have set messages and look

653
00:33:58.900 --> 00:34:02.300
 for you can look for the next up MTU

654
00:34:01.300 --> 00:34:04.800
 field in the packet details and

655
00:34:04.800 --> 00:34:08.300
 you can compare the next hub MTU

656
00:34:07.300 --> 00:34:10.600
 value with the packet size in order

657
00:34:10.600 --> 00:34:14.200
 to see if packets are being fragmented if packets

658
00:34:13.200 --> 00:34:16.500
 are being fragmented then the cause

659
00:34:16.500 --> 00:34:19.200
 of slow Network could be that the packets

660
00:34:19.200 --> 00:34:22.700
 are being sent at a larger size than the

661
00:34:22.700 --> 00:34:24.900
 maximum transmission unit size of the network.

662
00:34:26.100 --> 00:34:30.300
At the third one is checking for Network congestion. And

663
00:34:29.300 --> 00:34:33.000
 if the network is congested then

664
00:34:32.800 --> 00:34:35.900
 packets may be dropped or delayed

665
00:34:35.900 --> 00:34:38.800
 which can cause slow Network performance.

666
00:34:40.300 --> 00:34:43.200
So the other way is checking for quality of

667
00:34:43.200 --> 00:34:46.900
 service issues can use network monitoring tools

668
00:34:46.900 --> 00:34:49.300
 again, in order to check or quality of

669
00:34:49.300 --> 00:34:52.500
 service issues. For example, if the network

670
00:34:52.500 --> 00:34:55.200
 is arranged for the quality of

671
00:34:55.200 --> 00:34:59.100
 service, but the turf is not being prioritized correctly and

672
00:34:58.100 --> 00:35:01.500
 then it could cause slow Network

673
00:35:01.500 --> 00:35:04.800
 performance for some types of traffic. This

674
00:35:04.800 --> 00:35:07.500
 was one of the most common definitions I

675
00:35:07.500 --> 00:35:10.800
 encountered in the companies. I provided Support Services to

676
00:35:11.400 --> 00:35:14.500
So there were some problems mostly interruptions

677
00:35:14.500 --> 00:35:17.400
 and quality problems in Voiceover IP terrific

678
00:35:17.400 --> 00:35:20.200
 because the quality of service process in

679
00:35:20.200 --> 00:35:23.600
 the network traffic wasn't done correctly or at

680
00:35:23.600 --> 00:35:27.200
 all, and the traffic wasn't a prioritized

681
00:35:26.200 --> 00:35:27.700
 correctly.

682
00:35:28.500 --> 00:35:31.900
So and the other way is checking for network

683
00:35:31.900 --> 00:35:34.600
 security issues such as denial of

684
00:35:34.600 --> 00:35:38.000
 service attacks or other types of malicious traffic.

685
00:35:38.600 --> 00:35:41.700
This could be the cause of slow Network

686
00:35:41.700 --> 00:35:45.300
 performance as well. As you know, and the

687
00:35:44.300 --> 00:35:47.700
 sixth one is checking for Hardware

688
00:35:47.700 --> 00:35:49.500
 or software issues.

689
00:35:50.300 --> 00:35:53.700
You can check for Hardware or software issues such

690
00:35:53.700 --> 00:35:57.900
 as outdated drivers or malfunctioning network

691
00:35:57.900 --> 00:36:01.700
 interfaces or incorrect a

692
00:36:01.700 --> 00:36:04.300
 network configurations. These issues can

693
00:36:04.300 --> 00:36:07.200
 cause a slow Network performance as well.

694
00:36:08.100 --> 00:36:11.600
And usual check for other issues that could

695
00:36:11.600 --> 00:36:14.100
 affect Network performance. So there are

696
00:36:14.100 --> 00:36:17.400
 a variety of other issues that could effect in its

697
00:36:17.400 --> 00:36:20.500
 work performance such as Network topology writing and

698
00:36:20.500 --> 00:36:22.300
 network capacity.

699
00:36:22.900 --> 00:36:26.100
It's important to consider all possible vectors

700
00:36:25.100 --> 00:36:29.100
 when troubleshting solar Network performance process.

701
00:36:28.100 --> 00:36:31.400
 It's worth noting that finding the

702
00:36:31.400 --> 00:36:34.200
 root cause of network issues can be complex and

703
00:36:34.200 --> 00:36:37.300
 time-consuming. It's important to have a

704
00:36:37.300 --> 00:36:41.000
 good understanding of network protocols tools and

705
00:36:40.400 --> 00:36:43.500
 to be prepared to use a

706
00:36:43.500 --> 00:36:46.600
 combination of different techniques to troubleshoot the

707
00:36:46.600 --> 00:36:46.700
 problem.

708
00:36:47.600 --> 00:36:50.100
To sum up head empty Discovery is a

709
00:36:50.100 --> 00:36:53.900
 mechanism used by IP to determine the

710
00:36:53.900 --> 00:36:56.500
 maximum transmission unit to determine

711
00:36:56.500 --> 00:36:59.700
 the MTU along the pad to a

712
00:36:59.700 --> 00:37:03.000
 destination host. It starts by sending a

713
00:37:02.600 --> 00:37:05.900
 packets with the don't fragment bitset in

714
00:37:05.900 --> 00:37:08.800
 the IP heater. And when a

715
00:37:08.800 --> 00:37:11.300
 packet reads a router that is a

716
00:37:11.300 --> 00:37:14.300
 smaller amp to you than the packet size the router sends

717
00:37:14.300 --> 00:37:17.300
 and icmp message which contains the

718
00:37:17.300 --> 00:37:20.400
 warning fragmentation needed and PF set.

719
00:37:21.200 --> 00:37:24.700
To the sender the sander can then reduce the

720
00:37:24.700 --> 00:37:28.100
 size of its packets to avoid fragmentation by

721
00:37:27.100 --> 00:37:30.400
 using the smallest MTU along the

722
00:37:30.400 --> 00:37:30.600
 pad.

723
00:37:31.200 --> 00:37:34.500
And its performed dynamically and fit to

724
00:37:34.500 --> 00:37:38.100
 change in network conditions. It

725
00:37:37.100 --> 00:37:41.300
 allows the sender to discover the smallest MTU

726
00:37:40.300 --> 00:37:43.400
 along the pad to destination host

727
00:37:43.400 --> 00:37:46.300
 and adjust the packet size

728
00:37:46.300 --> 00:37:47.000
 accordingly.

729
00:37:48.700 --> 00:37:51.700
So that's all about the pattern you Discovery.

730
00:37:51.700 --> 00:37:52.700
 See you on the next video.
