Gecko [ dataharbor.africa ]

Name	Size	Permission
?;diameter	[ DIR ]	drwxr-xr-x
?;dtds	[ DIR ]	drwxr-xr-x
?;help	[ DIR ]	drwxr-xr-x
?;profiles	[ DIR ]	drwxr-xr-x
?;radius	[ DIR ]	drwxr-xr-x
?;tpncp	[ DIR ]	drwxr-xr-x
?;wimaxasncp	[ DIR ]	drwxr-xr-x
AUTHORS-SHORT	38.39 KB	-rw-r--r--
COPYING	26.62 KB	-rw-r--r--
capinfos.html	12.64 KB	-rw-r--r--
cfilters	515 B	-rw-r--r--
colorfilters	1.82 KB	-rw-r--r--
console.lua	3.41 KB	-rw-r--r--
dfilters	659 B	-rw-r--r--
dftest.html	1.24 KB	-rw-r--r--
dtd_gen.lua	8.18 KB	-rw-r--r--
dumpcap.html	17.06 KB	-rw-r--r--
editcap.html	16.05 KB	-rw-r--r--
ipmap.html	4.05 KB	-rw-r--r--
manuf	1.41 MB	-rw-r--r--
mergecap.html	7.15 KB	-rw-r--r--
pdml2html.xsl	5.92 KB	-rw-r--r--
randpkt.html	3.96 KB	-rw-r--r--
rawshark.html	23.49 KB	-rw-r--r--
reordercap.html	2.85 KB	-rw-r--r--
services	918.31 KB	-rw-r--r--
smi_modules	315 B	-rw-r--r--
text2pcap.html	11.16 KB	-rw-r--r--
tshark.html	79.91 KB	-rw-r--r--
wireshark-filter.html	17.43 KB	-rw-r--r--
wireshark.html	155.65 KB	-rw-r--r--
ws.css	3.82 KB	-rw-r--r--

Code Editor : wireshark-filter.html

<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>wireshark-filter - The Wireshark Network Analyzer 1.10.14</title>
<link rel="stylesheet" href="../docbook/ws.css" type="text/css" />
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>

<body>

wireshark-filter - Wireshark filter syntax and reference

<h1 id="SYNOPSIS">SYNOPSIS</h1>

wireshark [other options] [ -R &quot;filter expression&quot; ]

tshark [other options] [ -R &quot;filter expression&quot; ]

<h1 id="DESCRIPTION">DESCRIPTION</h1>

Wireshark and TShark share a powerful filter engine that helps remove the noise from a packet trace and lets you see only the packets that interest you. If a packet meets the requirements expressed in your filter, then it is displayed in the list of packets. Display filters let you compare the fields within a protocol against a specific value, compare fields against fields, and check the existence of specified fields or protocols.

Filters are also used by other features such as statistics generation and packet list colorization (the latter is only available to Wireshark). This manual page describes their syntax. A comprehensive reference of filter fields can be found within Wireshark and in the display filter reference at <a href="http://www.wireshark.org/docs/dfref/">http://www.wireshark.org/docs/dfref/</a>.

<h1 id="FILTER-SYNTAX">FILTER SYNTAX</h1>

<h2 id="Check-whether-a-field-or-protocol-exists">Check whether a field or protocol exists</h2>

The simplest filter allows you to check for the existence of a protocol or field. If you want to see all packets which contain the IP protocol, the filter would be &quot;ip&quot; (without the quotation marks). To see all packets that contain a Token-Ring RIF field, use &quot;tr.rif&quot;.

Think of a protocol or field in a filter as implicitly having the &quot;exists&quot; operator.

<h2 id="Comparison-operators">Comparison operators</h2>

Fields can also be compared against values. The comparison operators can be expressed either through English-like abbreviations or through C-like symbols:

<pre><code> eq, == Equal
 ne, != Not Equal
 gt, &gt; Greater Than
 lt, &lt; Less Than
 ge, &gt;= Greater than or Equal to
 le, &lt;= Less than or Equal to</code></pre>

<h2 id="Search-and-match-operators">Search and match operators</h2>

Additional operators exist expressed only in English, not C-like syntax:

<pre><code> contains Does the protocol, field or slice contain a value
 matches Does the protocol or text string match the given Perl
 regular expression</code></pre>

