WEBVTT - This file was automatically generated by VIMEO

0
00:00:17.400 --> 00:00:20.400
Hello everyone in this video. You will learn the different

1
00:00:20.400 --> 00:00:21.400
 filtering techniques.

2
00:00:22.400 --> 00:00:25.900
At the beginning we will work on the capturing live Network traffic

3
00:00:25.900 --> 00:00:28.300
 and let's begin to filter out

4
00:00:28.300 --> 00:00:32.400
 our packets on the five Network traffic.

5
00:00:31.400 --> 00:00:34.700
 We will first make filtering

6
00:00:34.700 --> 00:00:37.500
 before capturing the network traffic

7
00:00:37.500 --> 00:00:40.900
 and we are going to open the capture options

8
00:00:40.900 --> 00:00:41.300
 window.

9
00:00:44.400 --> 00:00:47.500
In this window, you can see the compiled selected

10
00:00:47.500 --> 00:00:48.300
 PPS.

11
00:00:49.500 --> 00:00:50.400
this button

12
00:00:51.200 --> 00:00:54.700
vpf is an acronym that stands for

13
00:00:54.700 --> 00:00:57.300
 Berkeley packet filters syntax.

14
00:00:57.800 --> 00:01:00.700
So and it is applied to all of

15
00:01:00.700 --> 00:01:03.800
 the filters you select for capture. It

16
00:01:03.800 --> 00:01:06.600
 is critical because this is what will allow

17
00:01:06.600 --> 00:01:09.600
 the computer to understand whatever you

18
00:01:09.600 --> 00:01:12.600
 create and how those filters are

19
00:01:12.600 --> 00:01:15.800
 used in the Wireshark and

20
00:01:15.800 --> 00:01:19.700
 after selecting the interface to

21
00:01:18.700 --> 00:01:21.800
 capture Network traffic.

22
00:01:23.300 --> 00:01:26.600
And I will choose the Wi-Fi interface.

23
00:01:27.500 --> 00:01:30.400
And after selecting the interface to

24
00:01:30.400 --> 00:01:33.900
 capture Network traffic. There is a filter field. You can

25
00:01:33.900 --> 00:01:36.200
 see enter a capture filters.

26
00:01:37.900 --> 00:01:41.200
On this Pane and there's

27
00:01:40.200 --> 00:01:43.300
 a filter field in this window.

28
00:01:43.300 --> 00:01:46.900
 We may enter our filter here and then

29
00:01:46.900 --> 00:01:49.800
 begin the capturing process as a

30
00:01:49.800 --> 00:01:52.600
 result on the packets that matching the

31
00:01:52.600 --> 00:01:55.700
 filter the determined are collected and

32
00:01:55.700 --> 00:01:58.300
 stored. Let's go ahead

33
00:01:58.300 --> 00:02:01.900
 and click on the bookmark icon.

34
00:02:03.600 --> 00:02:06.700
and in this icon, you can

35
00:02:06.700 --> 00:02:09.500
 see some manage saved

36
00:02:09.500 --> 00:02:11.500
 bookmarks, so

37
00:02:13.500 --> 00:02:16.200
And when we are when we are

38
00:02:16.200 --> 00:02:19.700
 clicking on this button this bookmark button,

39
00:02:19.700 --> 00:02:23.600
 you can see the manage captured

40
00:02:22.600 --> 00:02:24.000
 filters.

41
00:02:24.600 --> 00:02:28.300
So we will select this button this Choice. Sorry

42
00:02:27.300 --> 00:02:30.300
 from the

43
00:02:30.300 --> 00:02:31.300
 drop down menu.

44
00:02:33.400 --> 00:02:35.500
And we selected.

45
00:02:37.500 --> 00:02:42.900
This window will come to us so pre-recorded

46
00:02:40.900 --> 00:02:44.800
 and ready-made

47
00:02:43.800 --> 00:02:46.900
 basic filtering is shown here.

48
00:02:48.500 --> 00:02:51.600
As a result even someone who has never used

49
00:02:51.600 --> 00:02:54.100
 a capture filter May understand it.

50
00:02:57.300 --> 00:03:01.700
And to escape receiving broadcast and multicast

51
00:03:00.700 --> 00:03:04.700
 packets. For example, we may

52
00:03:04.700 --> 00:03:07.900
 use the not broadcast and not

53
00:03:07.900 --> 00:03:09.400
 multicast filtering.

54
00:03:10.800 --> 00:03:14.300
We can we can make a filtering

55
00:03:13.300 --> 00:03:16.500
 to escape receiving some

56
00:03:16.500 --> 00:03:19.700
 broadcast and multicast spec packets

57
00:03:19.700 --> 00:03:23.400
 by this filtering. So

58
00:03:22.400 --> 00:03:26.200
 as a logical operator do not

59
00:03:26.200 --> 00:03:30.100
 operator do not operator is

60
00:03:29.100 --> 00:03:34.600
 used here the mean with using

61
00:03:33.600 --> 00:03:36.600
 this operator. We

62
00:03:36.600 --> 00:03:39.600
 mean will not broadcast when we

63
00:03:39.600 --> 00:03:40.000
 say that.

64
00:03:42.400 --> 00:03:45.500
So the same is true, the same is true

65
00:03:45.500 --> 00:03:49.200
 for multicast and we

66
00:03:48.200 --> 00:03:51.300
 used and comparison.

67
00:03:52.200 --> 00:03:56.200
And we used and comparison operators to

68
00:03:55.200 --> 00:03:58.700
 satisfy both of these conditions.

69
00:03:59.800 --> 00:04:00.600
We may use.

70
00:04:01.600 --> 00:04:04.800
And operators for this

71
00:04:04.800 --> 00:04:08.100
 purpose. We may also utilize C

72
00:04:07.100 --> 00:04:10.800
 like operators such as not and

73
00:04:10.800 --> 00:04:13.600
 and so instead of not we

74
00:04:13.600 --> 00:04:17.100
 may use an exclamation point and

75
00:04:16.100 --> 00:04:20.200
 a double and symbol

76
00:04:19.200 --> 00:04:24.100
 instead of these operators we

77
00:04:22.100 --> 00:04:24.700
 can use that.

78
00:04:27.800 --> 00:04:31.100
Justice, so the exclamation point

79
00:04:30.100 --> 00:04:34.100
 is enough instead of

80
00:04:34.100 --> 00:04:34.800
 not.

81
00:04:35.600 --> 00:04:39.900
word and you can use again instead

82
00:04:38.900 --> 00:04:40.200
 of not

83
00:04:42.100 --> 00:04:45.500
the exclamation point like this

84
00:04:49.700 --> 00:04:52.200
and we are clearing the spaces.

85
00:04:54.600 --> 00:04:56.800
Okay, and then you can use.

86
00:04:58.300 --> 00:05:00.400
And double and symbol.

87
00:05:06.700 --> 00:05:07.500
so you can

88
00:05:09.400 --> 00:05:12.700
you can write a double and

