WEBVTT - This file was automatically generated by VIMEO

0
00:00:10.200 --> 00:00:13.400
Hello everyone in this section. We will look at how to

1
00:00:13.400 --> 00:00:16.400
 capture the network traffic and how to make

2
00:00:16.400 --> 00:00:17.300
 analysis.

3
00:00:18.900 --> 00:00:22.000
In this lesson, we will investigate the different capturing

4
00:00:21.400 --> 00:00:23.900
 techniques or Wireshark.

5
00:00:25.200 --> 00:00:26.400
Now let's begin.

6
00:00:31.300 --> 00:00:33.800
At the beginning click on the capture options button.

7
00:00:35.800 --> 00:00:37.700
And there are three main tabs.

8
00:00:39.300 --> 00:00:46.600
You in

9
00:00:44.600 --> 00:00:47.500
 the input tab we

10
00:00:47.500 --> 00:00:50.900
 can select which interface we are going to sniff the

11
00:00:50.900 --> 00:00:51.200
 traffic.

12
00:00:51.800 --> 00:00:55.100
Now let's pay attention the promiscues mode.

13
00:00:56.500 --> 00:00:57.800
As you see in here.

14
00:00:59.600 --> 00:01:03.100
Promiscues mode is a setting that allows the

15
00:01:02.100 --> 00:01:05.600
 network interface to capture all packets that

16
00:01:05.600 --> 00:01:08.800
 pass through the network rather than just packets that

17
00:01:08.800 --> 00:01:10.200
 are others to the device.

18
00:01:11.100 --> 00:01:15.000
This can be useful for capturing and analyzing

19
00:01:14.500 --> 00:01:17.200
 Network traffic in a variety of

20
00:01:17.200 --> 00:01:21.400
 situations such as troubleshdink performing security

21
00:01:21.400 --> 00:01:23.800
 assessments or net or analyzing Network.

22
00:01:24.900 --> 00:01:27.600
and to enable promiscuous mode

23
00:01:27.600 --> 00:01:28.500
 in Wireshark

24
00:01:29.800 --> 00:01:32.700
You can select the interface firstly you

25
00:01:32.700 --> 00:01:36.300
 want to use for packet capture

26
00:01:36.300 --> 00:01:39.700
 in the interface list window in the

27
00:01:39.700 --> 00:01:42.200
 input in the input Pane and I am

28
00:01:42.200 --> 00:01:46.700
 selecting the Wi-Fi interface because I am using actively this

29
00:01:45.700 --> 00:01:47.600
 interface.

30
00:01:48.800 --> 00:01:52.100
As you see in here for all the other interfaces

31
00:01:51.100 --> 00:01:54.400
 the promiscuous mode

32
00:01:54.400 --> 00:01:55.600
 has been selected.

33
00:01:56.500 --> 00:02:00.000
And I want to uncheck these options for

34
00:01:59.300 --> 00:02:01.400
 the other interfaces.

35
00:02:02.400 --> 00:02:05.300
Because I don't want to use the

36
00:02:05.300 --> 00:02:06.300
 promise Keys mode.

37
00:02:08.200 --> 00:02:11.400
For the other interfaces and I just

38
00:02:11.400 --> 00:02:14.900
 want to choose the promiscuous mode

39
00:02:14.900 --> 00:02:17.100
 for the Wi-Fi interface because

40
00:02:17.100 --> 00:02:21.100
 I want to capture on this interface the

41
00:02:20.100 --> 00:02:23.200
 network traffic.

42
00:02:24.600 --> 00:02:27.600
Once promiscules mode is enabled Wireshark will

43
00:02:27.600 --> 00:02:31.400
 capture all packets that pass through the network regardless

44
00:02:30.400 --> 00:02:33.900
 of whether they are addressed

45
00:02:33.900 --> 00:02:36.500
 to the device or not. If you

46
00:02:36.500 --> 00:02:39.800
 check the enable promises mod on all interfaces.

47
00:02:41.200 --> 00:02:44.600
Again, all of the other for all

