
The results will now only show HTTP (tcp port 80) traffic. The easiest filter is to type http into the filter bar. The display filter syntax to filter out addresses between 192.168.1.1 – 192.168.1.255 would be ip.addr=192.168.1.0/24 and if you are comfortable with IP subnetting, you can alter the /24 to change the range. As seen here, you can filter on MAC address, IP address, Subnet or protocol. However, if the addresses are contiguous or in the same subnet, you might be able to get away with a subnet filter. A capture filter will limit the amount of data that is. One time-consuming approach would be to literally type out all the addresses you want to filter on. Wireshark has two filter syntaxes, a capture syntax similar to tcpdump, and a display syntax. In this video, I respond to a question from one of my readers who wanted to create a display filter for many IP addresses.

In either case, you will need to use a display filter to narrow the traffic down.

Even when you have a capture filter, it may be too generic. You may not know what to focus on when you capture packets, resulting in no capture filter. A display filter is configured after you have captured your packets. A capture filter is configured prior to starting your capture and affects what packets are captured. Note that in Wireshark, display and capture filter syntax are completely different. In this video, I review the two most common filters in Wireshark. Since we are not specifying a source or destination (i.e. One of the keys to being an effective network troubleshooter when using a protocol analyzer is the ability to see patterns, which is where filters come into play. You can use this wireshark filter to restrict results to the network you are interested in: ip.addr 10.10.0.0/16.