89
00:05:12.700 --> 00:05:15.100
 symbol instead of

90
00:05:15.100 --> 00:05:16.800
 the word and

91
00:05:17.900 --> 00:05:21.300
and these symbols are used

92
00:05:20.300 --> 00:05:25.400
 instead of the word versions

93
00:05:24.400 --> 00:05:27.800
 and these symbols are C

94
00:05:27.800 --> 00:05:30.400
 like versions of The

95
00:05:30.400 --> 00:05:33.700
 Operators that we

96
00:05:33.700 --> 00:05:36.500
 have used for the filtering.

97
00:05:38.100 --> 00:05:41.800
And this filter expiration is the same the

98
00:05:41.800 --> 00:05:42.600
 previous one.

99
00:05:44.100 --> 00:05:45.900
And you can use like this.

100
00:05:49.100 --> 00:05:53.000
In this window, we can also add our own filtering

101
00:05:52.500 --> 00:05:55.600
 phrases, press the plus

102
00:05:55.600 --> 00:05:56.100
 button.

103
00:05:57.700 --> 00:06:00.600
And let's create a filter that will only

104
00:06:00.600 --> 00:06:03.700
 capture incoming and outgoing packets

105
00:06:03.700 --> 00:06:05.400
 from my own IP address.

106
00:06:07.100 --> 00:06:10.100
So let's look at our IP address firstly.

107
00:06:30.200 --> 00:06:39.600
As you can see my IP address is 192.168.0.10.

108
00:06:33.600 --> 00:06:40.500
 So

109
00:06:39.500 --> 00:06:42.400
 I will use this IP address

110
00:06:42.400 --> 00:06:45.300
 as my IP address is my

111
00:06:45.300 --> 00:06:47.800
 for my filtering code.

112
00:07:04.200 --> 00:07:07.700
And now I'm writing my filtering expiration.

113
00:07:09.400 --> 00:07:11.100
for my IP address

114
00:07:16.900 --> 00:07:17.100
and

115
00:07:18.400 --> 00:07:19.400
for name

116
00:07:29.900 --> 00:07:32.600
terrific on my IP as the

117
00:07:32.600 --> 00:07:33.200
 printing name.

118
00:07:34.300 --> 00:07:35.100
And that's it.

119
00:07:39.900 --> 00:07:42.300
Now, let's create some filtering to capture

120
00:07:42.300 --> 00:07:46.000
 packets with only this IP address as their

121
00:07:45.400 --> 00:07:46.800
 Source address.

122
00:07:47.600 --> 00:07:48.200
to do this

123
00:07:49.300 --> 00:07:52.400
we start with SRC.

124
00:07:56.500 --> 00:08:00.600
And with SRC we mean

125
00:08:00.600 --> 00:08:04.700
 which stands for source source

126
00:08:03.700 --> 00:08:06.100
 IP address we will

127
00:08:06.100 --> 00:08:07.300
 specify.

128
00:08:08.300 --> 00:08:11.600
And to specify the source host IP address

129
00:08:11.600 --> 00:08:14.200
 we can we can write

130
00:08:14.200 --> 00:08:15.200
 Source host.

131
00:08:16.800 --> 00:08:18.400
and then IP address

132
00:08:21.400 --> 00:08:24.800
and this is enough to make a filtering.

133
00:08:26.600 --> 00:08:29.700
To capture some Network packets

134
00:08:29.700 --> 00:08:33.500
 with only source IP

135
00:08:32.500 --> 00:08:33.600
 address.

136
00:08:35.500 --> 00:08:39.100
Let this filtering be named from my

137
00:08:38.100 --> 00:08:39.700
 IP.

138
00:08:54.100 --> 00:08:57.600
The only capture outbound traffic from this IP

139
00:08:57.600 --> 00:09:00.600
 address using this filter now, let

140
00:09:00.600 --> 00:09:03.900
 us now build filtering to catch packets

141
00:09:03.900 --> 00:09:07.300
 with only this IP address as they

142
00:09:07.300 --> 00:09:09.200
 are destination address and do this.

143
00:09:13.400 --> 00:09:16.700
We begin with DST which

144
00:09:16.700 --> 00:09:18.400
 stands for destination.

145
00:09:21.500 --> 00:09:22.200
and host

146
00:09:25.100 --> 00:09:27.600
and then again IP address

147
00:09:33.400 --> 00:09:36.500
so let this filtering be named to my

148
00:09:36.500 --> 00:09:37.000
 IP.

149
00:09:47.800 --> 00:09:50.200
And we only capture traffic to this

150
00:09:50.200 --> 00:09:52.300
 IP address with this filter.

151
00:09:58.100 --> 00:10:01.500
And as you can see, we may provide the port.

152
00:10:02.400 --> 00:10:07.100
in a provide some ports and we

153
00:10:05.100 --> 00:10:08.900
 may provide Samples used

154
00:10:08.900 --> 00:10:11.600
 by that protocol for example,

155
00:10:11.600 --> 00:10:15.600
 HTTP or at an

156
00:10:14.600 --> 00:10:17.800
 another protocol as

157
00:10:17.800 --> 00:10:21.600
 DNS and to capture

158
00:10:21.600 --> 00:10:25.300
 just traffic in part in particular protocols

159
00:10:24.300 --> 00:10:27.600
 by using a capture filter

160
00:10:27.600 --> 00:10:29.900
 like this and

161
00:10:31.400 --> 00:10:34.300
to capture only DNS packets. For example,

162
00:10:34.300 --> 00:10:37.500
 we can write a filter like

163
00:10:37.500 --> 00:10:37.800
 this.

164
00:10:40.500 --> 00:10:41.400
only the port

165
00:10:42.900 --> 00:10:44.300
53

166
00:10:45.900 --> 00:10:48.500
you know the port 53 is

167
00:10:48.500 --> 00:10:51.500
 used for the DNS protocol and you

168
00:10:51.500 --> 00:10:55.000
 can use this filter to capture only DNS

169
00:10:54.600 --> 00:10:58.000
 packets and we can give a

170
00:10:57.100 --> 00:10:58.700
 name as

171
00:11:02.800 --> 00:11:04.300
only DNS

172
00:11:07.200 --> 00:11:10.600
So that's it. And as a

173
00:11:10.600 --> 00:11:13.300
 result, we only see packets coming and going

174
00:11:13.300 --> 00:11:16.500
 from Port 53. They use

175
00:11:16.500 --> 00:11:19.700
 port 53 since the DNS protocol

176
00:11:19.700 --> 00:11:22.600
 runs on that part and we can

177
00:11:22.600 --> 00:11:26.000
 directly filter TCP UDP

178
00:11:25.800 --> 00:11:28.000
 and IP.

179
00:11:28.700 --> 00:11:31.400
and ARP also

180
00:11:32.300 --> 00:11:38.100
we can use and airp protocols

181
00:11:36.100 --> 00:11:39.000
 by their names.

182
00:11:40.300 --> 00:11:40.900
You can see.

