This can quickly become messy unless we use a Wireshark Filter. Therefore, you will have to deal with tons of information, particularly in a production network.

However, as we have seen in the previous article, it literally collects all the traffic. To do that, it shows you all the traffic you send and receive on a Network interface. Very powerful tools indeed.Wireshark is a powerful tool: it allows you to see what’s going on in a network. As a result, to ensure that DNS packets appear when searching for domain names, the filter frame contains “google” should be used instead of frame contains “”. Note that DNS records use various separators in place of literal dots “.”. For example, if I wanted to find my dns query for dns and frame contains 'cloudshark' Last but not least, you can of course always use the concatenation operators. You can even get more specific, using the “contains” filter to look at specific parts of a frame, such as tcp contains or eth contains. For example, if I only want to view the DNS query with transaction ID Oxb413: The frame contains feature can also be used for Hex values. Take a look at this capture with the above filter applied: …will show you only those packets that contain the word “cloudshark” somewhere in them.ĬloudShark lets you embed these filters right in the URL that you share. The “frame contains” filter will let you pick out only those packets that contain a sequence of any ASCII or Hex value that you specify. You may know the common ones, such as searching on ip address or tcp port, or even protocol but did you know you can search for any ASCII or Hex values in any field throughout the capture? The great thing about CloudShark’s capture decode is that it supports all of the standard Wireshark display filters.

Wireshark filters for protocol