48
00:02:44.600 --> 00:02:47.300
 of the other interfaces promiscules mode

49
00:02:47.300 --> 00:02:48.700
 is again active.

50
00:02:49.800 --> 00:02:52.700
As you see in here, it turns

51
00:02:52.700 --> 00:02:56.000
 to promiscues mode in active

52
00:02:55.700 --> 00:02:58.300
 again. So if you

53
00:02:58.300 --> 00:03:01.400
 aren't checked this option, the promiscues mode

54
00:03:01.400 --> 00:03:04.600
 is now unavailable for the all

55
00:03:04.600 --> 00:03:07.500
 of the other interfaces all around other

56
00:03:07.500 --> 00:03:08.100
 interfaces.

57
00:03:09.200 --> 00:03:12.500
And I want to check the promiscue smart

58
00:03:12.500 --> 00:03:14.700
 for the entire face five.

59
00:03:15.500 --> 00:03:18.500
Again, because I want to capture the packets on

60
00:03:18.500 --> 00:03:21.700
 the Wi-Fi interface and I want

61
00:03:21.700 --> 00:03:24.800
 to enable the promiscues mode for this

62
00:03:24.800 --> 00:03:25.600
 interface.

63
00:03:26.500 --> 00:03:29.500
And it's important to note that

64
00:03:29.500 --> 00:03:33.700
 promiscues mode can significantly increase the

65
00:03:33.700 --> 00:03:37.000
 amount of traffic captured by Wireshark, and

66
00:03:36.500 --> 00:03:39.600
 it may also expose the device to

67
00:03:39.600 --> 00:03:42.200
 a greater risk of security vulnerabilities.

68
00:03:43.300 --> 00:03:46.600
So as a result, it's generally recommended to

69
00:03:46.600 --> 00:03:49.400
 use promiscues mode only when necessary

70
00:03:49.400 --> 00:03:52.300
 and to disable it when it is no

71
00:03:52.300 --> 00:03:55.600
 longer needed. How can we capture the live

72
00:03:55.600 --> 00:03:56.900
 traffic on our Network?

73
00:03:58.100 --> 00:04:01.300
After we have chosen the entire face that we want

74
00:04:01.300 --> 00:04:04.200
 to capture the network traffic. We will

75
00:04:04.200 --> 00:04:07.000
 just click on the start button.

76
00:04:12.300 --> 00:04:15.800
Now the packets are streaming on our

77
00:04:15.800 --> 00:04:16.500
 pane.

78
00:04:17.100 --> 00:04:19.900
We are capturing some packets on our Network.

79
00:04:20.700 --> 00:04:22.900
on our Wi-Fi interface

80
00:04:26.600 --> 00:04:30.600
and you can see the notification capturing from

81
00:04:30.600 --> 00:04:33.300
 Wi-Fi because we are

82
00:04:33.300 --> 00:04:37.100
 capturing the packets on the Wi-Fi interface now.

83
00:04:41.200 --> 00:04:42.300
And that's enough for us.

84
00:04:43.500 --> 00:04:44.400
for now

85
00:04:47.200 --> 00:04:50.300
when you have finished to capture the traffic, you

86
00:04:50.300 --> 00:04:54.300
 can click on the stop capturing packets

87
00:04:53.300 --> 00:04:54.500
 button.

88
00:04:57.900 --> 00:05:00.600
If you look at the status bar, you can

89
00:05:00.600 --> 00:05:03.800
 see the number of packets and we have

90
00:05:03.800 --> 00:05:05.900
 now 59 packets.

91
00:05:07.200 --> 00:05:07.900
currently

92
00:05:13.100 --> 00:05:16.600
after capturing process you can save this

93
00:05:16.600 --> 00:05:19.400
 file as a capturing file.

94
00:05:20.700 --> 00:05:22.700
as you know say

95
00:05:25.200 --> 00:05:28.500
and then you can enter a name to the

96
00:05:28.500 --> 00:05:29.000
 file.