183
00:11:42.300 --> 00:11:46.300
And for the other protocols we have

184
00:11:45.300 --> 00:11:48.500
 to we have to specify the

185
00:11:48.500 --> 00:11:51.300
 port their ports to make a

186
00:11:51.300 --> 00:11:55.100
 filtering for the other protocols and

187
00:11:54.100 --> 00:11:59.300
 the filters for these protocols for

188
00:11:57.300 --> 00:12:00.600
 TCP and

189
00:12:00.200 --> 00:12:02.600
 UDP and arp.

190
00:12:05.500 --> 00:12:08.700
Are already available in the capture filters

191
00:12:08.700 --> 00:12:08.800
 window?

192
00:12:09.800 --> 00:12:12.600
So to generate these treatable filtering

193
00:12:12.600 --> 00:12:15.800
 for our purposes. We must pay spatial

194
00:12:15.800 --> 00:12:20.100
 attention to the filtering syntax. And now

195
00:12:19.100 --> 00:12:22.800
 let's do capturing using one

196
00:12:22.800 --> 00:12:24.700
 of the filters we created.

197
00:12:25.500 --> 00:12:28.400
We have three filtering in

198
00:12:28.400 --> 00:12:31.000
 here. Now. We have created.

199
00:12:36.600 --> 00:12:39.900
We will choose the entire face as Wi-Fi

200
00:12:39.900 --> 00:12:43.800
 and here when

201
00:12:42.800 --> 00:12:45.800
 we click on the bookmark sign.

202
00:12:47.800 --> 00:12:49.800
We can now see the filter.

203
00:12:50.800 --> 00:12:52.100
That we have added.

204
00:12:53.700 --> 00:12:56.900
On the DNS to my IP from

205
00:12:56.900 --> 00:12:59.200
 my IP and traffic on my IP.

206
00:13:00.300 --> 00:13:02.200
We have created these filters.

207
00:13:04.800 --> 00:13:08.200
And I will choose first the filter

208
00:13:07.200 --> 00:13:10.000
 of traffic on my IP.

209
00:13:11.300 --> 00:13:14.600
And they start to the capturing process.

210
00:13:25.500 --> 00:13:29.400
Network packets started to drop because some programs

211
00:13:28.400 --> 00:13:31.300
 that I am running active in

212
00:13:31.300 --> 00:13:35.000
 the background are using the internet and you

213
00:13:34.400 --> 00:13:37.200
 can open the command line

214
00:13:37.200 --> 00:13:40.700
 window and you can send some

215
00:13:40.700 --> 00:13:46.000
 pink packets to google.com or wireshark.org

216
00:13:44.600 --> 00:13:47.100
 websites, or you

217
00:13:47.100 --> 00:13:51.400
 can go to these websites on your browser in

218
00:13:50.400 --> 00:13:54.100
 order to create some HTTP packets,

219
00:13:53.100 --> 00:13:56.200
 but I don't need

220
00:13:56.200 --> 00:13:59.800
 to do these operations because I

221
00:13:59.800 --> 00:14:03.700
 have already some packets

222
00:14:03.700 --> 00:14:05.500
 on my network.

223
00:14:06.300 --> 00:14:09.600
And that's enough for now and I

224
00:14:09.600 --> 00:14:11.600
 am stopping the capturing process.

225
00:14:14.100 --> 00:14:18.300
as you can see the package that we have now are coming

226
00:14:18.300 --> 00:14:23.000
 from only the IP address that

227
00:14:21.300 --> 00:14:24.500
 we have specified in

228
00:14:24.500 --> 00:14:28.700
 the filter and or the

229
00:14:27.700 --> 00:14:30.400
 packets are

230
00:14:32.600 --> 00:14:35.900
Going to this IP address or coming

231
00:14:35.900 --> 00:14:38.300
 from this IP address and that's

232
00:14:38.300 --> 00:14:41.300
 why we only see this IP address

233
00:14:41.300 --> 00:14:45.400
 as the source or destination

234
00:14:44.400 --> 00:14:47.700
 IP address on this

235
00:14:47.700 --> 00:14:50.600
 PK file now, let's try another

236
00:14:50.600 --> 00:14:54.000
 filter to to capture

237
00:14:53.400 --> 00:14:55.500
 some packets on my network.

238
00:14:56.400 --> 00:14:59.500
And I'm closing this pick a

239
00:14:59.500 --> 00:15:00.600
 file firstly.

240
00:15:01.600 --> 00:15:04.100
Close this and continue without saving.

241
00:15:04.900 --> 00:15:08.000
And again, we will start a

242
00:15:07.000 --> 00:15:08.500
 capture.

243
00:15:09.500 --> 00:15:10.400
and

244
00:15:11.800 --> 00:15:14.300
in this step now, I will

245
00:15:14.300 --> 00:15:16.100
 choose another filter.

246
00:15:17.400 --> 00:15:20.100
We have chosen the traffic on my

247
00:15:20.100 --> 00:15:23.300
 IP filtering last one

248
00:15:23.300 --> 00:15:26.400
 in last one and now I will choose

249
00:15:26.400 --> 00:15:29.700
 the from my IP filtering. So

250
00:15:29.700 --> 00:15:33.300
 I will see the packets only sourcing

251
00:15:32.300 --> 00:15:35.000
 from this IP address.

252
00:15:36.300 --> 00:15:39.800
And I have chosen this IP this

253
00:15:39.800 --> 00:15:42.800
 filtering and start.

254
00:15:44.500 --> 00:15:46.000
now as you can see

255
00:15:47.600 --> 00:15:49.100
the only see

256
00:15:49.700 --> 00:15:52.600
this IP address is the

257
00:15:52.600 --> 00:15:53.600
 source IP address.

258
00:15:57.700 --> 00:16:00.700
So that's enough for now. Again. We

259
00:16:00.700 --> 00:16:02.600
 are stopping capturing packets.

260
00:16:04.200 --> 00:16:06.500
And let's try another one.

261
00:16:10.700 --> 00:16:15.700
In this time, I will choose the from my

262
00:16:15.700 --> 00:16:16.700
 IP address.

263
00:16:18.600 --> 00:16:22.100
Sorry to my IP address as the

264
00:16:21.100 --> 00:16:24.500
 destination IP

265
00:16:24.500 --> 00:16:24.800
 address.

266
00:16:26.200 --> 00:16:29.300
And I will use this filtering.

267
00:16:30.100 --> 00:16:33.900
While we are capturing some packets.

268
00:16:34.700 --> 00:16:36.200
So click on the start.

269
00:16:38.700 --> 00:16:40.000
continue without saving

270
00:16:54.200 --> 00:16:56.200
that's enough and we can stop.

271
00:16:57.100 --> 00:17:00.100
the capturing and in this

272
00:17:00.100 --> 00:17:04.300
 time you can see the IP address

273
00:17:04.300 --> 00:17:07.500
 as the destination IP address

274
00:17:07.500 --> 00:17:10.000
 only so there is

