You can set this type of filter before initiating a capture operation and later adjust or cancel it. Ip.addr = 153.11.105.34/31 or ip.addr = 153.11.105.36/31 or ip.addr = 153.11.105.On the other hand, display filters contain parameters that apply to all captured packets. You could also combine a mix of explicit addresses and a smaller subnets: a subnet, unfortunately your range of addresses doesn't map neatly so you'll have to use a slightly bigger subnet, e.g.ip.addr = 1.2.3.0/24 filters any packets in the 1.2.3.4.0 class c subnet.Īssuming you're trying to create a display filter for address in the range 153.11.105.34 - 38 you can either use:.ip.addr = 1.2.3.4 or ip.addr = myhost filters any packets to or from the ip address or host name.1.2.3.0/24ĭisplay syntax is explained here and uses a form of ip.xxx = 1.2.3.4, e.g: net - identifies a network of addresses, usually in CIDR notation, e.g.host- identifies a particular host, if a name, the resolved ip(s) are all used, if an ip, then that is used.

You seem to be confused by the differing syntaxes of capture and display filters.Ĭapture filter syntax is explained here, and allows use of the following keywords to identify ip addresses: Refer to the pcap-filter man page for more information. They are pcap-filter capture filter syntax and can't be used in this context. Refer to the wireshark-filter man page for more information.Īs the red color indicates, the following are not valid Wireshark display filter syntax. ip contains 153.11.105.34/38 Again, /38 is invalid, but also the contains operator does not work with IP addresses.ip.address = 153.11.105.34 or 153.11.105.35 This is invalid because there is no field called 'ip.address' and you need to specify the field name for the second IP address too.(Ideally, the Wireshark display filter validation could be improved to detect this and turn the expression red instead of green.) ip.addr = 153.11.105.34/38 This is invalid because the maximum number of bits is /32.

Wireshark ip range display filter