97
00:05:29.600 --> 00:05:32.200
After giving the name to the

98
00:05:32.200 --> 00:05:35.300
 file, you can click on the save button, but I

99
00:05:35.300 --> 00:05:38.100
 don't want to save this file for now.

100
00:05:38.900 --> 00:05:41.700
So I am shutting down the

101
00:05:41.700 --> 00:05:42.200
 window.

102
00:05:43.200 --> 00:05:46.700
And now we want to use a capture filter

103
00:05:46.700 --> 00:05:49.300
 during capturing our packets on

104
00:05:49.300 --> 00:05:53.100
 our Network. So I'm shutting this file.

105
00:05:54.100 --> 00:05:57.300
And again, I want to go to

106
00:05:57.300 --> 00:05:58.800
 the capture options.

107
00:06:00.500 --> 00:06:03.300
And in here as you can see

108
00:06:03.300 --> 00:06:06.900
 capture filter for selected interfaces.

109
00:06:08.400 --> 00:06:11.200
And you can enter a capture filter

110
00:06:11.200 --> 00:06:11.600
 in here.

111
00:06:12.600 --> 00:06:15.400
So you want to create a capture filter

112
00:06:15.400 --> 00:06:18.200
 to only show us traffic sourcing from

113
00:06:18.200 --> 00:06:21.700
 or distant to

114
00:06:21.700 --> 00:06:24.400
 our IP address personally. I

115
00:06:24.400 --> 00:06:26.400
 want to see my IP address.

116
00:06:47.900 --> 00:06:50.600
so as you can see, my IP address

117
00:06:50.600 --> 00:06:51.000
 is

118
00:06:51.800 --> 00:06:54.600
In here, and I want to use

119
00:06:54.600 --> 00:06:56.900
 this IP address as a filter.

120
00:07:04.200 --> 00:07:06.300
Now I am typing my filtering code.

121
00:07:10.600 --> 00:07:12.100
And click on the start.

122
00:07:20.800 --> 00:07:23.700
Now we will see the only packets from

123
00:07:23.700 --> 00:07:26.000
 the this IP address.

124
00:07:29.700 --> 00:07:33.000
Only the packets sourcing from

125
00:07:32.400 --> 00:07:35.400
 this other this address and

126
00:07:35.400 --> 00:07:38.200
 distance to this IP address.

127
00:07:40.800 --> 00:07:43.400
There is no another IP address as a

128
00:07:43.400 --> 00:07:46.300
 host IP address only this one.

129
00:07:47.400 --> 00:07:49.900
only this IP address as you can see

130
00:07:52.700 --> 00:07:55.400
So now we can stop the

131
00:07:55.400 --> 00:07:58.900
 capturing option capturing process

132
00:07:58.900 --> 00:08:00.800
 and we have stopped it.

133
00:08:01.900 --> 00:08:06.100
And we have 126 packets

134
00:08:05.100 --> 00:08:06.200
 now.

135
00:08:06.800 --> 00:08:09.200
As you can see in status bar.

136
00:08:11.200 --> 00:08:13.800
And we can close this capture file without saving.

137
00:08:16.700 --> 00:08:17.500
continue without saving

138
00:08:18.900 --> 00:08:21.600
and I want to close this

139
00:08:21.600 --> 00:08:21.900
 option.

140
00:08:22.600 --> 00:08:22.900
as well

141
00:08:24.700 --> 00:08:27.400
Is then another method to capture a

142
00:08:27.400 --> 00:08:30.400
 network traffic we can take a file we

143
00:08:30.400 --> 00:08:33.300
 can take a capturing file that we

144
00:08:33.300 --> 00:08:37.300
 have captured before and to

145
00:08:36.300 --> 00:08:39.500
 do this we can go to

146
00:08:39.500 --> 00:08:43.400
 the file menu and open option

147
00:08:42.400 --> 00:08:44.100
 click on.

148
00:08:44.700 --> 00:08:47.200
For example, I want to open the my first