275
00:17:10.800 --> 00:17:14.000
no, IP address except

276
00:17:15.300 --> 00:17:18.900
that IP address we have specified before in

277
00:17:18.900 --> 00:17:20.600
 filtering expiration.

278
00:17:22.100 --> 00:17:26.100
We are seeing only this IP

279
00:17:25.100 --> 00:17:28.900
 address as the destination IP

280
00:17:28.900 --> 00:17:31.000
 address, so that's okay now.

281
00:17:35.200 --> 00:17:38.800
Now, let's review the capture filter syntax structure again.

282
00:17:42.400 --> 00:17:45.700
The words we will use to define

283
00:17:45.700 --> 00:17:46.600
 the scope.

284
00:17:49.600 --> 00:17:50.500
or the scope

285
00:17:51.400 --> 00:17:52.500
are host

286
00:17:55.200 --> 00:17:59.100
Or net which means Network you

287
00:17:58.100 --> 00:18:02.900
 can specify the network address before

288
00:18:01.900 --> 00:18:05.300
 capturing process. And

289
00:18:04.300 --> 00:18:07.800
 the other one is the

290
00:18:07.800 --> 00:18:09.300
 port range.

291
00:18:11.400 --> 00:18:12.000
Port range

292
00:18:12.700 --> 00:18:16.300
or you can use port word.

293
00:18:17.800 --> 00:18:19.100
of as well

294
00:18:21.500 --> 00:18:24.700
So you can specify a port range

295
00:18:24.700 --> 00:18:28.100
 using the port range

296
00:18:27.100 --> 00:18:30.900
 word the port range

297
00:18:30.900 --> 00:18:34.100
 expression and to determine

298
00:18:33.100 --> 00:18:35.000
 the direction.

299
00:18:36.100 --> 00:18:37.200
You can use.

300
00:18:41.600 --> 00:18:45.900
You can use the words SRC which

301
00:18:45.900 --> 00:18:47.400
 means source.

302
00:18:47.900 --> 00:18:50.000
and the DST

303
00:18:51.200 --> 00:18:53.400
which stands for destination?

304
00:18:55.700 --> 00:19:00.600
And you can use these words for determining

305
00:18:59.600 --> 00:19:02.800
 the direction the traffic

306
00:19:02.800 --> 00:19:04.600
 direction and finally.

307
00:19:05.700 --> 00:19:08.300
Finally the words we

308
00:19:08.300 --> 00:19:10.200
 can use to indicate the protocol.

309
00:19:14.900 --> 00:19:17.000
eater for ethernet

310
00:19:18.300 --> 00:19:19.600
And VLAN.

311
00:19:20.900 --> 00:19:25.100
to specify the sum

312
00:19:23.100 --> 00:19:25.700
 vlans

313
00:19:26.800 --> 00:19:27.900
and IP

314
00:19:28.900 --> 00:19:29.100
and

315
00:19:32.500 --> 00:19:34.600
IP version 6

316
00:19:37.400 --> 00:19:40.600
And ARP for our protocol.

317
00:19:41.700 --> 00:19:45.000
and read and are

318
00:19:44.000 --> 00:19:45.700
 our

319
00:19:49.600 --> 00:19:56.600
for the other protocol which means

320
00:19:56.600 --> 00:20:00.400
 reverse ARP

321
00:19:59.400 --> 00:20:03.900
 reverse are protocol and

322
00:20:03.900 --> 00:20:05.100
 the TCP.

323
00:20:05.900 --> 00:20:06.400
again

324
00:20:08.300 --> 00:20:11.900
we have seen before in the capture filters window

325
00:20:11.900 --> 00:20:12.800
 and

326
00:20:14.200 --> 00:20:16.100
lastly UDP

327
00:20:16.700 --> 00:20:21.300
You can use these words to specify

328
00:20:20.300 --> 00:20:25.500
 the protocol to directly

329
00:20:23.500 --> 00:20:28.000
 specify these

330
00:20:26.800 --> 00:20:30.100
 protocols. And if

331
00:20:29.100 --> 00:20:33.400
 you want to specify some other

332
00:20:32.400 --> 00:20:35.200
 protocols, you must

333
00:20:35.200 --> 00:20:38.400
 use the port numbers for example

334
00:20:38.400 --> 00:20:39.600
 if you use to

335
00:20:41.400 --> 00:20:44.900
If you want to specify the DNS

336
00:20:44.900 --> 00:20:48.900
 protocol, you must enter the

337
00:20:47.900 --> 00:20:50.300
 port number of

338
00:20:50.300 --> 00:20:53.400
 the DNS as 53.

339
00:20:55.900 --> 00:20:58.700
So that's okay about the capturing filters.

340
00:21:06.200 --> 00:21:09.900
The second filtering option is display filter

341
00:21:09.900 --> 00:21:12.300
 in this section. I will use

342
00:21:12.300 --> 00:21:15.600
 a pickup file that I have downloaded from the

343
00:21:15.600 --> 00:21:20.100
 Wireshark website, you know, why shark.org

344
00:21:18.100 --> 00:21:21.700
 and now

345
00:21:21.700 --> 00:21:25.000
 we are opening that file in Wireshark firstly.

346
00:21:29.800 --> 00:21:32.500
And the PK file

347
00:21:32.500 --> 00:21:36.100
 is HTTP with gpags

348
00:21:35.100 --> 00:21:37.000
 DOT cap.

349
00:21:38.100 --> 00:21:41.500
So and this capturing file has some traffic

350
00:21:41.500 --> 00:21:43.500
 with HTTP protocol.

351
00:21:44.300 --> 00:21:47.800
Keep in mind that display filters are

352
00:21:47.800 --> 00:21:50.400
 used while the capture is running

353
00:21:50.400 --> 00:21:53.300
 and after the capture has stopped.

354
00:21:54.200 --> 00:21:57.800
So if you have already a pickup file,

355
00:21:57.800 --> 00:22:00.800
 you can use display filter.

356
00:22:02.200 --> 00:22:05.300
You can use some display filters. So let's

357
00:22:05.300 --> 00:22:09.100
 see some examples previously written in Wireshark

358
00:22:08.100 --> 00:22:12.100
 and under the analyze menu.

359
00:22:11.100 --> 00:22:15.600
 You can click display filters.

360
00:22:17.200 --> 00:22:21.100
In this window, we can see some of the expressions in

361
00:22:20.100 --> 00:22:23.600
 capturing filters.

362
00:22:24.500 --> 00:22:27.900
For example in addition to protocol filters

363
00:22:27.900 --> 00:22:29.700
 such as IP.

364
00:22:30.200 --> 00:22:34.100
And TCP and the UDP.

365
00:22:33.100 --> 00:22:36.800
 You can see that expressions using

366
00:22:36.800 --> 00:22:40.300
 logical operators such

367
00:22:39.300 --> 00:22:42.300
 as not ARP not

368
00:22:42.300 --> 00:22:45.000
 our used here.

