Now we put “tcp.port = 443” as Wireshark filter and see only HTTPS packets. Now we put “udp.port = 53” as Wireshark filter and see only packets where port is 53.ģ. Here 192.168.1.6 is trying to send DNS query. Now we put “tcp.port = 80” as Wireshark filter and see only packets where port is 80.Ģ. Here 192.168.1.6 is trying to access web server where HTTP server is running. Ports 1024 to 49151 are Registered Ports.īefore we use filter in Wireshark we should know what port is used for which protocol.In this article we will try to understand some well know ports through Wireshark analysis. To know more about filter by IP in Wireshark, please follow below link: Not (ip.addr=176.31.239.201 or ip.addr=192.168.0.1 or ip.addr=10.10.10.Port filtering is the way of filtering packets based on port number. This filter will find the HEX values of 0x03 0x28 0x58 at any offset in the packet trace. This filter will find and display all HTTP GET requests. This creates a filter to display all icmp and dns packets in the trace. This is helpful when tracking down slow application performance and packet loss. This filter will display all retransmissions in the trace. This is a great way to remove protocols from the view that are not involved with troubleshooting thus allowing you to focus on the traffic that may be the problem. This filter will mask out arp, icmp, or dns protocols.

Very helpful when searching on a specific string or user ID, for example. This filter will find and display all TCP packets that contain the word ‘test’.

This creates a filter for any TCP packet with 5000 as a source or destination port. This filter will find and display all TCP resets. This creates a conversation filter between the two defined IP addresses.

This filters for any packet with 172.16.1.1, as either the source or destination.

Wireshark filter by destination ip