149
00:08:47.200 --> 00:08:48.000
 chip file.

150
00:08:50.200 --> 00:08:51.700
And click on the open.

151
00:08:53.200 --> 00:08:56.500
Then you can have a network

152
00:08:56.500 --> 00:08:57.000
 traffic.

153
00:08:57.900 --> 00:09:01.200
That you have captured captured

154
00:09:00.200 --> 00:09:04.000
 before and third option

155
00:09:03.100 --> 00:09:06.400
 to have a capturing

156
00:09:06.400 --> 00:09:09.300
 file to have some packets on

157
00:09:09.300 --> 00:09:13.000
 the network is the capturing is

158
00:09:12.600 --> 00:09:15.300
 capturing from the common line.

159
00:09:18.500 --> 00:09:21.100
And through this we will open the comment line.

160
00:09:22.600 --> 00:09:25.700
Firstly I want to close this file

161
00:09:25.700 --> 00:09:26.200
 again.

162
00:09:27.500 --> 00:09:28.900
Close this capture file.

163
00:09:30.400 --> 00:09:34.100
And when you are opening the comment

164
00:09:33.100 --> 00:09:36.600
 line in the windows to capturing from

165
00:09:36.600 --> 00:09:39.200
 the command line and you should be

166
00:09:39.200 --> 00:09:43.500
 the administrator. So you should run the command

167
00:09:42.500 --> 00:09:46.600
 line as the administrator. Otherwise,

168
00:09:45.600 --> 00:09:48.800
 you will get an permission

169
00:09:48.800 --> 00:09:50.000
 errors and

170
00:09:52.200 --> 00:09:54.600
So when we are opening the command line.

171
00:09:58.400 --> 00:10:01.300
first right click on the command prompt

172
00:10:02.400 --> 00:10:05.000
and run as administrators.

173
00:10:11.500 --> 00:10:14.200
Now as you can see, we have opened the common

174
00:10:14.200 --> 00:10:16.100
 line as administrator.

175
00:10:16.800 --> 00:10:18.100
That is important to us.

176
00:10:19.700 --> 00:10:23.200
Now navigate to directory a Wireshark

177
00:10:22.200 --> 00:10:24.500
 has installed

178
00:10:26.700 --> 00:10:29.400
I want to go to my directory.

179
00:10:47.700 --> 00:10:50.300
Then we will follow the comment to start

180
00:10:50.300 --> 00:10:54.100
 capturing packets with t-shark. T-shark

181
00:10:53.100 --> 00:10:57.100
 is used to capture the network

182
00:10:56.100 --> 00:10:59.500
 packets on the common line.

183
00:11:00.900 --> 00:11:03.000
as an attribute for the Wireshark

184
00:11:03.700 --> 00:11:06.200
and people use the t-shark.

185
00:11:29.500 --> 00:11:33.000
So now I have written the row format

186
00:11:32.300 --> 00:11:35.800
 for the T-shirt comment. And

187
00:11:35.800 --> 00:11:38.500
 in this comment, we will

188
00:11:38.500 --> 00:11:42.100
 we will replace the entire face part

189
00:11:41.100 --> 00:11:44.700
 as our interface and

190
00:11:44.700 --> 00:11:47.600
 we want to capture the traffic on

191
00:11:47.600 --> 00:11:50.500
 Wi-Fi interface. So

192
00:11:51.400 --> 00:11:54.100
I will write in here as an

193
00:11:54.100 --> 00:11:55.700
 entire face Wi-Fi.

194
00:12:00.500 --> 00:12:03.500
And you should pay attention when you are writing the

195
00:12:03.500 --> 00:12:06.300
 name of the interface because it is

196
00:12:06.300 --> 00:12:07.500
 case sensitive.

197
00:12:08.700 --> 00:12:11.900
So it is important whether the letter

198
00:12:11.900 --> 00:12:15.200
 will be upper or lowercase and

199
00:12:16.500 --> 00:12:17.700
I want to replace.