369
00:22:45.800 --> 00:22:48.900
As in capture filters

370
00:22:48.900 --> 00:22:51.200
 window and in addition to

371
00:22:51.200 --> 00:22:54.400
 this to the expressions in

372
00:22:54.400 --> 00:22:57.400
 the capture filtering. We should know that here.

373
00:22:57.400 --> 00:23:00.500
 We can also filter other protocols by name.

374
00:23:00.500 --> 00:23:03.700
 For example, you can use

375
00:23:03.700 --> 00:23:07.300
 the HTTP name for

376
00:23:06.300 --> 00:23:09.600
 the filtering and

377
00:23:10.800 --> 00:23:13.400
For example, we can

378
00:23:13.400 --> 00:23:17.400
 use the DNS as

379
00:23:16.400 --> 00:23:19.900
 protocol name to make

380
00:23:19.900 --> 00:23:22.500
 a filter. And now let's

381
00:23:22.500 --> 00:23:26.200
 enter a filter to see only HTTP packets

382
00:23:25.200 --> 00:23:29.000
 in the display filter

383
00:23:28.000 --> 00:23:29.500
 field.

384
00:23:34.300 --> 00:23:35.700
If you type http.

385
00:23:37.300 --> 00:23:37.500
and

386
00:23:38.500 --> 00:23:41.900
put a dot you will see it automatically suggest

387
00:23:41.900 --> 00:23:44.300
 any parameters that may be

388
00:23:44.300 --> 00:23:47.300
 present in a in an HTTP packet or

389
00:23:47.300 --> 00:23:50.000
 message. For example, let's look at

390
00:23:50.300 --> 00:23:51.700
 this HTTP packet.

391
00:23:58.900 --> 00:24:01.400
In this HTTP packet, we have some

392
00:24:01.400 --> 00:24:05.100
 Fields some parameters such as

393
00:24:05.100 --> 00:24:08.300
 except host user agent.

394
00:24:08.900 --> 00:24:11.800
And when we click to the

395
00:24:11.800 --> 00:24:15.000
 display filter field again, and when

396
00:24:14.300 --> 00:24:18.200
 we put the dot syntax.

397
00:24:18.900 --> 00:24:22.500
You can see the some parameters. You

398
00:24:22.500 --> 00:24:27.700
 can see some parameters such as except server

399
00:24:25.700 --> 00:24:29.300
 or such as

400
00:24:29.300 --> 00:24:32.700
 chat and request.

401
00:24:33.800 --> 00:24:36.900
For example, you can see the request parameters

402
00:24:36.900 --> 00:24:39.200
 and user agent.

403
00:24:39.800 --> 00:24:41.100
As well you can see.

404
00:24:42.800 --> 00:24:46.000
So we can understand that all parameters in

405
00:24:45.200 --> 00:24:48.900
 this packet in an HTTP packet

406
00:24:48.900 --> 00:24:52.400
 are also suggested in the display filter

407
00:24:51.400 --> 00:24:53.400
 area.

408
00:24:54.100 --> 00:24:57.100
If you if you put a dot

409
00:24:57.100 --> 00:24:59.000
 syntax, you can see.

410
00:25:00.700 --> 00:25:04.900
this suggestions about the parameters associated with

411
00:25:04.900 --> 00:25:08.200
 the HTTP protocol and

412
00:25:11.200 --> 00:25:15.400
when we used those Syntax for the except parameter

413
00:25:14.400 --> 00:25:16.700
 here, for example

414
00:25:19.100 --> 00:25:22.400
You can you you can you can see

415
00:25:22.400 --> 00:25:26.600
 that. It's suggest here as well does if

416
00:25:25.600 --> 00:25:28.800
 you are looking for an HTTP packet

417
00:25:28.800 --> 00:25:31.500
 with a specific parameter value, we can

418
00:25:31.500 --> 00:25:34.700
 specify it in this way and filter

419
00:25:34.700 --> 00:25:38.400
 it to search whether there is such a packet. For

420
00:25:37.400 --> 00:25:40.500
 example this packet this

421
00:25:40.500 --> 00:25:42.900
 packet contains a get method.

422
00:25:43.500 --> 00:25:46.300
as the HTTP method you can

423
00:25:46.300 --> 00:25:48.700
 see in here and

424
00:25:50.500 --> 00:25:53.400
V type V type

425
00:25:53.400 --> 00:25:58.000
 we can type http.request to

426
00:25:57.200 --> 00:26:00.500
 see all HTTP request packets.

427
00:26:02.100 --> 00:26:03.700
And let's look at this.

428
00:26:04.700 --> 00:26:06.500
now dot request

429
00:26:07.900 --> 00:26:10.200
we are writing dot request.

430
00:26:11.300 --> 00:26:14.600
With this filtering, we will see all the

431
00:26:14.600 --> 00:26:17.200
 request packets on http.

432
00:26:18.300 --> 00:26:19.400
Let's click enter.

433
00:26:20.800 --> 00:26:23.300
And as you can see now we have

434
00:26:23.300 --> 00:26:27.300
 all request packets associated with

435
00:26:27.300 --> 00:26:29.500
 HTTP protocol.

436
00:26:30.200 --> 00:26:30.900
we have

437
00:26:31.900 --> 00:26:34.100
19 packets you can see

438
00:26:34.100 --> 00:26:36.000
 in the status bar.

439
00:26:36.900 --> 00:26:40.000
So we see all requests and

440
00:26:39.400 --> 00:26:42.800
 if you are searching for a specific request

441
00:26:42.800 --> 00:26:45.300
 method we can type this.

442
00:26:46.500 --> 00:26:50.300
http.request dot method

443
00:26:52.200 --> 00:26:56.500
and then we will add an operator

444
00:26:55.500 --> 00:26:58.800
 and comparing operators.

445
00:27:01.200 --> 00:27:02.500
this operator is

446
00:27:03.500 --> 00:27:06.400
is equal to operator maybe you

447
00:27:06.400 --> 00:27:10.000
 know, the double equality sign means

448
00:27:09.500 --> 00:27:12.900
 is equal to

449
00:27:13.900 --> 00:27:16.800
This sign means is equal

450
00:27:16.800 --> 00:27:20.100
 to and is equal to operator will

451
00:27:19.100 --> 00:27:23.200
 compare the HTTP methods

452
00:27:22.200 --> 00:27:25.500
 in the packets with the

453
00:27:25.500 --> 00:27:27.000
 value. We will give it.

454
00:27:27.600 --> 00:27:30.400
For example, I will give the method.

455
00:27:31.000 --> 00:27:31.400
get

456
00:27:33.300 --> 00:27:36.400
in this situation is equal to operator will

457
00:27:36.400 --> 00:27:37.100
 compare.

458
00:27:38.300 --> 00:27:41.300
the HTTP methods in the packets with

459
00:27:41.300 --> 00:27:42.700
 the value get

460
00:27:43.900 --> 00:27:46.800
so we will find the ones