The &quot;contains&quot; operator allows a filter to search for a sequence of characters, expressed as a string (quoted or unquoted), or bytes, expressed as a byte array. For example, to search for a given HTTP URL in a capture, the following filter can be used:

<pre><code> http contains &quot;http://www.wireshark.org&quot;</code></pre>

The &quot;contains&quot; operator cannot be used on atomic fields, such as numbers or IP addresses.

The &quot;matches&quot; operator allows a filter to apply to a specified Perl-compatible regular expression (PCRE). The &quot;matches&quot; operator is only implemented for protocols and for protocol fields with a text string representation. For example, to search for a given WAP WSP User-Agent, you can write:

<pre><code> wsp.user_agent matches &quot;(?i)cldc&quot;</code></pre>

This example shows an interesting PCRE feature: pattern match options have to be specified with the (?option) construct. For instance, (?i) performs a case-insensitive pattern match. More information on PCRE can be found in the pcrepattern(3) man page (Perl Regular Expressions are explained in <a href="http://perldoc.perl.org/perlre.html">http://perldoc.perl.org/perlre.html</a>).

<h2 id="Functions">Functions</h2>

The filter language has the following functions:

<pre><code> upper(string-field) - converts a string field to uppercase
 lower(string-field) - converts a string field to lowercase</code></pre>

upper() and lower() are useful for performing case-insensitive string comparisons. For example:

<pre><code> upper(ncp.nds_stream_name) contains &quot;MACRO&quot;
 lower(mount.dump.hostname) == &quot;angel&quot;</code></pre>

<h2 id="Protocol-field-types">Protocol field types</h2>

Each protocol field is typed. The types are:

<pre><code> ASN.1 object identifier
 Boolean
 Character string
 Compiled Perl-Compatible Regular Expression (GRegex) object
 Date and time
 Ethernet or other MAC address
 EUI64 address
 Floating point (double-precision)
 Floating point (single-precision)
 Frame number
 Globally Unique Identifier
 IPv4 address
 IPv6 address
 IPX network number
 Label
 Protocol
 Sequence of bytes
 Signed integer, 1, 2, 3, 4, or 8 bytes
 Time offset
 Unsigned integer, 1, 2, 3, 4, or 8 bytes</code></pre>

An integer may be expressed in decimal, octal, or hexadecimal notation. The following three display filters are equivalent:

<pre><code> frame.pkt_len &gt; 10
 frame.pkt_len &gt; 012
 frame.pkt_len &gt; 0xa</code></pre>

Boolean values are either true or false. In a display filter expression testing the value of a Boolean field, &quot;true&quot; is expressed as 1 or any other non-zero value, and &quot;false&quot; is expressed as zero. For example, a token-ring packet&#39;s source route field is Boolean. To find any source-routed packets, a display filter would be:

Non source-routed packets can be found with:

Ethernet addresses and byte arrays are represented by hex digits. The hex digits may be separated by colons, periods, or hyphens:

IPv4 addresses can be represented in either dotted decimal notation or by using the hostname:

IPv4 addresses can be compared with the same logical relations as numbers: eq, ne, gt, ge, lt, and le. The IPv4 address is stored in host order, so you do not have to worry about the endianness of an IPv4 address when using it in a display filter.

Classless InterDomain Routing (CIDR) notation can be used to test if an IPv4 address is in a certain subnet. For example, this display filter will find all packets in the 129.111 Class-B network:

Remember, the number after the slash represents the number of bits used to represent the network. CIDR notation can also be used with hostnames, as in this example of finding IP addresses on the same Class C network as &#39;sneezy&#39;:

<pre><code> ip.addr eq sneezy/24</code></pre>

The CIDR notation can only be used on IP addresses or hostnames, not in variable names. So, a display filter like &quot;ip.src/24 == ip.dst/24&quot; is not valid (yet).

IPX networks are represented by unsigned 32-bit integers. Most likely you will be using hexadecimal when testing IPX network values:

Strings are enclosed in double quotes:

<pre><code> http.request.method == &quot;POST&quot;</code></pre>

Inside double quotes, you may use a backslash to embed a double quote or an arbitrary byte represented in either octal or hexadecimal.

<pre><code> browser.comment == &quot;An embedded \&quot; double-quote&quot;</code></pre>

Use of hexadecimal to look for &quot;HEAD&quot;:

<pre><code> http.request.method == &quot;\x48EAD&quot;</code></pre>

Use of octal to look for &quot;HEAD&quot;:

<pre><code> http.request.method == &quot;\110EAD&quot;</code></pre>

This means that you must escape backslashes with backslashes inside double quotes.

<pre><code> smb.path contains &quot;\\\\SERVER\\SHARE&quot;</code></pre>

looks for \\SERVER\SHARE in &quot;smb.path&quot;.

<h2 id="The-slice-operator">The slice operator</h2>

You can take a slice of a field if the field is a text string or a byte array. For example, you can filter on the vendor portion of an ethernet address (the first three bytes) like this:

Another example is:

<pre><code> http.content_type[0:4] == &quot;text&quot;</code></pre>

You can use the slice operator on a protocol name, too. The &quot;frame&quot; protocol can be useful, encompassing all the data captured by Wireshark or TShark.

<pre><code> token[0:5] ne 0.0.0.1.1
 llc[0] eq aa
 frame[100-199] contains &quot;wireshark&quot;</code></pre>

The following syntax governs slices:

<pre><code> [i:j] i = start_offset, j = length
 [i-j] i = start_offset, j = end_offset, inclusive.
 [i] i = start_offset, length = 1
 [:j] start_offset = 0, length = j
 [i:] start_offset = i, end_offset = end_of_field</code></pre>

Offsets can be negative, in which case they indicate the offset from the end of the field. The last byte of the field is at offset -1, the last but one byte is at offset -2, and so on. Here&#39;s how to check the last four bytes of a frame:

<pre><code> frame[-4:4] == 0.1.2.3</code></pre>

or

<pre><code> frame[-4:] == 0.1.2.3</code></pre>

A slice is alwasy compared against either a string or a byte sequence. As a special case, when the slice is only 1 byte wide, you can compare it against a hex integer that 0xff or less (which means it fits inside one byte). This is not allowed for byte sequences greater than one byte, because then one would need to specify the endianness of the multi-byte integer. Also, this is not allowed for decimal numbers, since they would be confused with hex numbers that are already allowed as byte strings. Neverthelss, single-byte hex integers can be convienent:

<pre><code> frame[4] == 0xff</code></pre>

Slices can be combined. You can concatenate them using the comma operator:

This concatenates offset 1, offsets 3-5, and offset 9 to the end of the ftp data.

<h2 id="Type-conversions">Type conversions</h2>

If a field is a text string or a byte array, it can be expressed in whichever way is most convenient.

So, for instance, the following filters are equivalent:

<pre><code> http.request.method == &quot;GET&quot;
 http.request.method == 47.45.54</code></pre>

A range can also be expressed in either way:

<pre><code> frame[60:2] gt 50.51
 frame[60:2] gt &quot;PQ&quot;</code></pre>

<h2 id="Bit-field-operations">Bit field operations</h2>

It is also possible to define tests with bit field operations. Currently the following bit field operation is supported:

<pre><code> bitwise_and, &amp; Bitwise AND</code></pre>

The bitwise AND operation allows testing to see if one or more bits are set. Bitwise AND operates on integer protocol fields and slices.

When testing for TCP SYN packets, you can write:

<pre><code> tcp.flags &amp; 0x02</code></pre>

That expression will match all packets that contain a &quot;tcp.flags&quot; field with the 0x02 bit, i.e. the SYN bit, set.

Similarly, filtering for all WSP GET and extended GET methods is achieved with:

When using slices, the bit mask must be specified as a byte string, and it must have the same number of bytes as the slice itself, as in:

<h2 id="Logical-expressions">Logical expressions</h2>

Tests can be combined using logical expressions. These too are expressible in C-like syntax or with English-like abbreviations:

<pre><code> and, &amp;&amp; Logical AND
 or, || Logical OR
 not, ! Logical NOT</code></pre>

Expressions can be grouped by parentheses as well. The following are all valid display filter expressions:

<pre><code> tcp.port == 80 and ip.src == 192.168.2.1
 not llc
 http and frame[100-199] contains &quot;wireshark&quot;
 (ipx.src.net == 0xbad &amp;&amp; ipx.src.node == 0.0.0.0.0.1) || ip</code></pre>

Remember that whenever a protocol or field name occurs in an expression, the &quot;exists&quot; operator is implicitly called. The &quot;exists&quot; operator has the highest priority. This means that the first filter expression must be read as &quot;show me the packets for which tcp.port exists and equals 80, and ip.src exists and equals 192.168.2.1&quot;. The second filter expression means &quot;show me the packets where not (llc exists)&quot;, or in other words &quot;where llc does not exist&quot; and hence will match all packets that do not contain the llc protocol. The third filter expression includes the constraint that offset 199 in the frame exists, in other words the length of the frame is at least 200.

A special caveat must be given regarding fields that occur more than once per packet. &quot;ip.addr&quot; occurs twice per IP packet, once for the source address, and once for the destination address. Likewise, &quot;tr.rif.ring&quot; fields can occur more than once per packet. The following two expressions are not equivalent:

The first filter says &quot;show me packets where an ip.addr exists that does not equal 192.168.4.1&quot;. That is, as long as one ip.addr in the packet does not equal 192.168.4.1, the packet passes the display filter. The other ip.addr could equal 192.168.4.1 and the packet would still be displayed. The second filter says &quot;don&#39;t show me any packets that have an ip.addr field equal to 192.168.4.1&quot;. If one ip.addr is 192.168.4.1, the packet does not pass. If neither ip.addr field is 192.168.4.1, then the packet is displayed.

It is easy to think of the &#39;ne&#39; and &#39;eq&#39; operators as having an implicit &quot;exists&quot; modifier when dealing with multiply-recurring fields. &quot;ip.addr ne 192.168.4.1&quot; can be thought of as &quot;there exists an ip.addr that does not equal 192.168.4.1&quot;. &quot;not ip.addr eq 192.168.4.1&quot; can be thought of as &quot;there does not exist an ip.addr equal to 192.168.4.1&quot;.

Be careful with multiply-recurring fields; they can be confusing.

Care must also be taken when using the display filter to remove noise from the packet trace. If, for example, you want to filter out all IP multicast packets to address 224.1.2.3, then using:

may be too restrictive. Filtering with &quot;ip.dst&quot; selects only those IP packets that satisfy the rule. Any other packets, including all non-IP packets, will not be displayed. To display the non-IP packets as well, you can use one of the following two expressions:

The first filter uses &quot;not ip&quot; to include all non-IP packets and then lets &quot;ip.dst ne 224.1.2.3&quot; filter out the unwanted IP packets. The second filter has already been explained above where filtering with multiply occurring fields was discussed.

<h1 id="FILTER-FIELD-REFERENCE">FILTER FIELD REFERENCE</h1>

The entire list of display filters is too large to list here. You can can find references and examples at the following locations:

<ul>

<li>The online Display Filter Reference: <a href="http://www.wireshark.org/docs/dfref/">http://www.wireshark.org/docs/dfref/</a>

</li>
<li>Help:Supported Protocols in Wireshark

</li>
<li><code>tshark -G fields</code> on the command line

</li>
<li>The Wireshark wiki: <a href="http://wiki.wireshark.org/DisplayFilters">http://wiki.wireshark.org/DisplayFilters</a>

</li>
</ul>

<h1 id="NOTES">NOTES</h1>

The wireshark-filters manpage is part of the Wireshark distribution. The latest version of Wireshark can be found at <a href="http://www.wireshark.org">http://www.wireshark.org</a>.

Regular expressions in the &quot;matches&quot; operator are provided by GRegex in GLib. See <a href="http://developer.gnome.org/glib/2.32/glib-regex-syntax.html/">http://developer.gnome.org/glib/2.32/glib-regex-syntax.html/</a> or <a href="http://www.pcre.org/">http://www.pcre.org/</a> for more information.

This manpage does not describe the capture filter syntax, which is different. See the manual page of pcap-filter(7) or, if that doesn&#39;t exist, tcpdump(8), or, if that doesn&#39;t exist, <a href="http://wiki.wireshark.org/CaptureFilters">http://wiki.wireshark.org/CaptureFilters</a> for a description of capture filters.

wireshark(1), tshark(1), editcap(1), pcap(3), pcap-filter(7) or tcpdump(8) if it doesn&#39;t exist.

<h1 id="AUTHORS">AUTHORS</h1>

See the list of authors in the Wireshark man page for a list of authors of that code.

</body>

</html>

${this.title}

Code Editor : wireshark-filter.html