200
00:12:18.700 --> 00:12:20.700
my output file name

201
00:12:25.100 --> 00:12:29.600
And in here you will specify the location of your file that

202
00:12:28.600 --> 00:12:31.200
 you will save your

203
00:12:31.200 --> 00:12:32.500
 network packets.

204
00:12:33.800 --> 00:12:35.800
And I want to write my location.

205
00:12:49.100 --> 00:12:51.300
So I'm giving a name to my file.

206
00:12:56.700 --> 00:12:58.300
new t-shirt cap

207
00:12:59.400 --> 00:13:00.100
and then

208
00:13:00.800 --> 00:13:03.200
you will specify the extension of your

209
00:13:03.200 --> 00:13:03.700
 file.

210
00:13:06.600 --> 00:13:10.400
And now if we press the enter we

211
00:13:09.400 --> 00:13:13.000
 will start to capturing the network

212
00:13:12.000 --> 00:13:14.100
 packets.

213
00:13:14.900 --> 00:13:17.400
And press the button enter.

214
00:13:24.100 --> 00:13:27.400
Okay now press Ctrl C to

215
00:13:27.400 --> 00:13:30.200
 stop the capture and save the packets to

216
00:13:30.200 --> 00:13:31.200
 the output file.

217
00:13:32.100 --> 00:13:34.900
That we have specified before in here.

218
00:13:36.200 --> 00:13:39.100
And I am pressing the buttons DRL and

219
00:13:39.100 --> 00:13:39.700
 C.

220
00:13:44.800 --> 00:13:47.200
Let's open the pickup file that we have created.

221
00:13:56.100 --> 00:13:57.500
And the file is here.

222
00:13:59.300 --> 00:13:59.700
click open

223
00:14:03.400 --> 00:14:07.600
Then we look at the status bar. We can see the package

224
00:14:06.600 --> 00:14:09.300
 number and we have

225
00:14:09.300 --> 00:14:12.000
 56 Network packets.

226
00:14:13.700 --> 00:14:16.800
And we captured these packets

227
00:14:16.800 --> 00:14:19.700
 with the t-shark on the common line.

228
00:14:20.700 --> 00:14:24.000
This was the another way to capturing our

229
00:14:23.300 --> 00:14:25.000
 Network topic.

230
00:14:26.300 --> 00:14:29.100
the last method I'm gonna show you about the

231
00:14:30.700 --> 00:14:31.400
capturing remote

232
00:14:32.200 --> 00:14:35.800
connections capturing about the remote network

233
00:14:35.800 --> 00:14:38.100
 and to do this. We are

234
00:14:38.100 --> 00:14:42.600
 opening again the capture options and in

235
00:14:41.600 --> 00:14:46.300
 here you can see manage interfaces

236
00:14:45.300 --> 00:14:46.700
 option.

237
00:14:47.600 --> 00:14:47.800
so

238
00:14:50.100 --> 00:14:54.100
we are clicking on the managing interfaces and

239
00:14:53.100 --> 00:14:57.300
 you can add the remote interface using

240
00:14:56.300 --> 00:14:58.300
 this button.

241
00:14:58.800 --> 00:15:01.500
Adding button at the remote host and

242
00:15:01.500 --> 00:15:02.900
 its interfaces.

243
00:15:04.300 --> 00:15:05.900
and when we click on the

244
00:15:07.500 --> 00:15:10.600
Remote interface button. You can add your host

245
00:15:10.600 --> 00:15:13.500
 IP address in here,

246
00:15:13.500 --> 00:15:16.600
 then you can add its Port

247
00:15:16.600 --> 00:15:17.400
 information.

248
00:15:18.700 --> 00:15:22.000
And after adding these information you can

249
00:15:21.200 --> 00:15:24.600
 use an authentication with the

250
00:15:24.600 --> 00:15:28.200
 password with the username and password or now

251
00:15:27.200 --> 00:15:29.000
 Authentication.

252
00:15:29.800 --> 00:15:32.500
You can use then you will