461
00:27:46.800 --> 00:27:48.400
 that contain get.

462
00:27:49.400 --> 00:27:52.300
And you know that HTTP request methods

463
00:27:52.300 --> 00:27:56.000
 can be get paused put or page

464
00:27:55.600 --> 00:27:58.400
 now click on the enter to see

465
00:27:58.400 --> 00:28:02.000
 the only get methods in the

466
00:28:01.000 --> 00:28:02.900
 packets.

467
00:28:05.600 --> 00:28:09.200
When we click on the enter now, we have only packets

468
00:28:08.200 --> 00:28:11.600
 which contain the

469
00:28:11.600 --> 00:28:12.500
 get method.

470
00:28:13.300 --> 00:28:17.400
There's no other methods with the

471
00:28:17.400 --> 00:28:19.000
 packets. You can see in here.

472
00:28:20.600 --> 00:28:23.500
We have only get packets now.

473
00:28:27.200 --> 00:28:31.000
For example, if we are looking for a packet containing

474
00:28:30.200 --> 00:28:33.500
 the post method we type

475
00:28:33.500 --> 00:28:36.900
 HTTP request method is

476
00:28:36.900 --> 00:28:39.100
 equal to post.

477
00:28:43.500 --> 00:28:44.700
and hit enter

478
00:28:46.800 --> 00:28:50.000
and as you can see as a

479
00:28:49.200 --> 00:28:52.400
 result, there is only one

480
00:28:52.400 --> 00:28:55.600
 packet contains postmet, but if

481
00:28:55.600 --> 00:28:57.100
 we change it to get

482
00:28:59.100 --> 00:28:59.600
again

483
00:29:03.200 --> 00:29:04.200
and hit enter

484
00:29:06.400 --> 00:29:09.700
we have 18 packets with the

485
00:29:09.700 --> 00:29:10.200
 get methods.

486
00:29:12.300 --> 00:29:14.900
We can see the get request packets here.

487
00:29:15.900 --> 00:29:18.300
Now I will show you how you can

488
00:29:18.300 --> 00:29:21.300
 easily do the same filters as someone who

489
00:29:21.300 --> 00:29:23.100
 doesn't know any filtering.

490
00:29:23.700 --> 00:29:28.000
Who who has any filtering

491
00:29:26.500 --> 00:29:29.800
 information and this

492
00:29:29.800 --> 00:29:32.500
 method is the easiest way to make

493
00:29:32.500 --> 00:29:35.400
 filter. For example, if you

494
00:29:35.400 --> 00:29:39.000
 want to see only the packets with the source IP

495
00:29:38.100 --> 00:29:46.100
 address of 10.1.1.1. We

496
00:29:44.100 --> 00:29:47.300
 will we will choose this

497
00:29:47.300 --> 00:29:48.400
 way to make this.

498
00:29:49.300 --> 00:29:52.900
Firstly I will clear this filtering.

499
00:29:53.500 --> 00:29:54.400
and then

500
00:29:56.200 --> 00:29:59.400
I will take a packet with the

501
00:29:59.400 --> 00:30:04.000
 source IP address 10.1.1 dot

502
00:30:03.700 --> 00:30:06.300
 one and click on

503
00:30:06.300 --> 00:30:09.500
 this packet and and then

504
00:30:09.500 --> 00:30:12.900
 we will expand the Internet Protocol

505
00:30:12.900 --> 00:30:15.300
 version 4 heater.

506
00:30:16.200 --> 00:30:19.600
And in here you can see the source address field

507
00:30:19.600 --> 00:30:23.000
 Source others perimeters, and we

508
00:30:22.200 --> 00:30:24.400
 will use this parameter.

509
00:30:26.100 --> 00:30:28.800
And let's right click on Source address.

510
00:30:29.800 --> 00:30:31.700
And apply as filter.

511
00:30:32.400 --> 00:30:35.300
And the selected let's click selected.

512
00:30:37.600 --> 00:30:38.700
as you can see

513
00:30:40.100 --> 00:30:45.200
in the display filter field and the packet

514
00:30:43.200 --> 00:30:46.700
 paint in the packet

515
00:30:46.700 --> 00:30:49.100
 paint. Our filter

516
00:30:49.100 --> 00:30:53.500
 has been prepared and applied automatically.

517
00:30:52.500 --> 00:30:55.500
 Now, let's say we

518
00:30:55.500 --> 00:30:59.800
 want to see only the packets with 200

519
00:30:58.800 --> 00:31:01.900
 HTTP code and

520
00:31:01.900 --> 00:31:04.300
 OK message from the package

521
00:31:04.300 --> 00:31:07.500
 coming from this IP address.

522
00:31:08.900 --> 00:31:12.200
We can't we can do this in

523
00:31:11.200 --> 00:31:14.800
 this way. Let's click on

524
00:31:14.800 --> 00:31:16.900
 a packet with the message. Ok.

525
00:31:18.200 --> 00:31:19.400
And let's go.

526
00:31:20.700 --> 00:31:23.600
To the packet details Pane and

527
00:31:23.600 --> 00:31:27.300
 let's expand the hypertext

528
00:31:26.300 --> 00:31:28.600
 transfer protocol field.

529
00:31:30.700 --> 00:31:34.400
And we are going to the HTTP response.

530
00:31:35.100 --> 00:31:38.900
So let's right click on the HTTP

531
00:31:38.900 --> 00:31:40.100
 appearance response.

532
00:31:40.900 --> 00:31:43.600
And then when we

533
00:31:43.600 --> 00:31:47.200
 come to apply as filters, we will

534
00:31:47.200 --> 00:31:49.800
 click and select it.

535
00:31:50.700 --> 00:31:53.300
Because we want our new condition to

536
00:31:53.300 --> 00:31:56.500
 be met with the previous one. If

537
00:31:56.500 --> 00:31:59.700
 you want to filter you have prepared to be

538
00:31:59.700 --> 00:32:03.400
 written in the display filter

539
00:32:02.400 --> 00:32:05.700
 and make some change

540
00:32:05.700 --> 00:32:08.500
 instead of applying it

541
00:32:08.500 --> 00:32:12.700
 directly. You can do the same with prepare

542
00:32:11.700 --> 00:32:15.200
 as filter option. So

543
00:32:14.200 --> 00:32:18.800
 I will I will use the prepare

544
00:32:18.800 --> 00:32:21.600
 as filter and the this

545
00:32:21.600 --> 00:32:24.400
 time not apply as filter. I will

546
00:32:24.400 --> 00:32:27.700
 use the prepare as filter and

547
00:32:27.700 --> 00:32:30.800
 lead and selected because

548
00:32:30.800 --> 00:32:33.900
 I want to save the last

549
00:32:33.900 --> 00:32:38.200
 the previous condition which IP

550
00:32:37.200 --> 00:32:43.300
 stores is equal to 10.1.1.1 and

551
00:32:42.300 --> 00:32:46.000
 I will choose the