253
00:15:32.500 --> 00:15:34.000
 click on the okay.

254
00:15:34.900 --> 00:15:36.500
I didn't enter any information.

255
00:15:38.100 --> 00:15:38.400
and

256
00:15:39.500 --> 00:15:44.000
When add the remote interfaces information you

257
00:15:42.200 --> 00:15:46.400
 will see your remote interface

258
00:15:45.400 --> 00:15:48.800
 in here and you can click

259
00:15:48.800 --> 00:15:52.100
 on button. Okay again, after these

260
00:15:51.100 --> 00:15:54.500
 operations, you will see

261
00:15:54.500 --> 00:15:57.700
 the interface the remote entire face on

262
00:15:57.700 --> 00:15:58.700
 the input window.

263
00:16:00.200 --> 00:16:03.800
And you can capture the packets

264
00:16:03.800 --> 00:16:06.700
 on the remote interface by using this

265
00:16:06.700 --> 00:16:09.800
 way and these are the features of the input pane.

266
00:16:11.800 --> 00:16:14.100
And that's all when we pass

267
00:16:14.100 --> 00:16:17.500
 to the output pane. We can see in here

268
00:16:17.500 --> 00:16:20.600
 a file field and you

269
00:16:20.600 --> 00:16:24.900
 can use a file pad with

270
00:16:23.900 --> 00:16:26.900
 writing directly or

271
00:16:26.900 --> 00:16:29.200
 using the browse button

272
00:16:29.200 --> 00:16:32.800
 and you can choose a pad in here a file.

273
00:16:32.800 --> 00:16:35.200
 You can choose then you can

274
00:16:35.200 --> 00:16:36.400
 click on the say.

275
00:16:38.600 --> 00:16:41.300
To capture to add Paramount file

276
00:16:41.300 --> 00:16:44.900
 you can use this field. You can

277
00:16:44.900 --> 00:16:47.600
 also arrange the output format as

278
00:16:47.600 --> 00:16:50.900
 pcapng or pcap what

279
00:16:50.900 --> 00:16:52.300
 are differences between them?

280
00:16:53.300 --> 00:16:56.800
TCAP is meaning a packet capture.

281
00:16:56.800 --> 00:17:00.500
 I mean pickup is the shortcut that

282
00:16:59.500 --> 00:17:02.400
 packed capture and

283
00:17:02.400 --> 00:17:05.700
 the pcap engine means packet capture

284
00:17:05.700 --> 00:17:06.500
 Next Generation.

285
00:17:07.300 --> 00:17:10.300
And these file extensions are

286
00:17:10.300 --> 00:17:13.400
 bought file formats for storing captured

287
00:17:13.400 --> 00:17:14.200
 Network traffic.

288
00:17:14.800 --> 00:17:17.600
Pcap is the original packet capture format

289
00:17:17.600 --> 00:17:20.600
 while pickup NG is an extension

290
00:17:20.600 --> 00:17:23.400
 of the PCAT format that was developed

291
00:17:23.400 --> 00:17:26.800
 to address some of the limitations of

292
00:17:26.800 --> 00:17:28.200
 the origin of format.

293
00:17:28.800 --> 00:17:32.000
And some of the key difference between pcap and

294
00:17:31.000 --> 00:17:32.900
 pcapng.

295
00:17:33.800 --> 00:17:37.000
Are like this PK files

296
00:17:36.300 --> 00:17:39.600
 are supported by a wide range

297
00:17:39.600 --> 00:17:42.600
 of tools including Wireshark TCP dump

298
00:17:42.600 --> 00:17:45.400
 and many others PK PNG

299
00:17:45.400 --> 00:17:48.400
 files aren't as widely supported, but they

300
00:17:48.400 --> 00:17:51.100
 can open and analyzed using Wireshark and

301
00:17:51.100 --> 00:17:52.500
 a few other tools.

302
00:17:53.300 --> 00:17:56.300
Anti-distructure difference is

303
00:17:56.300 --> 00:18:00.000
 PK files have a simple structure with a

304
00:17:59.100 --> 00:18:02.700
 single Global header followed by a serious

305
00:18:02.700 --> 00:18:05.200
 or packet records pick up and G

306
00:18:05.200 --> 00:18:08.700
 files have a more complex structure with multiple

307
00:18:08.700 --> 00:18:11.600
 block types that can be used to store

308
00:18:11.600 --> 00:18:13.300
 different types of data.

309
00:18:14.200 --> 00:18:18.200
And the third difference about between the

310
00:18:17.200 --> 00:18:21.300
 these files in this

311
00:18:20.300 --> 00:18:23.700
 way. We kept PK files

312
00:18:23.700 --> 00:18:26.500
 have limited extensibility as they

313
00:18:26.500 --> 00:18:30.200
 do not include a way to store additional metadata

314
00:18:29.200 --> 00:18:33.900
 or other types of data pkbng

315
00:18:32.900 --> 00:18:35.100
 files on the other

316
00:18:35.100 --> 00:18:38.800
 hand are designed to be extensible and can

317
00:18:38.800 --> 00:18:41.800
 include a wide range of additional type

318
00:18:41.800 --> 00:18:45.300
 data types. And the last difference criteria

319
00:18:44.300 --> 00:18:48.300
 is performance and pickup

320
00:18:47.300 --> 00:18:50.700
 files can be large and difficult to

321
00:18:50.700 --> 00:18:51.200
 process.

322
00:18:51.900 --> 00:18:55.500
Especially when capturing traffic

323
00:18:54.500 --> 00:18:57.800
 from high bandwidth networks

324
00:18:57.800 --> 00:19:00.300
 and pick up NG files

325
00:19:00.300 --> 00:19:04.000
 are generally more efficient and easier to

326
00:19:03.000 --> 00:19:04.200
 process.

327
00:19:05.100 --> 00:19:08.500
As they are optimized for storing large amounts

328
00:19:08.500 --> 00:19:09.200
 of data.

329
00:19:10.100 --> 00:19:15.000
These are the differences about these two extension and

330
00:19:13.000 --> 00:19:16.900
 the pcap

331
00:19:16.900 --> 00:19:20.000
 engine file format is the default extension

332
00:19:19.900 --> 00:19:22.600
 if you don't specify the

333
00:19:22.600 --> 00:19:26.200
 extension in Wireshark, so

334
00:19:28.900 --> 00:19:31.600
And the other window is the

335
00:19:31.600 --> 00:19:33.000
 options window.

336
00:19:33.800 --> 00:19:37.000
So in here you can see some display

337
00:19:36.000 --> 00:19:37.900
 options.

338
00:19:39.500 --> 00:19:43.400
Name resolutions and display options

339
00:19:42.400 --> 00:19:45.500
 are update list

340
00:19:45.500 --> 00:19:48.700
 of packets in real time. And we

341
00:19:48.700 --> 00:19:51.800
 also use this option

342
00:19:51.800 --> 00:19:54.900
 by default and automatically

343
00:19:54.900 --> 00:19:57.200
 scroll during live capture, you

344
00:19:57.200 --> 00:19:57.200
 know.

345
00:19:58.400 --> 00:20:02.600
Some pickets are streaming continuous and

346
00:20:02.600 --> 00:20:05.600
 we are observing packets.

347
00:20:06.500 --> 00:20:09.600
Up to down and there's streaming in

348
00:20:09.600 --> 00:20:12.900
 this way. So automatically scroll doing

349
00:20:12.900 --> 00:20:15.800
 live capture in this

350
00:20:15.800 --> 00:20:18.900
 way. And the other choice is

351
00:20:18.900 --> 00:20:21.500
 showing capture information doing

352
00:20:21.500 --> 00:20:24.400
 live captures and we are not using

353
00:20:24.400 --> 00:20:27.900
 this option by default and name

354
00:20:27.900 --> 00:20:30.800
 our resolution under the name red