552
00:32:45.500 --> 00:32:49.200
 end selected just we

553
00:32:48.200 --> 00:32:50.100
 have prepared.

554
00:32:50.700 --> 00:32:53.400
Filtering expiration, but we didn't

555
00:32:53.400 --> 00:32:55.500
 apply yet.

556
00:32:56.200 --> 00:32:59.600
And let's enter this filtering now.

557
00:33:01.500 --> 00:33:04.500
As you can see there are now decades that

558
00:33:04.500 --> 00:33:08.900
 contain only OK answers.

559
00:33:07.900 --> 00:33:11.600
 Okay responses instead

560
00:33:10.600 --> 00:33:13.700
 of using corresponse number.

561
00:33:14.500 --> 00:33:18.200
In here response number we can

562
00:33:17.200 --> 00:33:20.700
 use another option. Let's use

563
00:33:27.100 --> 00:33:30.000
in here http

564
00:33:30.900 --> 00:33:31.600
Dot

565
00:33:34.100 --> 00:33:35.100
response

566
00:33:36.500 --> 00:33:39.000
You will see the response parameter.

567
00:33:39.700 --> 00:33:42.500
And Dot response dot code

568
00:33:42.500 --> 00:33:45.200
 perimeter that I want

569
00:33:45.200 --> 00:33:45.600
 to use.

570
00:33:47.200 --> 00:33:52.300
So HTTP dot response dot code will

571
00:33:50.300 --> 00:33:54.500
 be 200 because

572
00:33:54.500 --> 00:33:57.500
 I want to see the packets with

573
00:33:57.500 --> 00:34:00.300
 the response 200.

574
00:34:02.400 --> 00:34:04.200
code and I will

575
00:34:05.600 --> 00:34:06.800
make equal

576
00:34:07.600 --> 00:34:11.900
to 200 my response

577
00:34:10.900 --> 00:34:12.200
 code.

578
00:34:14.300 --> 00:34:15.300
Now we see that.

579
00:34:16.900 --> 00:34:18.400
the filtering

580
00:34:21.100 --> 00:34:24.500
And we see that we get the same

581
00:34:24.500 --> 00:34:27.400
 result so you can you can

582
00:34:27.400 --> 00:34:30.400
 choose this way instead of

583
00:34:30.400 --> 00:34:34.400
 the HTTP response number

584
00:34:33.400 --> 00:34:36.100
 suppose. We want to

585
00:34:36.100 --> 00:34:40.300
 see packets associated with Apache server some

586
00:34:40.300 --> 00:34:43.400
 Apache servers for this. It

587
00:34:43.400 --> 00:34:47.200
 is necessary to find packets containing Apache

588
00:34:46.200 --> 00:34:49.700
 in the server information.

589
00:34:50.700 --> 00:34:54.400
You can see in here. For example in this packet. The

590
00:34:53.400 --> 00:34:57.000
 server is an Apache server. You

591
00:34:56.100 --> 00:34:59.900
 can see the information about server in

592
00:34:59.900 --> 00:35:02.700
 this parameter and you

593
00:35:02.700 --> 00:35:05.900
 can see this is a Apache server

594
00:35:05.900 --> 00:35:08.600
 and Reddit Linux.

595
00:35:09.800 --> 00:35:13.100
Now we will type A filtering expiration

596
00:35:12.100 --> 00:35:16.600
 with the HTTP server

597
00:35:15.600 --> 00:35:19.200
 and This

598
00:35:18.200 --> 00:35:21.500
 Server field This

599
00:35:21.500 --> 00:35:26.800
 Server perimeter will contain Apache.

600
00:35:27.500 --> 00:35:30.200
And to do this we can type

601
00:35:30.200 --> 00:35:31.700
 http.

602
00:35:32.700 --> 00:35:33.200
Dot

603
00:35:35.400 --> 00:35:36.700
server and

604
00:35:38.800 --> 00:35:41.800
it has already suggested automatically.

605
00:35:44.400 --> 00:35:48.500
and HTTP server will contain Apache

606
00:35:47.500 --> 00:35:48.900
 so

607
00:35:49.900 --> 00:35:51.100
to specify that

608
00:35:52.500 --> 00:35:53.300
we can use.

609
00:35:54.100 --> 00:35:56.000
contains keyword

610
00:35:57.400 --> 00:35:59.200
as you can see contains filter.

611
00:36:01.100 --> 00:36:02.700
and I want to

612
00:36:05.200 --> 00:36:05.600
right

613
00:36:06.400 --> 00:36:08.000
the name of the server

614
00:36:11.300 --> 00:36:12.500
as Apache

615
00:36:14.900 --> 00:36:16.400
so now click on the enter.

616
00:36:20.200 --> 00:36:23.700
And you can see the 10 packets.

617
00:36:25.700 --> 00:36:28.500
Which contained Apache server?

618
00:36:29.500 --> 00:36:32.500
The contains filter has a case sensitive

619
00:36:32.500 --> 00:36:35.300
 feature if the uppercase or lowercase

620
00:36:35.300 --> 00:36:38.500
 feature of the value of the entered in here.

621
00:36:39.500 --> 00:36:43.800
This in display filter field if it

622
00:36:42.800 --> 00:36:45.900
 isn't the same as in

623
00:36:45.900 --> 00:36:46.700
 the packets.

624
00:36:48.200 --> 00:36:51.400
Is in the packets, it will not find

625
00:36:51.400 --> 00:36:55.600
 it. It will not find the packets that

626
00:36:54.600 --> 00:36:57.300
 the name of

627
00:36:57.300 --> 00:37:01.400
 some with this some with

628
00:37:00.400 --> 00:37:04.700
 some uppercase letter or

629
00:37:04.700 --> 00:37:08.000
 with the combination of upper is

630
00:37:07.600 --> 00:37:10.100
 letter and the lowercase letters.

631
00:37:11.700 --> 00:37:14.500
It can't find in this

632
00:37:14.500 --> 00:37:17.600
 situation. If we

633
00:37:17.600 --> 00:37:20.400
 don't if you don't enter the name

634
00:37:20.400 --> 00:37:24.300
 properly, so the

635
00:37:23.300 --> 00:37:26.900
 contains the contains

636
00:37:26.900 --> 00:37:30.200
 filter as a case active

637
00:37:29.200 --> 00:37:32.800
 feature keep in

638
00:37:32.800 --> 00:37:36.200
 mind that because it is important to find

639
00:37:35.200 --> 00:37:38.700
 pecans packets so we

640
00:37:38.700 --> 00:37:41.100
 can use some of

641
00:37:41.100 --> 00:37:44.500
 the methods such as upper or

642
00:37:44.500 --> 00:37:47.000
 lower to overcome this problem.

643
00:37:48.100 --> 00:37:51.600
If you do upper we use

644
00:37:51.600 --> 00:37:54.000
 upper method we can write this.

645
00:37:55.200 --> 00:37:55.800
like this

646
00:37:59.600 --> 00:38:00.400
upper