355
00:20:30.800 --> 00:20:33.800
 solution. We have three options

356
00:20:33.800 --> 00:20:37.100
 resolve Mac addresses resolve

357
00:20:36.100 --> 00:20:40.100
 Network names and result transport links.

358
00:20:41.800 --> 00:20:44.400
In Wireshark, the result make

359
00:20:44.400 --> 00:20:47.400
 other races option is a feature that enables the

360
00:20:47.400 --> 00:20:50.400
 tool to resolve the Mac addresses of the device on

361
00:20:50.400 --> 00:20:53.600
 network and displayed them in the packet

362
00:20:53.600 --> 00:20:56.400
 capture by default. This option

363
00:20:56.400 --> 00:20:58.600
 is enabled as you see

364
00:20:59.400 --> 00:21:02.400
which means that Wireshark will attempt to

365
00:21:02.400 --> 00:21:05.600
 resolve the Mac addresses of the devices in the

366
00:21:05.600 --> 00:21:08.400
 capture and display them in the pack list

367
00:21:08.400 --> 00:21:10.100
 and other views.

368
00:21:10.600 --> 00:21:13.800
As you can see in here, we can

369
00:21:13.800 --> 00:21:17.000
 see the device name Intel

370
00:21:16.200 --> 00:21:20.700
 Core as Intel Core. So the

371
00:21:19.700 --> 00:21:22.700
 Wireshark has resolved

372
00:21:22.700 --> 00:21:25.700
 the MAC address to the name to the device name

373
00:21:25.700 --> 00:21:29.000
 and how the result Mech address option

374
00:21:28.200 --> 00:21:31.800
 works in by shark Wireshark maintains

375
00:21:31.800 --> 00:21:33.600
 a MAC address resolution cash.

376
00:21:34.400 --> 00:21:37.400
As it processes the packets in the capture

377
00:21:37.400 --> 00:21:40.400
 Wireshark maintains a cache of the Mac addresses

378
00:21:40.400 --> 00:21:41.800
 that it has seen.

379
00:21:42.800 --> 00:21:45.300
So this cash is used to store the MAC

380
00:21:45.300 --> 00:21:49.100
 address of the devices on the network and corresponding

381
00:21:48.100 --> 00:21:52.100
 pip addresses Wireshark uses

382
00:21:51.100 --> 00:21:55.500
 the cache to resolve mechanalysis. If the

383
00:21:54.500 --> 00:21:57.700
 MAC address is not in the cache Wireshark

384
00:21:57.700 --> 00:21:59.100
 will display the MAC address.

385
00:21:59.800 --> 00:22:02.800
In this plural form, so it couldn't

386
00:22:02.800 --> 00:22:05.600
 resolve this Mac address and we

387
00:22:05.600 --> 00:22:06.500
 are seeing it.

388
00:22:07.200 --> 00:22:10.400
in the row form as in here, but

389
00:22:11.600 --> 00:22:14.700
these Mac addresses has been resolved and

390
00:22:14.700 --> 00:22:16.700
 we can see the device names.

391
00:22:18.500 --> 00:22:21.700
So it is the resolving Mac addresses

392
00:22:21.700 --> 00:22:24.300
 and the other option under the name

393
00:22:24.300 --> 00:22:27.700
 of the solution. You can check the

394
00:22:27.700 --> 00:22:29.400
 result Network names.

395
00:22:30.200 --> 00:22:34.800
And the last one the resolve transport names

396
00:22:34.800 --> 00:22:37.600
 as you can see and that's all

397
00:22:37.600 --> 00:22:41.400
 about the Wireshark capture options window and

398
00:22:40.400 --> 00:22:42.300
 we can close.

399
00:22:45.100 --> 00:22:48.600
We will talk about the Wireshark interface and

400
00:22:48.600 --> 00:22:52.000
 device I model relationship on

401
00:22:51.300 --> 00:22:54.600
 the next lesson, and so see you

402
00:22:54.600 --> 00:22:55.500
 on the next video.