647
00:38:01.600 --> 00:38:03.500
and making parentheses

648
00:38:10.100 --> 00:38:11.900
if you use the upper method

649
00:38:13.300 --> 00:38:17.600
it will it will capitalize the HTTP server

650
00:38:16.600 --> 00:38:18.000
 information?

651
00:38:19.300 --> 00:38:22.700
So it will make the all

652
00:38:22.700 --> 00:38:26.400
 letter in uppercase

653
00:38:25.400 --> 00:38:29.100
 and this word

654
00:38:28.100 --> 00:38:30.500
 Apache.

655
00:38:31.300 --> 00:38:35.000
You can see the this will in

656
00:38:34.300 --> 00:38:38.900
 a format with a uppercase so

657
00:38:38.900 --> 00:38:39.500
 we will.

658
00:38:41.100 --> 00:38:41.500
right

659
00:38:42.300 --> 00:38:42.800
with

660
00:38:44.800 --> 00:38:46.100
the letter in uppercase

661
00:38:47.400 --> 00:38:48.900
and we can

662
00:38:50.400 --> 00:38:51.300
search now.

663
00:38:53.700 --> 00:38:56.200
So you can see we have

664
00:38:56.200 --> 00:38:57.700
 the same result.

665
00:39:00.700 --> 00:39:03.900
By the upper method and also

666
00:39:03.900 --> 00:39:07.000
 you can use the lower method with

667
00:39:06.500 --> 00:39:08.100
 the same logic.

668
00:39:10.600 --> 00:39:12.200
and if you use lower

669
00:39:13.400 --> 00:39:14.100
in here

670
00:39:22.400 --> 00:39:22.900
you will.

671
00:39:23.800 --> 00:39:25.500
make lowercase

672
00:39:32.800 --> 00:39:34.500
You will make lowercase.

673
00:39:41.900 --> 00:39:45.300
As you can see we have the same result

674
00:39:44.300 --> 00:39:45.700
 now.

675
00:39:47.400 --> 00:39:50.900
So another filter is called matches. The matches

676
00:39:50.900 --> 00:39:53.500
 filter has a case insensitive feature.

677
00:39:53.500 --> 00:39:57.100
 That's right to filter. We wrote before with

678
00:39:56.100 --> 00:39:58.300
 matches now.

679
00:40:01.300 --> 00:40:03.200
And I will write.

680
00:40:04.200 --> 00:40:04.900
http

681
00:40:06.600 --> 00:40:07.300
server

682
00:40:10.100 --> 00:40:12.300
and instead of contains

683
00:40:13.200 --> 00:40:13.900
filters

684
00:40:14.500 --> 00:40:16.800
I will write matches.

685
00:40:18.400 --> 00:40:21.600
So next filter will be

686
00:40:21.600 --> 00:40:25.600
 applied now, so it isn't important how

687
00:40:24.600 --> 00:40:27.600
 you write the server name

688
00:40:27.600 --> 00:40:30.500
 you can write with the lowercase or

689
00:40:30.500 --> 00:40:33.800
 uppercase or with the

690
00:40:33.800 --> 00:40:36.900
 combination of them that isn't

691
00:40:36.900 --> 00:40:39.700
 important for the matches filter. It

692
00:40:39.700 --> 00:40:42.400
 will find the packets which

693
00:40:42.400 --> 00:40:46.300
 contain Apache to for

694
00:40:45.300 --> 00:40:49.000
 us and now click

695
00:40:48.100 --> 00:40:51.200
 on and enter as you

696
00:40:51.200 --> 00:40:54.800
 can see the same result that we

697
00:40:54.800 --> 00:40:59.000
 have in the Packers pain.

698
00:40:58.700 --> 00:41:01.600
 We have 10 packets and

699
00:41:01.600 --> 00:41:05.400
 they are containing Apache

700
00:41:04.400 --> 00:41:07.400
 name as the server

701
00:41:07.400 --> 00:41:11.300
 name and we have written

702
00:41:10.300 --> 00:41:13.300
 with the lowercase.

703
00:41:14.700 --> 00:41:18.700
The server name because the matches filter

704
00:41:17.700 --> 00:41:20.500
 as a

705
00:41:20.500 --> 00:41:23.100
 case insensitive feature.

706
00:41:26.500 --> 00:41:29.300
So that's all and we can use the

707
00:41:29.300 --> 00:41:32.800
 in filter to see terrific on

708
00:41:32.800 --> 00:41:35.800
 only on certain parts.

709
00:41:37.800 --> 00:41:40.300
For example, if you want to see the traffic

710
00:41:40.300 --> 00:41:47.100
 on TCP ports 80 and 443

711
00:41:43.100 --> 00:41:47.800
 and

712
00:41:47.800 --> 00:41:52.000
 8080, you

713
00:41:51.400 --> 00:41:55.900
 know, these ports are some HTTP

714
00:41:54.900 --> 00:41:56.400
 ports.

715
00:41:57.200 --> 00:41:58.600
We can write in.

716
00:41:59.500 --> 00:42:01.100
filtering field

717
00:42:02.700 --> 00:42:03.500
like this

718
00:42:04.400 --> 00:42:05.700
TCP port

719
00:42:07.800 --> 00:42:08.100
in

720
00:42:11.800 --> 00:42:15.100
so if you will specify more than

721
00:42:14.100 --> 00:42:17.800
 one ports, you will

722
00:42:17.800 --> 00:42:21.400
 use these curly braces like

723
00:42:20.400 --> 00:42:23.600
 in this way and you

724
00:42:23.600 --> 00:42:27.900
 will enter your ports in these curly

725
00:42:26.900 --> 00:42:29.400
 braces, and I

726
00:42:29.400 --> 00:42:32.600
 will enter my port number.

727
00:42:34.300 --> 00:42:36.300
and the other one will be

728
00:42:39.700 --> 00:42:42.700
443 and the

729
00:42:42.700 --> 00:42:43.500
 last one

730
00:42:44.400 --> 00:42:46.300
Is 80 80?

731
00:42:49.400 --> 00:42:53.400
So I want to see the traffic on these TCP

732
00:42:52.400 --> 00:42:54.000
 ports.

733
00:42:54.900 --> 00:42:56.800
And click on the enter.

734
00:42:57.400 --> 00:43:00.900
So we can see the packets with any of the ports the

735
00:43:00.900 --> 00:43:03.800
 entered in filtering as

736
00:43:03.800 --> 00:43:04.400
 both.

737
00:43:07.100 --> 00:43:10.800
the destination port and the source Port you can

738
00:43:10.800 --> 00:43:11.000
 see

739
00:43:12.100 --> 00:43:16.000
both of them we can see now.

740
00:43:18.100 --> 00:43:22.200
So we will meet again on the next video and we

741
00:43:21.200 --> 00:43:24.900
 will discuss about the protocol details

742
00:43:24.900 --> 00:43:26.500
 and Analysis.

743
00:43:27.300 --> 00:43:28.800
See you on the next video.
