4 tshark - Dump and analyze network traffic
10 S<[ B<-a> E<lt>capture autostop conditionE<gt> ] ...>
11 S<[ B<-b> E<lt>capture ring buffer optionE<gt>] ...>
12 S<[ B<-B> E<lt>capture buffer sizeE<gt> ] >
13 S<[ B<-c> E<lt>capture packet countE<gt> ]>
14 S<[ B<-C> E<lt>configuration profileE<gt> ]>
15 S<[ B<-d> E<lt>layer typeE<gt>==E<lt>selectorE<gt>,E<lt>decode-as protocolE<gt> ]>
17 S<[ B<-e> E<lt>fieldE<gt> ]>
18 S<[ B<-E> E<lt>field print optionE<gt> ]>
19 S<[ B<-f> E<lt>capture filterE<gt> ]>
20 S<[ B<-F> E<lt>file formatE<gt> ]>
23 S<[ B<-H> E<lt>input hosts fileE<gt> ]>
24 S<[ B<-i> E<lt>capture interfaceE<gt>|- ]>
25 S<[ B<-j> E<lt>protocol match filterE<gt> ]>
27 S<[ B<-K> E<lt>keytabE<gt> ]>
31 S<[ B<-N> E<lt>name resolving flagsE<gt> ]>
32 S<[ B<-o> E<lt>preference settingE<gt> ] ...>
33 S<[ B<-O> E<lt>protocolsE<gt> ]>
38 S<[ B<-r> E<lt>infileE<gt> ]>
39 S<[ B<-R> E<lt>Read filterE<gt> ]>
40 S<[ B<-s> E<lt>capture snaplenE<gt> ]>
41 S<[ B<-S> E<lt>separatorE<gt> ]>
42 S<[ B<-t> a|ad|adoy|d|dd|e|r|u|ud|udoy ]>
43 S<[ B<-T> ek|fields|json|pdml|ps|psml|tabs|text ]>
44 S<[ B<-u> E<lt>seconds typeE<gt>]>
45 S<[ B<-U> E<lt>tap_nameE<gt>]>
48 S<[ B<-w> E<lt>outfileE<gt>|- ]>
49 S<[ B<-W> E<lt>file format optionE<gt>]>
51 S<[ B<-X> E<lt>eXtension optionE<gt>]>
52 S<[ B<-y> E<lt>capture link typeE<gt> ]>
53 S<[ B<-Y> E<lt>displaY filterE<gt> ]>
54 S<[ B<-M> E<lt>auto session resetE<gt> ]>
55 S<[ B<-z> E<lt>statisticsE<gt> ]>
56 S<[ B<--capture-comment> E<lt>commentE<gt> ]>
57 S<[ B<--list-time-stamp-types> ]>
58 S<[ B<--time-stamp-type> E<lt>typeE<gt> ]>
60 S<[ B<--no-duplicate-keys> ]>
61 S<[ B<--export-objects> E<lt>protocolE<gt>,E<lt>destdirE<gt> ]>
62 S<[ B<--enable-protocol> E<lt>proto_nameE<gt> ]>
63 S<[ B<--disable-protocol> E<lt>proto_nameE<gt> ]>
64 S<[ B<--enable-heuristic> E<lt>short_nameE<gt> ]>
65 S<[ B<--disable-heuristic> E<lt>short_nameE<gt> ]>
66 S<[ E<lt>capture filterE<gt> ]>
69 B<-G> [ E<lt>report typeE<gt> ]
73 B<TShark> is a network protocol analyzer. It lets you capture packet
74 data from a live network, or read packets from a previously saved
75 capture file, either printing a decoded form of those packets to the
76 standard output or writing the packets to a file. B<TShark>'s native
77 capture file format is B<pcap> format, which is also the format used
78 by B<tcpdump> and various other tools.
80 Without any options set, B<TShark> will work much like B<tcpdump>. It will
81 use the pcap library to capture traffic from the first available network
82 interface and displays a summary line on stdout for each received packet.
84 B<TShark> is able to detect, read and write the same capture files that
85 are supported by B<Wireshark>.
86 The input file doesn't need a specific filename extension; the file
87 format and an optional gzip compression will be automatically detected.
88 Near the beginning of the DESCRIPTION section of wireshark(1) or
89 L<https://www.wireshark.org/docs/man-pages/wireshark.html>
90 is a detailed description of the way B<Wireshark> handles this, which is
91 the same way B<Tshark> handles this.
93 Compressed file support uses (and therefore requires) the zlib library.
94 If the zlib library is not present, B<TShark> will compile, but will
95 be unable to read compressed files.
97 If the B<-w> option is not specified, B<TShark> writes to the standard
98 output the text of a decoded form of the packets it captures or reads.
99 If the B<-w> option is specified, B<TShark> writes to the file
100 specified by that option the raw data of the packets, along with the
101 packets' time stamps.
103 When writing a decoded form of packets, B<TShark> writes, by
104 default, a summary line containing the fields specified by the
105 preferences file (which are also the fields displayed in the packet list
106 pane in B<Wireshark>), although if it's writing packets as it captures
107 them, rather than writing packets from a saved capture file, it won't
108 show the "frame number" field. If the B<-V> option is specified, it
109 writes instead a view of the details of the packet, showing all the
110 fields of all protocols in the packet. If the B<-O> option is specified,
111 it will only show the full protocols specified. Use the output of
112 "B<tshark -G protocols>" to find the abbreviations of the protocols you can
115 If you want to write the decoded form of packets to a file, run
116 B<TShark> without the B<-w> option, and redirect its standard output to
117 the file (do I<not> use the B<-w> option).
119 When writing packets to a file, B<TShark>, by default, writes the
120 file in B<pcap> format, and writes all of the packets it sees to the
121 output file. The B<-F> option can be used to specify the format in which
122 to write the file. This list of available file formats is displayed by
123 the B<-F> flag without a value. However, you can't specify a file format
126 Read filters in B<TShark>, which allow you to select which packets
127 are to be decoded or written to a file, are very powerful; more fields
128 are filterable in B<TShark> than in other protocol analyzers, and the
129 syntax you can use to create your filters is richer. As B<TShark>
130 progresses, expect more and more protocol fields to be allowed in read
133 Packet capturing is performed with the pcap library. The capture filter
134 syntax follows the rules of the pcap library. This syntax is different
135 from the read filter syntax. A read filter can also be specified when
136 capturing, and only packets that pass the read filter will be displayed
137 or saved to the output file; note, however, that capture filters are much
138 more efficient than read filters, and it may be more difficult for
139 B<TShark> to keep up with a busy network if a read filter is
140 specified for a live capture.
142 A capture or read filter can either be specified with the B<-f> or B<-R>
143 option, respectively, in which case the entire filter expression must be
144 specified as a single argument (which means that if it contains spaces,
145 it must be quoted), or can be specified with command-line arguments
146 after the option arguments, in which case all the arguments after the
147 filter arguments are treated as a filter expression. Capture filters
148 are supported only when doing a live capture; read filters are supported
149 when doing a live capture and when reading a capture file, but require
150 TShark to do more work when filtering, so you might be more likely to
151 lose packets under heavy load if you're using a read filter. If the
152 filter is specified with command-line arguments after the option
153 arguments, it's a capture filter if a capture is being done (i.e., if no
154 B<-r> option was specified) and a read filter if a capture file is being
155 read (i.e., if a B<-r> option was specified).
157 The B<-G> option is a special mode that simply causes B<Tshark>
158 to dump one of several types of internal glossaries and then exit.
166 Perform a two-pass analysis. This causes tshark to buffer output until the
167 entire first pass is done, but allows it to fill in fields that require future
168 knowledge, such as 'response in frame #' fields. Also permits reassembly
169 frame dependencies to be calculated correctly.
171 =item -a E<lt>capture autostop conditionE<gt>
173 Specify a criterion that specifies when B<TShark> is to stop writing
174 to a capture file. The criterion is of the form I<test>B<:>I<value>,
175 where I<test> is one of:
177 B<duration>:I<value> Stop writing to a capture file after I<value> seconds
180 B<filesize>:I<value> Stop writing to a capture file after it reaches a size of
181 I<value> kB. If this option is used together with the -b option, B<TShark>
182 will stop writing to the current capture file and switch to the next one if
183 filesize is reached. When reading a capture file, B<TShark> will stop reading
184 the file after the number of bytes read exceeds this number (the complete
185 packet will be read, so more bytes than this number may be read). Note that
186 the filesize is limited to a maximum value of 2 GiB.
188 B<files>:I<value> Stop writing to capture files after I<value> number of files
191 =item -b E<lt>capture ring buffer optionE<gt>
193 Cause B<TShark> to run in "multiple files" mode. In "multiple files" mode,
194 B<TShark> will write to several capture files. When the first capture file
195 fills up, B<TShark> will switch writing to the next file and so on.
197 The created filenames are based on the filename given with the B<-w> option,
198 the number of the file and on the creation date and time,
199 e.g. outfile_00001_20050604120117.pcap, outfile_00002_20050604120523.pcap, ...
201 With the I<files> option it's also possible to form a "ring buffer".
202 This will fill up new files until the number of files specified,
203 at which point B<TShark> will discard the data in the first file and start
204 writing to that file and so on. If the I<files> option is not set,
205 new files filled up until one of the capture stop conditions match (or
206 until the disk is full).
208 The criterion is of the form I<key>B<:>I<value>,
209 where I<key> is one of:
211 B<duration>:I<value> switch to the next file after I<value> seconds have
212 elapsed, even if the current file is not completely filled up.
214 B<interval>:I<value> switch to the next file when the time is an exact
215 multiple of I<value> seconds
217 B<filesize>:I<value> switch to the next file after it reaches a size of
218 I<value> kB. Note that the filesize is limited to a maximum value of 2 GiB.
220 B<files>:I<value> begin again with the first file after I<value> number of
221 files were written (form a ring buffer). This value must be less than 100000.
222 Caution should be used when using large numbers of files: some filesystems do
223 not handle many files in a single directory well. The B<files> criterion
224 requires either B<duration>, B<interval> or B<filesize> to be specified to
225 control when to go to the next file. It should be noted that each B<-b>
226 parameter takes exactly one criterion; to specify two criterion, each must be
227 preceded by the B<-b> option.
229 Example: B<-b filesize:1000 -b files:5> results in a ring buffer of five files
230 of size one megabyte each.
232 =item -B E<lt>capture buffer sizeE<gt>
234 Set capture buffer size (in MiB, default is 2 MiB). This is used by
235 the capture driver to buffer packet data until that data can be written
236 to disk. If you encounter packet drops while capturing, try to increase
237 this size. Note that, while B<Tshark> attempts to set the buffer size
238 to 2 MiB by default, and can be told to set it to a larger value, the
239 system or interface on which you're capturing might silently limit the
240 capture buffer size to a lower value or raise it to a higher value.
242 This is available on UNIX systems with libpcap 1.0.0 or later and on
243 Windows. It is not available on UNIX systems with earlier versions of
246 This option can occur multiple times. If used before the first
247 occurrence of the B<-i> option, it sets the default capture buffer size.
248 If used after an B<-i> option, it sets the capture buffer size for
249 the interface specified by the last B<-i> option occurring before
250 this option. If the capture buffer size is not set specifically,
251 the default capture buffer size is used instead.
253 =item -c E<lt>capture packet countE<gt>
255 Set the maximum number of packets to read when capturing live
256 data. If reading a capture file, set the maximum number of packets to read.
258 =item -C E<lt>configuration profileE<gt>
260 Run with the given configuration profile.
262 =item -d E<lt>layer typeE<gt>==E<lt>selectorE<gt>,E<lt>decode-as protocolE<gt>
264 Like Wireshark's B<Decode As...> feature, this lets you specify how a
265 layer type should be dissected. If the layer type in question (for example,
266 B<tcp.port> or B<udp.port> for a TCP or UDP port number) has the specified
267 selector value, packets should be dissected as the specified protocol.
269 Example: B<-d tcp.port==8888,http> will decode any traffic running over
270 TCP port 8888 as HTTP.
272 Example: B<-d tcp.port==8888:3,http> will decode any traffic running over
273 TCP ports 8888, 8889 or 8890 as HTTP.
275 Example: B<-d tcp.port==8888-8890,http> will decode any traffic running over
276 TCP ports 8888, 8889 or 8890 as HTTP.
278 Using an invalid selector or protocol will print out a list of valid selectors
279 and protocol names, respectively.
281 Example: B<-d .> is a quick way to get a list of valid selectors.
283 Example: B<-d ethertype==0x0800.> is a quick way to get a list of protocols that can be
284 selected with an ethertype.
288 Print a list of the interfaces on which B<TShark> can capture, and
289 exit. For each network interface, a number and an
290 interface name, possibly followed by a text description of the
291 interface, is printed. The interface name or the number can be supplied
292 to the B<-i> option to specify an interface on which to capture.
294 This can be useful on systems that don't have a command to list them
295 (UNIX systems lacking B<ifconfig -a> or Linux systems lacking
296 B<ip link show>). The number can be useful on Windows systems, where
297 the interface name might be a long name or a GUID.
299 Note that "can capture" means that B<TShark> was able to open that
300 device to do a live capture. Depending on your system you may need to
301 run tshark from an account with special privileges (for example, as
302 root) to be able to capture network traffic. If B<TShark -D> is not run
303 from such an account, it will not list any interfaces.
305 =item -e E<lt>fieldE<gt>
307 Add a field to the list of fields to display if B<-T ek|fields|json|pdml>
308 is selected. This option can be used multiple times on the command line.
309 At least one field must be provided if the B<-T fields> option is
310 selected. Column names may be used prefixed with "_ws.col."
312 Example: B<-e frame.number -e ip.addr -e udp -e _ws.col.Info>
314 Giving a protocol rather than a single field will print multiple items
315 of data about the protocol as a single field. Fields are separated by
316 tab characters by default. B<-E> controls the format of the printed
319 =item -E E<lt>field print optionE<gt>
321 Set an option controlling the printing of fields when B<-T fields> is
326 B<bom=y|n> If B<y>, prepend output with the UTF-8 byte order mark
327 (hexadecimal ef, bb, bf). Defaults to B<n>.
329 B<header=y|n> If B<y>, print a list of the field names given using B<-e>
330 as the first line of the output; the field name will be separated using
331 the same character as the field values. Defaults to B<n>.
333 B<separator=/t|/s|>E<lt>characterE<gt> Set the separator character to
334 use for fields. If B</t> tab will be used (this is the default), if
335 B</s>, a single space will be used. Otherwise any character that can be
336 accepted by the command line as part of the option may be used.
338 B<occurrence=f|l|a> Select which occurrence to use for fields that have
339 multiple occurrences. If B<f> the first occurrence will be used, if B<l>
340 the last occurrence will be used and if B<a> all occurrences will be used
341 (this is the default).
343 B<aggregator=,|/s|>E<lt>characterE<gt> Set the aggregator character to
344 use for fields that have multiple occurrences. If B<,> a comma will be used
345 (this is the default), if B</s>, a single space will be used. Otherwise
346 any character that can be accepted by the command line as part of the
349 B<quote=d|s|n> Set the quote character to use to surround fields. B<d>
350 uses double-quotes, B<s> single-quotes, B<n> no quotes (the default).
352 =item -f E<lt>capture filterE<gt>
354 Set the capture filter expression.
356 This option can occur multiple times. If used before the first
357 occurrence of the B<-i> option, it sets the default capture filter expression.
358 If used after an B<-i> option, it sets the capture filter expression for
359 the interface specified by the last B<-i> option occurring before
360 this option. If the capture filter expression is not set specifically,
361 the default capture filter expression is used if provided.
363 Pre-defined capture filter names, as shown in the GUI menu item Capture->Capture Filters,
364 can be used by prefixing the argument with "predef:".
365 Example: B<-f "predef:MyPredefinedHostOnlyFilter">
367 =item -F E<lt>file formatE<gt>
369 Set the file format of the output capture file written using the B<-w>
370 option. The output written with the B<-w> option is raw packet data, not
371 text, so there is no B<-F> option to request text output. The option B<-F>
372 without a value will list the available formats.
376 This option causes the output file(s) to be created with group-read permission
377 (meaning that the output file(s) can be read by other members of the calling
380 =item -G [ E<lt>report typeE<gt> ]
382 The B<-G> option will cause B<Tshark> to dump one of several types of glossaries
383 and then exit. If no specific glossary type is specified, then the B<fields> report will be generated by default.
385 The available report types include:
387 B<column-formats> Dumps the column formats understood by tshark.
388 There is one record per line. The fields are tab-delimited.
390 * Field 1 = format string (e.g. "%rD")
391 * Field 2 = text description of format string (e.g. "Dest port (resolved)")
393 B<currentprefs> Dumps a copy of the current preferences file to stdout.
395 B<decodes> Dumps the "layer type"/"decode as" associations to stdout.
396 There is one record per line. The fields are tab-delimited.
398 * Field 1 = layer type, e.g. "tcp.port"
399 * Field 2 = selector in decimal
400 * Field 3 = "decode as" name, e.g. "http"
402 B<defaultprefs> Dumps a default preferences file to stdout.
404 B<dissector-tables> Dumps a list of dissector tables to stdout. There
405 is one record per line. The fields are tab-delimited.
407 * Field 1 = dissector table name, e.g. "tcp.port"
408 * Field 2 = name used for the dissector table in the GUI
409 * Field 3 = type (textual representation of the ftenum type)
410 * Field 4 = base for display (for integer types)
412 B<fieldcount> Dumps the number of header fields to stdout.
414 B<fields> Dumps the contents of the registration database to
415 stdout. An independent program can take this output and format it into nice
416 tables or HTML or whatever. There is one record per line. Each record is
417 either a protocol or a header field, differentiated by the first field.
418 The fields are tab-delimited.
423 * Field 2 = descriptive protocol name
424 * Field 3 = protocol abbreviation
429 * Field 2 = descriptive field name
430 * Field 3 = field abbreviation
431 * Field 4 = type (textual representation of the ftenum type)
432 * Field 5 = parent protocol abbreviation
433 * Field 6 = base for display (for integer types); "parent bitfield width" for FT_BOOLEAN
434 * Field 7 = bitmask: format: hex: 0x....
435 * Field 8 = blurb describing field
437 B<folders> Dumps various folders used by tshark. This is essentially the
438 same data reported in Wireshark's About | Folders tab.
439 There is one record per line. The fields are tab-delimited.
441 * Field 1 = Folder type (e.g "Personal configuration:")
442 * Field 2 = Folder location (e.g. "/home/vagrant/.config/wireshark/")
444 B<ftypes> Dumps the "ftypes" (fundamental types) understood by tshark.
445 There is one record per line. The fields are tab-delimited.
447 * Field 1 = FTYPE (e.g "FT_IPv6")
448 * Field 2 = text description of type (e.g. "IPv6 address")
450 B<heuristic-decodes> Dumps the heuristic decodes currently installed.
451 There is one record per line. The fields are tab-delimited.
453 * Field 1 = underlying dissector (e.g. "tcp")
454 * Field 2 = name of heuristic decoder (e.g. ucp")
455 * Field 3 = heuristic enabled (e.g. "T" or "F")
457 B<plugins> Dumps the plugins currently installed.
458 There is one record per line. The fields are tab-delimited.
460 * Field 1 = plugin library (e.g. "gryphon.so")
461 * Field 2 = plugin version (e.g. 0.0.4)
462 * Field 3 = plugin type (e.g. "dissector" or "tap")
463 * Field 4 = full path to plugin file
465 B<protocols> Dumps the protocols in the registration database to stdout.
466 An independent program can take this output and format it into nice tables
467 or HTML or whatever. There is one record per line. The fields are tab-delimited.
469 * Field 1 = protocol name
470 * Field 2 = protocol short name
471 * Field 3 = protocol filter name
473 B<values> Dumps the value_strings, range_strings or true/false strings
474 for fields that have them. There is one record per line. Fields are
475 tab-delimited. There are three types of records: Value String, Range
476 String and True/False String. The first field, 'V', 'R' or 'T', indicates
482 * Field 2 = field abbreviation to which this value string corresponds
483 * Field 3 = Integer value
489 * Field 2 = field abbreviation to which this range string corresponds
490 * Field 3 = Integer value: lower bound
491 * Field 4 = Integer value: upper bound
497 * Field 2 = field abbreviation to which this true/false string corresponds
498 * Field 3 = True String
499 * Field 4 = False String
503 Print the version and options and exits.
505 =item -H E<lt>input hosts fileE<gt>
507 Read a list of entries from a "hosts" file, which will then be written
508 to a capture file. Implies B<-W n>. Can be called multiple times.
510 The "hosts" file format is documented at
511 L<http://en.wikipedia.org/wiki/Hosts_(file)>.
513 =item -i E<lt>capture interfaceE<gt> | -
515 Set the name of the network interface or pipe to use for live packet
518 Network interface names should match one of the names listed in
519 "B<tshark -D>" (described above); a number, as reported by
520 "B<tshark -D>", can also be used. If you're using UNIX, "B<netstat
521 -i>" or "B<ifconfig -a>" might also work to list interface names,
522 although not all versions of UNIX support the B<-a> option to B<ifconfig>.
524 If no interface is specified, B<TShark> searches the list of
525 interfaces, choosing the first non-loopback interface if there are any
526 non-loopback interfaces, and choosing the first loopback interface if
527 there are no non-loopback interfaces. If there are no interfaces at all,
528 B<TShark> reports an error and doesn't start the capture.
530 Pipe names should be either the name of a FIFO (named pipe) or ``-'' to
531 read data from the standard input. Data read from pipes must be in
532 standard pcap format.
534 This option can occur multiple times. When capturing from multiple
535 interfaces, the capture file will be saved in pcap-ng format.
537 Note: the Win32 version of B<TShark> doesn't support capturing from
542 Put the interface in "monitor mode"; this is supported only on IEEE
543 802.11 Wi-Fi interfaces, and supported only on some operating systems.
545 Note that in monitor mode the adapter might disassociate from the
546 network with which it's associated, so that you will not be able to use
547 any wireless networks with that adapter. This could prevent accessing
548 files on a network server, or resolving host names or network addresses,
549 if you are capturing in monitor mode and are not connected to another
550 network with another adapter.
552 This option can occur multiple times. If used before the first
553 occurrence of the B<-i> option, it enables the monitor mode for all interfaces.
554 If used after an B<-i> option, it enables the monitor mode for
555 the interface specified by the last B<-i> option occurring before
558 =item -j E<lt>protocol match filterE<gt>
560 Protocol match filter used for ek|json|jsonraw|pdml output file types.
561 Parent node containing multiple child nodes is only included,
562 if the name is found in the filter.
564 Example: B<-j "ip ip.flags text">
566 =item -J E<lt>protocol match filterE<gt>
568 Protocol top level filter used for ek|json|jsonraw|pdml output file types.
569 Parent node containing multiple child nodes is included with all children.
571 Example: B<-J "http tcp">
573 =item -K E<lt>keytabE<gt>
575 Load kerberos crypto keys from the specified keytab file.
576 This option can be used multiple times to load keys from several files.
578 Example: B<-K krb5.keytab>
582 Flush the standard output after the information for each packet is
583 printed. (This is not, strictly speaking, line-buffered if B<-V>
584 was specified; however, it is the same as line-buffered if B<-V> wasn't
585 specified, as only one line is printed for each packet, and, as B<-l> is
586 normally used when piping a live capture to a program or script, so that
587 output for a packet shows up as soon as the packet is seen and
588 dissected, it should work just as well as true line-buffering. We do
589 this as a workaround for a deficiency in the Microsoft Visual C++ C
592 This may be useful when piping the output of B<TShark> to another
593 program, as it means that the program to which the output is piped will
594 see the dissected data for a packet as soon as B<TShark> sees the
595 packet and generates that output, rather than seeing it only when the
596 standard output buffer containing that data fills up.
600 List the data link types supported by the interface and exit. The reported
601 link types can be used for the B<-y> option.
605 Disable network object name resolution (such as hostname, TCP and UDP port
606 names); the B<-N> flag might override this one.
608 =item -N E<lt>name resolving flagsE<gt>
610 Turn on name resolving only for particular types of addresses and port
611 numbers, with name resolving for other types of addresses and port
612 numbers turned off. This flag overrides B<-n> if both B<-N> and B<-n> are
613 present. If both B<-N> and B<-n> flags are not present, all name resolutions
616 The argument is a string that may contain the letters:
618 B<d> to enable resolution from captured DNS packets
620 B<m> to enable MAC address resolution
622 B<n> to enable network address resolution
624 B<N> to enable using external resolvers (e.g., DNS) for network address
627 B<t> to enable transport-layer port number resolution
629 =item -o E<lt>preferenceE<gt>:E<lt>valueE<gt>
631 Set a preference value, overriding the default value and any value read
632 from a preference file. The argument to the option is a string of the
633 form I<prefname>B<:>I<value>, where I<prefname> is the name of the
634 preference (which is the same name that would appear in the preference
635 file), and I<value> is the value to which it should be set.
637 =item -O E<lt>protocolsE<gt>
639 Similar to the B<-V> option, but causes B<TShark> to only show a detailed view
640 of the comma-separated list of I<protocols> specified, rather than a detailed
641 view of all protocols. Use the output of "B<tshark -G protocols>" to find the
642 abbreviations of the protocols you can specify.
646 I<Don't> put the interface into promiscuous mode. Note that the
647 interface might be in promiscuous mode for some other reason; hence,
648 B<-p> cannot be used to ensure that the only traffic that is captured is
649 traffic sent to or from the machine on which B<TShark> is running,
650 broadcast traffic, and multicast traffic to addresses received by that
653 This option can occur multiple times. If used before the first
654 occurrence of the B<-i> option, no interface will be put into the
656 If used after an B<-i> option, the interface specified by the last B<-i>
657 option occurring before this option will not be put into the
662 Decode and display the packet summary, even if writing raw packet data using
667 When capturing packets, don't display the continuous count of packets
668 captured that is normally shown when saving a capture to a file;
669 instead, just display, at the end of the capture, a count of packets
670 captured. On systems that support the SIGINFO signal, such as various
671 BSDs, you can cause the current count to be displayed by typing your
672 "status" character (typically control-T, although it
673 might be set to "disabled" by default on at least some BSDs, so you'd
674 have to explicitly set it to use it).
676 When reading a capture file, or when capturing and not saving to a file,
677 don't print packet information; this is useful if you're using a B<-z>
678 option to calculate statistics and don't want the packet information
679 printed, just the statistics.
683 When capturing packets, only display true errors. This outputs less
684 than the B<-q> option, so the interface name and total packet
685 count and the end of a capture are not sent to stderr.
687 =item -r E<lt>infileE<gt>
689 Read packet data from I<infile>, can be any supported capture file format
690 (including gzipped files). It is possible to use named pipes or stdin (-)
691 here but only with certain (not compressed) capture file formats (in
692 particular: those that can be read without seeking backwards).
694 =item -R E<lt>Read filterE<gt>
696 Cause the specified filter (which uses the syntax of read/display filters,
697 rather than that of capture filters) to be applied during the first pass of
698 analysis. Packets not matching the filter are not considered for future
699 passes. Only makes sense with multiple passes, see -2. For regular filtering
700 on single-pass dissect see -Y instead.
702 Note that forward-looking fields such as 'response in frame #' cannot be used
703 with this filter, since they will not have been calculate when this filter is
706 =item -s E<lt>capture snaplenE<gt>
708 Set the default snapshot length to use when capturing live data.
709 No more than I<snaplen> bytes of each network packet will be read into
710 memory, or saved to disk. A value of 0 specifies a snapshot length of
711 262144, so that the full packet is captured; this is the default.
713 This option can occur multiple times. If used before the first
714 occurrence of the B<-i> option, it sets the default snapshot length.
715 If used after an B<-i> option, it sets the snapshot length for
716 the interface specified by the last B<-i> option occurring before
717 this option. If the snapshot length is not set specifically,
718 the default snapshot length is used if provided.
720 =item -S E<lt>separatorE<gt>
722 Set the line separator to be printed between packets.
724 =item -t a|ad|adoy|d|dd|e|r|u|ud|udoy
726 Set the format of the packet timestamp printed in summary lines.
727 The format can be one of:
729 B<a> absolute: The absolute time, as local time in your time zone,
730 is the actual time the packet was captured, with no date displayed
732 B<ad> absolute with date: The absolute date, displayed as YYYY-MM-DD,
733 and time, as local time in your time zone, is the actual time and date
734 the packet was captured
736 B<adoy> absolute with date using day of year: The absolute date,
737 displayed as YYYY/DOY, and time, as local time in your time zone,
738 is the actual time and date the packet was captured
740 B<d> delta: The delta time is the time since the previous packet was
743 B<dd> delta_displayed: The delta_displayed time is the time since the
744 previous displayed packet was captured
746 B<e> epoch: The time in seconds since epoch (Jan 1, 1970 00:00:00)
748 B<r> relative: The relative time is the time elapsed between the first packet
749 and the current packet
751 B<u> UTC: The absolute time, as UTC, is the actual time the packet was
752 captured, with no date displayed
754 B<ud> UTC with date: The absolute date, displayed as YYYY-MM-DD,
755 and time, as UTC, is the actual time and date the packet was captured
757 B<udoy> UTC with date using day of year: The absolute date, displayed
758 as YYYY/DOY, and time, as UTC, is the actual time and date the packet
761 The default format is relative.
763 =item -T ek|fields|json|jsonraw|pdml|ps|psml|tabs|text
765 Set the format of the output when viewing decoded packet data. The
768 B<ek> Newline delimited JSON format for bulk import into Elasticsearch.
769 It can be used with B<-j> or B<-J> including the JSON filter or with
770 B<-x> flag to include raw hex-encoded packet data.
771 Example of usage to import data into Elasticsearch:
773 tshark -T ek -j "http tcp ip" -x -r file.pcap > file.json
774 curl -XPUT http://elasticsearch:9200/_bulk --data-binary @file.json
776 B<fields> The values of fields specified with the B<-e> option, in a
777 form specified by the B<-E> option. For example,
779 -T fields -E separator=, -E quote=d
781 would generate comma-separated values (CSV) output suitable for importing
782 into your favorite spreadsheet program.
784 B<json> JSON file format. It can be used with B<-j> or B<-J> including
785 the JSON filter or with B<-x> flag to include raw hex-encoded packet data.
788 tshark -T json -r file.pcap
789 tshark -T json -j "http tcp ip" -x -r file.pcap
791 B<jsonraw> JSON file format including only raw hex-encoded packet data.
792 It can be used with B<-j> including or B<-J >the JSON filter flag.
795 tshark -T jsonraw -r file.pcap
796 tshark -T jsonraw -j "http tcp ip" -x -r file.pcap
798 B<pdml> Packet Details Markup Language, an XML-based format for the details of
799 a decoded packet. This information is equivalent to the packet details
800 printed with the B<-V> flag.
801 Using the --color option will add color attributes to B<pdml> output. These
802 attributes are nonstandard.
804 B<ps> PostScript for a human-readable one-line summary of each of the packets,
805 or a multi-line view of the details of each of the packets, depending on
806 whether the B<-V> flag was specified.
808 B<psml> Packet Summary Markup Language, an XML-based format for the summary
809 information of a decoded packet. This information is equivalent to the
810 information shown in the one-line summary printed by default.
811 Using the --color option will add color attributes to B<pdml> output. These
812 attributes are nonstandard.
814 B<tabs> Similar to the default B<text> report except the human-readable one-line
815 summary of each packet will include an ASCII horizontal tab (0x09) character
816 as a delimiter between each column.
818 B<text> Text of a human-readable one-line summary of each of the packets, or a
819 multi-line view of the details of each of the packets, depending on
820 whether the B<-V> flag was specified. This is the default.
822 =item -u E<lt>seconds typeE<gt>
824 Specifies the seconds type. Valid choices are:
828 B<hms> for hours, minutes and seconds
830 =item -U E<lt>tap nameE<gt>
832 PDUs export, exports PDUs from infile to outfile according to the tap name given. Use -Y to filter.
834 Enter an empty tap name "" to get a list of available names.
838 Print the version and exit.
842 Cause B<TShark> to print a view of the packet details.
844 =item -w E<lt>outfileE<gt> | -
846 Write raw packet data to I<outfile> or to the standard output if
849 NOTE: -w provides raw packet data, not text. If you want text output
850 you need to redirect stdout (e.g. using '>'), don't use the B<-w>
853 =item -W E<lt>file format optionE<gt>
855 Save extra information in the file if the format supports it. For
860 will save host name resolution records along with captured packets.
862 Future versions of Wireshark may automatically change the capture format to
865 The argument is a string that may contain the following letter:
867 B<n> write network address resolution information (pcapng only)
871 Cause B<TShark> to print a hex and ASCII dump of the packet data
872 after printing the summary and/or details, if either are also being displayed.
874 =item -X E<lt>eXtension optionsE<gt>
876 Specify an option to be passed to a B<TShark> module. The eXtension option
877 is in the form I<extension_key>B<:>I<value>, where I<extension_key> can be:
879 B<lua_script>:I<lua_script_filename> tells B<TShark> to load the given script in addition to the
882 B<lua_script>I<num>:I<argument> tells B<TShark> to pass the given argument
883 to the lua script identified by 'num', which is the number indexed order of the 'lua_script' command.
884 For example, if only one script was loaded with '-X lua_script:my.lua', then '-X lua_script1:foo'
885 will pass the string 'foo' to the 'my.lua' script. If two scripts were loaded, such as '-X lua_script:my.lua'
886 and '-X lua_script:other.lua' in that order, then a '-X lua_script2:bar' would pass the string 'bar' to the second lua
887 script, namely 'other.lua'.
889 B<read_format>:I<file_format> tells B<TShark> to use the given file format to read in the
890 file (the file given in the B<-r> command option). Providing no I<file_format> argument, or
891 an invalid one, will produce a file of available file formats to use.
893 =item -y E<lt>capture link typeE<gt>
895 Set the data link type to use while capturing packets. The values
896 reported by B<-L> are the values that can be used.
898 This option can occur multiple times. If used before the first
899 occurrence of the B<-i> option, it sets the default capture link type.
900 If used after an B<-i> option, it sets the capture link type for
901 the interface specified by the last B<-i> option occurring before
902 this option. If the capture link type is not set specifically,
903 the default capture link type is used if provided.
905 =item -Y E<lt>displaY filterE<gt>
907 Cause the specified filter (which uses the syntax of read/display filters,
908 rather than that of capture filters) to be applied before printing a
909 decoded form of packets or writing packets to a file. Packets matching the
910 filter are printed or written to file; packets that the matching packets
911 depend upon (e.g., fragments), are not printed but are written to file;
912 packets not matching the filter nor depended upon are discarded rather
913 than being printed or written.
915 Use this instead of -R for filtering using single-pass analysis. If doing
916 two-pass analysis (see -2) then only packets matching the read filter (if there
917 is one) will be checked against this filter.
919 =item -M E<lt>auto session resetE<gt>
921 Automatically reset internal session when reached to specified number of packets.
926 will reset session every 100000 packets.
928 This feature does not support -2 two-pass analysis
930 =item -z E<lt>statisticsE<gt>
932 Get B<TShark> to collect various types of statistics and display the result
933 after finishing reading the capture file. Use the B<-q> flag if you're
934 reading a capture file and only want the statistics printed, not any
935 per-packet information.
937 Note that the B<-z proto> option is different - it doesn't cause
938 statistics to be gathered and printed when the capture is complete, it
939 modifies the regular packet summary output to include the values of
940 fields specified with the option. Therefore you must not use the B<-q>
941 option, as that option would suppress the printing of the regular packet
942 summary output, and must also not use the B<-V> option, as that would
943 cause packet detail information rather than packet summary information
946 Currently implemented statistics are:
952 Display all possible values for B<-z>.
954 =item B<-z> afp,srt[,I<filter>]
956 Show Apple Filing Protocol service response time statistics.
958 =item B<-z> camel,srt
960 =item B<-z> compare,I<start>,I<stop>,I<ttl[0|1]>,I<order[0|1]>,I<variance>[,I<filter>]
962 If the optional I<filter> is specified, only those packets that match the
963 filter will be used in the calculations.
965 =item B<-z> conv,I<type>[,I<filter>]
967 Create a table that lists all conversations that could be seen in the
968 capture. I<type> specifies the conversation endpoint types for which we
969 want to generate the statistics; currently the supported ones are:
971 "bluetooth" Bluetooth addresses
972 "eth" Ethernet addresses
973 "fc" Fibre Channel addresses
974 "fddi" FDDI addresses
976 "ipv6" IPv6 addresses
978 "jxta" JXTA message addresses
979 "ncp" NCP connections
980 "rsvp" RSVP connections
981 "sctp" SCTP addresses
982 "tcp" TCP/IP socket pairs Both IPv4 and IPv6 are supported
983 "tr" Token Ring addresses
985 "udp" UDP/IP socket pairs Both IPv4 and IPv6 are supported
986 "wlan" IEEE 802.11 addresses
988 If the optional I<filter> is specified, only those packets that match the
989 filter will be used in the calculations.
991 The table is presented with one line for each conversation and displays
992 the number of packets/bytes in each direction as well as the total
993 number of packets/bytes. The table is sorted according to the total
996 =item B<-z> dcerpc,srt,I<uuid>,I<major>.I<minor>[,I<filter>]
998 Collect call/reply SRT (Service Response Time) data for DCERPC interface I<uuid>,
999 version I<major>.I<minor>.
1000 Data collected is the number of calls for each procedure, MinSRT, MaxSRT
1003 Example: S<B<-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0>> will collect data for the CIFS SAMR Interface.
1005 This option can be used multiple times on the command line.
1007 If the optional I<filter> is provided, the stats will only be calculated
1008 on those calls that match that filter.
1010 Example: S<B<-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0,ip.addr==1.2.3.4>> will collect SAMR
1011 SRT statistics for a specific host.
1013 =item B<-z> bootp,stat[,I<filter>]
1015 Show DHCP (BOOTP) statistics.
1017 =item B<-z> diameter,avp[,I<cmd.code>,I<field>,I<field>,I<...>]
1019 This option enables extraction of most important diameter fields from large capture files.
1020 Exactly one text line for each diameter message with matched B<diameter.cmd.code> will be printed.
1022 Empty diameter command code or '*' can be specified to mach any B<diameter.cmd.code>
1024 Example: B<-z diameter,avp> extract default field set from diameter messages.
1026 Example: B<-z diameter,avp,280> extract default field set from diameter DWR messages.
1028 Example: B<-z diameter,avp,272> extract default field set from diameter CC messages.
1030 Extract most important fields from diameter CC messages:
1032 B<tshark -r file.cap.gz -q -z diameter,avp,272,CC-Request-Type,CC-Request-Number,Session-Id,Subscription-Id-Data,Rating-Group,Result-Code>
1034 Following fields will be printed out for each diameter message:
1036 "frame" Frame number.
1037 "time" Unix time of the frame arrival.
1038 "src" Source address.
1039 "srcport" Source port.
1040 "dst" Destination address.
1041 "dstport" Destination port.
1042 "proto" Constant string 'diameter', which can be used for post processing of tshark output. E.g. grep/sed/awk.
1043 "msgnr" seq. number of diameter message within the frame. E.g. '2' for the third diameter message in the same frame.
1044 "is_request" '0' if message is a request, '1' if message is an answer.
1045 "cmd" diameter.cmd_code, E.g. '272' for credit control messages.
1046 "req_frame" Number of frame where matched request was found or '0'.
1047 "ans_frame" Number of frame where matched answer was found or '0'.
1048 "resp_time" response time in seconds, '0' in case if matched Request/Answer is not found in trace. E.g. in the begin or end of capture.
1050 B<-z diameter,avp> option is much faster than B<-V -T text> or B<-T pdml> options.
1052 B<-z diameter,avp> option is more powerful than B<-T field> and B<-z proto,colinfo> options.
1054 Multiple diameter messages in one frame are supported.
1056 Several fields with same name within one diameter message are supported, e.g. I<diameter.Subscription-Id-Data> or I<diameter.Rating-Group>.
1058 Note: B<tshark -q> option is recommended to suppress default B<tshark> output.
1060 =item B<-z> dns,tree[,I<filter>]
1062 Create a summary of the captured DNS packets. General information are collected such as qtype and qclass distribution.
1063 For some data (as qname length or DNS payload) max, min and average values are also displayed.
1065 =item B<-z> endpoints,I<type>[,I<filter>]
1067 Create a table that lists all endpoints that could be seen in the
1068 capture. I<type> specifies the endpoint types for which we
1069 want to generate the statistics; currently the supported ones are:
1071 "bluetooth" Bluetooth addresses
1072 "eth" Ethernet addresses
1073 "fc" Fibre Channel addresses
1074 "fddi" FDDI addresses
1076 "ipv6" IPv6 addresses
1078 "jxta" JXTA message addresses
1079 "ncp" NCP connections
1080 "rsvp" RSVP connections
1081 "sctp" SCTP addresses
1082 "tcp" TCP/IP socket pairs Both IPv4 and IPv6 are supported
1083 "tr" Token Ring addresses
1085 "udp" UDP/IP socket pairs Both IPv4 and IPv6 are supported
1086 "wlan" IEEE 802.11 addresses
1088 If the optional I<filter> is specified, only those packets that match the
1089 filter will be used in the calculations.
1091 The table is presented with one line for each conversation and displays
1092 the number of packets/bytes in each direction as well as the total
1093 number of packets/bytes. The table is sorted according to the total
1096 =item B<-z> expert[I<,error|,warn|,note|,chat>][I<,filter>]
1098 Collects information about all expert info, and will display them in order,
1099 grouped by severity.
1101 Example: B<-z expert,sip> will show expert items of all severity for frames that
1102 match the sip protocol.
1104 This option can be used multiple times on the command line.
1106 If the optional I<filter> is provided, the stats will only be calculated
1107 on those calls that match that filter.
1109 Example: B<-z "expert,note,tcp"> will only collect expert items for frames that
1110 include the tcp protocol, with a severity of note or higher.
1112 =item B<-z> flow,I<name>,I<mode>,[I<filter>]
1114 Displays the flow of data between two nodes. Output is the same as ASCII format
1117 I<name> specifies the flow name. It can be one of:
1125 I<mode> specifies the address type. It can be one of:
1127 standard Any address
1128 network Network address
1130 Example: B<-z flow,tcp,network> will show data flow for all TCP frames
1132 =item B<-z> follow,I<prot>,I<mode>,I<filter>[I<,range>]
1134 Displays the contents of a TCP or UDP stream between two nodes. The data
1135 sent by the second node is prefixed with a tab to differentiate it from the
1136 data sent by the first node.
1138 I<prot> specifies the transport protocol. It can be one of:
1144 I<mode> specifies the output mode. It can be one of:
1146 ascii ASCII output with dots for non-printable characters
1147 ebcdic EBCDIC output with dots for non-printable characters
1148 hex Hexadecimal and ASCII data with offsets
1149 raw Hexadecimal data
1151 Since the output in B<ascii> or B<ebcdic> mode may contain newlines, the length
1152 of each section of output plus a newline precedes each section of output.
1154 I<filter> specifies the stream to be displayed. UDP/TCP streams are selected
1155 with either the stream index or IP address plus port pairs. SSL streams are
1156 selected with the stream index. For example:
1158 ip-addr0:port0,ip-addr1:port1
1161 I<range> optionally specifies which "chunks" of the stream should be displayed.
1163 Example: B<-z "follow,tcp,hex,1"> will display the contents of the second TCP
1164 stream (the first is stream 0) in "hex" format.
1166 ===================================================================
1168 Filter: tcp.stream eq 1
1169 Node 0: 200.57.7.197:32891
1170 Node 1: 200.57.7.198:2906
1171 00000000 00 00 00 22 00 00 00 07 00 0a 85 02 07 e9 00 02 ...".... ........
1172 00000010 07 e9 06 0f 00 0d 00 04 00 00 00 01 00 03 00 06 ........ ........
1173 00000020 1f 00 06 04 00 00 ......
1174 00000000 00 01 00 00 ....
1175 00000026 00 02 00 00
1177 Example: B<-z "follow,tcp,ascii,200.57.7.197:32891,200.57.7.198:2906"> will
1178 display the contents of a TCP stream between 200.57.7.197 port 32891 and
1179 200.57.7.98 port 2906.
1181 ===================================================================
1183 Filter: (omitted for readability)
1184 Node 0: 200.57.7.197:32891
1185 Node 1: 200.57.7.198:2906
1192 =item B<-z> h225,counter[I<,filter>]
1194 Count ITU-T H.225 messages and their reasons. In the first column you get a
1195 list of H.225 messages and H.225 message reasons, which occur in the current
1196 capture file. The number of occurrences of each message or reason is displayed
1197 in the second column.
1199 Example: B<-z h225,counter>.
1201 If the optional I<filter> is provided, the stats will only be calculated
1202 on those calls that match that filter.
1203 Example: use B<-z "h225,counter,ip.addr==1.2.3.4"> to only collect stats for
1204 H.225 packets exchanged by the host at IP address 1.2.3.4 .
1206 This option can be used multiple times on the command line.
1208 =item B<-z> h225,srt[I<,filter>]
1210 Collect requests/response SRT (Service Response Time) data for ITU-T H.225 RAS.
1211 Data collected is number of calls of each ITU-T H.225 RAS Message Type,
1212 Minimum SRT, Maximum SRT, Average SRT, Minimum in Packet, and Maximum in Packet.
1213 You will also get the number of Open Requests (Unresponded Requests),
1214 Discarded Responses (Responses without matching request) and Duplicate Messages.
1216 Example: B<-z h225,srt>
1218 This option can be used multiple times on the command line.
1220 If the optional I<filter> is provided, the stats will only be calculated
1221 on those calls that match that filter.
1223 Example: B<-z "h225,srt,ip.addr==1.2.3.4"> will only collect stats for
1224 ITU-T H.225 RAS packets exchanged by the host at IP address 1.2.3.4 .
1226 =item B<-z> hosts[,ipv4][,ipv6]
1228 Dump any collected IPv4 and/or IPv6 addresses in "hosts" format. Both IPv4
1229 and IPv6 addresses are dumped by default.
1231 Addresses are collected from a number of sources, including standard "hosts"
1232 files and captured traffic.
1234 =item B<-z> hpfeeds,tree[,I<filter>]
1236 Calculate statistics for HPFEEDS traffic such as publish per channel, and opcode
1239 =item B<-z> http,stat,
1241 Calculate the HTTP statistics distribution. Displayed values are
1242 the HTTP status codes and the HTTP request methods.
1244 =item B<-z> http,tree
1246 Calculate the HTTP packet distribution. Displayed values are the
1247 HTTP request modes and the HTTP status codes.
1249 =item B<-z> http_req,tree
1251 Calculate the HTTP requests by server. Displayed values are the
1252 server name and the URI path.
1254 =item B<-z> http_srv,tree
1256 Calculate the HTTP requests and responses by server. For the HTTP
1257 requests, displayed values are the server IP address and server
1258 hostname. For the HTTP responses, displayed values are the server
1259 IP address and status.
1261 =item B<-z> icmp,srt[,I<filter>]
1263 Compute total ICMP echo requests, replies, loss, and percent loss, as well as
1264 minimum, maximum, mean, median and sample standard deviation SRT statistics
1265 typical of what ping provides.
1267 Example: S<B<-z icmp,srt,ip.src==1.2.3.4>> will collect ICMP SRT statistics
1268 for ICMP echo request packets originating from a specific host.
1270 This option can be used multiple times on the command line.
1272 =item B<-z> icmpv6,srt[,I<filter>]
1274 Compute total ICMPv6 echo requests, replies, loss, and percent loss, as well as
1275 minimum, maximum, mean, median and sample standard deviation SRT statistics
1276 typical of what ping provides.
1278 Example: S<B<-z icmpv6,srt,ipv6.src==fe80::1>> will collect ICMPv6 SRT statistics
1279 for ICMPv6 echo request packets originating from a specific host.
1281 This option can be used multiple times on the command line.
1283 =item B<-z> io,phs[,I<filter>]
1285 Create Protocol Hierarchy Statistics listing both number of packets and bytes.
1286 If no I<filter> is specified the statistics will be calculated for all packets.
1287 If a I<filter> is specified statistics will only be calculated for those
1288 packets that match the filter.
1290 This option can be used multiple times on the command line.
1292 =item B<-z> io,stat,I<interval>[,I<filter>][,I<filter>][,I<filter>]...
1294 Collect packet/bytes statistics for the capture in intervals of
1295 I<interval> seconds. I<Interval> can be specified either as a whole or
1296 fractional second and can be specified with microsecond (us) resolution.
1297 If I<interval> is 0, the statistics will be calculated over all packets.
1299 If no I<filter> is specified the statistics will be calculated for all packets.
1300 If one or more I<filters> are specified statistics will be calculated for
1301 all filters and presented with one column of statistics for each filter.
1303 This option can be used multiple times on the command line.
1305 Example: B<-z io,stat,1,ip.addr==1.2.3.4> will generate 1 second
1306 statistics for all traffic to/from host 1.2.3.4.
1308 Example: B<-z "io,stat,0.001,smb&&ip.addr==1.2.3.4"> will generate 1ms
1309 statistics for all SMB packets to/from host 1.2.3.4.
1311 The examples above all use the standard syntax for generating statistics
1312 which only calculates the number of packets and bytes in each interval.
1314 B<io,stat> can also do much more statistics and calculate COUNT(), SUM(),
1315 MIN(), MAX(), AVG() and LOAD() using a slightly different filter syntax:
1317 =item -z io,stat,I<interval>,E<34>[COUNT|SUM|MIN|MAX|AVG|LOAD](I<field>)I<filter>E<34>
1319 NOTE: One important thing to note here is that the filter is not optional
1320 and that the field that the calculation is based on MUST be part of the filter
1321 string or the calculation will fail.
1323 So: B<-z io,stat,0.010,AVG(smb.time)> does not work. Use B<-z
1324 io,stat,0.010,AVG(smb.time)smb.time> instead. Also be aware that a field
1325 can exist multiple times inside the same packet and will then be counted
1326 multiple times in those packets.
1328 NOTE: A second important thing to note is that the system setting for
1329 decimal separator must be set to "."! If it is set to "," the statistics
1330 will not be displayed per filter.
1332 B<COUNT(I<field>)I<filter>> - Calculates the number of times that the
1333 field I<name> (not its value) appears per interval in the filtered packet list.
1334 ''I<field>'' can be any display filter name.
1336 Example: B<-z io,stat,0.010,E<34>COUNT(smb.sid)smb.sidE<34>>
1338 This will count the total number of SIDs seen in each 10ms interval.
1340 B<SUM(I<field>)I<filter>> - Unlike COUNT, the I<values> of the
1341 specified field are summed per time interval.
1342 ''I<field>'' can only be a named integer, float, double or relative time field.
1344 Example: B<-z io,stat,0.010,E<34>SUM(frame.len)frame.lenE<34>>
1346 Reports the total number of bytes that were transmitted bidirectionally in
1347 all the packets within a 10 millisecond interval.
1349 B<MIN/MAX/AVG(I<field>)I<filter>> - The minimum, maximum, or average field value
1350 in each interval is calculated. The specified field must be a named integer,
1351 float, double or relative time field. For relative time fields, the output is presented in
1352 seconds with six decimal digits of precision rounded to the nearest microsecond.
1354 In the following example, the time of the first Read_AndX call, the last Read_AndX
1355 response values are displayed and the minimum, maximum, and average Read response times
1356 (SRTs) are calculated. NOTE: If the DOS command shell line continuation character, ''^''
1357 is used, each line cannot end in a comma so it is placed at the beginning of each
1360 tshark -o tcp.desegment_tcp_streams:FALSE -n -q -r smb_reads.cap -z io,stat,0,
1361 "MIN(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==0",
1362 "MAX(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==1",
1363 "MIN(smb.time)smb.time and smb.cmd==0x2e",
1364 "MAX(smb.time)smb.time and smb.cmd==0x2e",
1365 "AVG(smb.time)smb.time and smb.cmd==0x2e"
1368 ======================================================================================================
1370 Column #0: MIN(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==0
1371 Column #1: MAX(frame.time_relative)frame.time_relative and smb.cmd==0x2e and smb.flags.response==1
1372 Column #2: MIN(smb.time)smb.time and smb.cmd==0x2e
1373 Column #3: MAX(smb.time)smb.time and smb.cmd==0x2e
1374 Column #4: AVG(smb.time)smb.time and smb.cmd==0x2e
1375 | Column #0 | Column #1 | Column #2 | Column #3 | Column #4 |
1376 Time | MIN | MAX | MIN | MAX | AVG |
1377 000.000- 0.000000 7.704054 0.000072 0.005539 0.000295
1378 ======================================================================================================
1380 The following command displays the average SMB Read response PDU size, the
1381 total number of read PDU bytes, the average SMB Write request PDU size, and
1382 the total number of bytes transferred in SMB Write PDUs:
1384 tshark -n -q -r smb_reads_writes.cap -z io,stat,0,
1385 "AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to",
1386 "SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to",
1387 "AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to",
1388 "SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to"
1390 =====================================================================================
1392 Column #0: AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to
1393 Column #1: SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2e and smb.response_to
1394 Column #2: AVG(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to
1395 Column #3: SUM(smb.file.rw.length)smb.file.rw.length and smb.cmd==0x2f and not smb.response_to
1396 | Column #0 | Column #1 | Column #2 | Column #3 |
1397 Time | AVG | SUM | AVG | SUM |
1398 000.000- 30018 28067522 72 3240
1399 =====================================================================================
1401 B<LOAD(I<field>)I<filter>> - The LOAD/Queue-Depth
1402 in each interval is calculated. The specified field must be a relative time field that represents a response time. For example smb.time.
1403 For each interval the Queue-Depth for the specified protocol is calculated.
1405 The following command displays the average SMB LOAD.
1406 A value of 1.0 represents one I/O in flight.
1408 tshark -n -q -r smb_reads_writes.cap
1409 -z "io,stat,0.001,LOAD(smb.time)smb.time"
1411 ============================================================================
1413 Interval: 0.001000 secs
1414 Column #0: LOAD(smb.time)smb.time
1417 0000.000000-0000.001000 1.000000
1418 0000.001000-0000.002000 0.741000
1419 0000.002000-0000.003000 0.000000
1420 0000.003000-0000.004000 1.000000
1424 B<FRAMES | BYTES[()I<filter>]> - Displays the total number of frames or bytes.
1425 The filter field is optional but if included it must be prepended with ''()''.
1427 The following command displays five columns: the total number of frames and bytes
1428 (transferred bidirectionally) using a single comma, the same two stats using the FRAMES and BYTES
1429 subcommands, the total number of frames containing at least one SMB Read response, and
1430 the total number of bytes transmitted to the client (unidirectionally) at IP address 10.1.0.64.
1432 tshark -o tcp.desegment_tcp_streams:FALSE -n -q -r smb_reads.cap -z io,stat,0,,FRAMES,BYTES,
1433 "FRAMES()smb.cmd==0x2e and smb.response_to","BYTES()ip.dst==10.1.0.64"
1435 =======================================================================================================================
1440 Column #3: FRAMES()smb.cmd==0x2e and smb.response_to
1441 Column #4: BYTES()ip.dst==10.1.0.64
1442 | Column #0 | Column #1 | Column #2 | Column #3 | Column #4 |
1443 Time | Frames | Bytes | FRAMES | BYTES | FRAMES | BYTES |
1444 000.000- 33576 29721685 33576 29721685 870 29004801
1445 =======================================================================================================================
1447 =item B<-z> mac-lte,stat[I<,filter>]
1449 This option will activate a counter for LTE MAC messages. You will get
1450 information about the maximum number of UEs/TTI, common messages and
1451 various counters for each UE that appears in the log.
1453 Example: B<-z mac-lte,stat>.
1455 This option can be used multiple times on the command line.
1457 If the optional I<filter> is provided, the stats will only be calculated
1458 for those frames that match that filter.
1459 Example: B<-z "mac-lte,stat,mac-lte.rnti>3000"> will only collect stats for
1460 UEs with an assigned RNTI whose value is more than 3000.
1462 =item B<-z> megaco,rtd[I<,filter>]
1464 Collect requests/response RTD (Response Time Delay) data for MEGACO.
1465 (This is similar to B<-z smb,srt>). Data collected is the number of calls
1466 for each known MEGACO Type, MinRTD, MaxRTD and AvgRTD.
1467 Additionally you get the number of duplicate requests/responses,
1468 unresponded requests, responses, which don't match with any request.
1469 Example: B<-z megaco,rtd>.
1471 If the optional I<filter> is provided, the stats will only be calculated
1472 on those calls that match that filter.
1473 Example: B<-z "megaco,rtd,ip.addr==1.2.3.4"> will only collect stats for
1474 MEGACO packets exchanged by the host at IP address 1.2.3.4 .
1476 This option can be used multiple times on the command line.
1478 =item B<-z> mgcp,rtd[I<,filter>]
1480 Collect requests/response RTD (Response Time Delay) data for MGCP.
1481 (This is similar to B<-z smb,srt>). Data collected is the number of calls
1482 for each known MGCP Type, MinRTD, MaxRTD and AvgRTD.
1483 Additionally you get the number of duplicate requests/responses,
1484 unresponded requests, responses, which don't match with any request.
1485 Example: B<-z mgcp,rtd>.
1487 This option can be used multiple times on the command line.
1489 If the optional I<filter> is provided, the stats will only be calculated
1490 on those calls that match that filter.
1491 Example: B<-z "mgcp,rtd,ip.addr==1.2.3.4"> will only collect stats for
1492 MGCP packets exchanged by the host at IP address 1.2.3.4 .
1494 =item B<-z> proto,colinfo,I<filter>,I<field>
1496 Append all I<field> values for the packet to the Info column of the
1497 one-line summary output.
1498 This feature can be used to append arbitrary fields to the Info column
1499 in addition to the normal content of that column.
1500 I<field> is the display-filter name of a field which value should be placed
1502 I<filter> is a filter string that controls for which packets the field value
1503 will be presented in the info column. I<field> will only be presented in the
1504 Info column for the packets which match I<filter>.
1506 NOTE: In order for B<TShark> to be able to extract the I<field> value
1507 from the packet, I<field> MUST be part of the I<filter> string. If not,
1508 B<TShark> will not be able to extract its value.
1510 For a simple example to add the "nfs.fh.hash" field to the Info column
1511 for all packets containing the "nfs.fh.hash" field, use
1513 B<-z proto,colinfo,nfs.fh.hash,nfs.fh.hash>
1515 To put "nfs.fh.hash" in the Info column but only for packets coming from
1518 B<-z "proto,colinfo,nfs.fh.hash && ip.src==1.2.3.4,nfs.fh.hash">
1520 This option can be used multiple times on the command line.
1522 =item B<-z> rlc-lte,stat[I<,filter>]
1524 This option will activate a counter for LTE RLC messages. You will get
1525 information about common messages and various counters for each UE that appears
1528 Example: B<-z rlc-lte,stat>.
1530 This option can be used multiple times on the command line.
1532 If the optional I<filter> is provided, the stats will only be calculated
1533 for those frames that match that filter.
1534 Example: B<-z "rlc-lte,stat,rlc-lte.ueid>3000"> will only collect stats for
1535 UEs with a UEId of more than 3000.
1537 =item B<-z> rpc,programs
1539 Collect call/reply SRT data for all known ONC-RPC programs/versions.
1540 Data collected is number of calls for each protocol/version, MinSRT,
1542 This option can only be used once on the command line.
1544 =item B<-z> rpc,srt,I<program>,I<version>[,I<filter>]
1546 Collect call/reply SRT (Service Response Time) data for I<program>/I<version>.
1547 Data collected is the number of calls for each procedure, MinSRT, MaxSRT,
1548 AvgSRT, and the total time taken for each procedure.
1551 Example: B<-z rpc,srt,100003,3> will collect data for NFS v3.
1553 This option can be used multiple times on the command line.
1555 If the optional I<filter> is provided, the stats will only be calculated
1556 on those calls that match that filter.
1558 Example: B<-z rpc,srt,100003,3,nfs.fh.hash==0x12345678> will collect NFS v3
1559 SRT statistics for a specific file.
1561 =item B<-z> rtp,streams
1563 Collect statistics for all RTP streams and calculate max. delta, max. and
1564 mean jitter and packet loss percentages.
1566 =item B<-z> scsi,srt,I<cmdset>[,I<filter>]
1568 Collect call/reply SRT (Service Response Time) data for SCSI commandset I<cmdset>.
1570 Commandsets are 0:SBC 1:SSC 5:MMC
1573 is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.
1575 Example: B<-z scsi,srt,0> will collect data for SCSI BLOCK COMMANDS (SBC).
1577 This option can be used multiple times on the command line.
1579 If the optional I<filter> is provided, the stats will only be calculated
1580 on those calls that match that filter.
1582 Example: B<-z scsi,srt,0,ip.addr==1.2.3.4> will collect SCSI SBC
1583 SRT statistics for a specific iscsi/ifcp/fcip host.
1585 =item B<-z> sip,stat[I<,filter>]
1587 This option will activate a counter for SIP messages. You will get the number
1588 of occurrences of each SIP Method and of each SIP Status-Code. Additionally
1589 you also get the number of resent SIP Messages (only for SIP over UDP).
1591 Example: B<-z sip,stat>.
1593 This option can be used multiple times on the command line.
1595 If the optional I<filter> is provided, the stats will only be calculated
1596 on those calls that match that filter.
1597 Example: B<-z "sip,stat,ip.addr==1.2.3.4"> will only collect stats for
1598 SIP packets exchanged by the host at IP address 1.2.3.4 .
1600 =item B<-z> smb,sids
1602 When this feature is used B<TShark> will print a report with all the
1603 discovered SID and account name mappings. Only those SIDs where the
1604 account name is known will be presented in the table.
1606 For this feature to work you will need to either to enable
1607 "Edit/Preferences/Protocols/SMB/Snoop SID to name mappings" in the
1608 preferences or you can override the preferences by specifying
1609 S<B<-o "smb.sid_name_snooping:TRUE">> on the B<TShark> command line.
1611 The current method used by B<TShark> to find the SID->name mapping
1612 is relatively restricted with a hope of future expansion.
1614 =item B<-z> smb,srt[,I<filter>]
1616 Collect call/reply SRT (Service Response Time) data for SMB. Data collected
1617 is number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.
1619 Example: B<-z smb,srt>
1621 The data will be presented as separate tables for all normal SMB commands,
1622 all Transaction2 commands and all NT Transaction commands.
1623 Only those commands that are seen in the capture will have its stats
1625 Only the first command in a xAndX command chain will be used in the
1626 calculation. So for common SessionSetupAndX + TreeConnectAndX chains,
1627 only the SessionSetupAndX call will be used in the statistics.
1628 This is a flaw that might be fixed in the future.
1630 This option can be used multiple times on the command line.
1632 If the optional I<filter> is provided, the stats will only be calculated
1633 on those calls that match that filter.
1635 Example: B<-z "smb,srt,ip.addr==1.2.3.4"> will only collect stats for
1636 SMB packets exchanged by the host at IP address 1.2.3.4 .
1640 =item --capture-comment E<lt>commentE<gt>
1642 Add a capture comment to the output file.
1644 This option is only available if a new output file in pcapng format is
1645 created. Only one capture comment may be set per output file.
1647 =item --list-time-stamp-types
1649 List time stamp types supported for the interface. If no time stamp type can be
1650 set, no time stamp types are listed.
1652 =item --time-stamp-type E<lt>typeE<gt>
1654 Change the interface's timestamp method.
1658 Enable coloring of packets according to standard Wireshark color filters. This
1659 is currently implemented via 24-bit "true color" terminal escape sequences that
1660 are not supported by all terminal emulators. See
1661 L<https://wiki.wireshark.org/ColoringRules> for more information on configuring
1664 =item --no-duplicate-keys
1666 If a key appears multiple times in an object, only write it a single time with
1667 as value a json array containing all the separate values. (Only works with
1670 =item --export-objects E<lt>protocolE<gt>,E<lt>destdirE<gt>
1672 Export all objects within a protocol into directory B<destdir>. The available
1673 values for B<protocol> can be listed with B<--export-objects help>.
1675 The objects are directly saved in the given directory. Filenames are dependent
1676 on the dissector, but typically it is named after the basename of a file.
1677 Duplicate files are not overwritten, instead an increasing number is appended
1678 before the file extension.
1680 This interface is subject to change, adding the possibility to filter on files.
1682 =item --enable-protocol E<lt>proto_nameE<gt>
1684 Enable dissection of proto_name.
1686 =item --disable-protocol E<lt>proto_nameE<gt>
1688 Disable dissection of proto_name.
1690 =item --enable-heuristic E<lt>short_nameE<gt>
1692 Enable dissection of heuristic protocol.
1694 =item --disable-heuristic E<lt>short_nameE<gt>
1696 Disable dissection of heuristic protocol.
1700 =head1 CAPTURE FILTER SYNTAX
1702 See the manual page of pcap-filter(7) or, if that doesn't exist, tcpdump(8),
1703 or, if that doesn't exist, L<https://wiki.wireshark.org/CaptureFilters>.
1705 =head1 READ FILTER SYNTAX
1707 For a complete table of protocol and protocol fields that are filterable
1708 in B<TShark> see the wireshark-filter(4) manual page.
1712 These files contains various B<Wireshark> configuration values.
1718 The F<preferences> files contain global (system-wide) and personal
1719 preference settings. If the system-wide preference file exists, it is
1720 read first, overriding the default settings. If the personal preferences
1721 file exists, it is read next, overriding any previous values. Note: If
1722 the command line option B<-o> is used (possibly more than once), it will
1723 in turn override values from the preferences files.
1725 The preferences settings are in the form I<prefname>B<:>I<value>,
1727 where I<prefname> is the name of the preference
1728 and I<value> is the value to
1729 which it should be set; white space is allowed between B<:> and
1730 I<value>. A preference setting can be continued on subsequent lines by
1731 indenting the continuation lines with white space. A B<#> character
1732 starts a comment that runs to the end of the line:
1734 # Capture in promiscuous mode?
1735 # TRUE or FALSE (case-insensitive).
1736 capture.prom_mode: TRUE
1738 The global preferences file is looked for in the F<wireshark> directory
1739 under the F<share> subdirectory of the main installation directory (for
1740 example, F</usr/local/share/wireshark/preferences>) on UNIX-compatible
1741 systems, and in the main installation directory (for example,
1742 F<C:\Program Files\Wireshark\preferences>) on Windows systems.
1744 The personal preferences file is looked for in
1745 F<$XDG_CONFIG_HOME/wireshark/preferences>
1746 (or, if F<$XDG_CONFIG_HOME/wireshark> does not exist while F<$HOME/.wireshark>
1747 is present, F<$HOME/.wireshark/preferences>) on
1748 UNIX-compatible systems and F<%APPDATA%\Wireshark\preferences> (or, if
1749 %APPDATA% isn't defined, F<%USERPROFILE%\Application
1750 Data\Wireshark\preferences>) on Windows systems.
1752 =item Disabled (Enabled) Protocols
1754 The F<disabled_protos> files contain system-wide and personal lists of
1755 protocols that have been disabled, so that their dissectors are never
1756 called. The files contain protocol names, one per line, where the
1757 protocol name is the same name that would be used in a display filter
1763 The global F<disabled_protos> file uses the same directory as the global
1766 The personal F<disabled_protos> file uses the same directory as the
1767 personal preferences file.
1769 =item Name Resolution (hosts)
1771 If the personal F<hosts> file exists, it is
1772 used to resolve IPv4 and IPv6 addresses before any other
1773 attempts are made to resolve them. The file has the standard F<hosts>
1774 file syntax; each line contains one IP address and name, separated by
1775 whitespace. The same directory as for the personal preferences file is
1778 Capture filter name resolution is handled by libpcap on UNIX-compatible
1779 systems and WinPcap on Windows. As such the Wireshark personal F<hosts> file
1780 will not be consulted for capture filter name resolution.
1782 =item Name Resolution (subnets)
1784 If an IPv4 address cannot be translated via name resolution (no exact
1785 match is found) then a partial match is attempted via the F<subnets> file.
1787 Each line of this file consists of an IPv4 address, a subnet mask length
1788 separated only by a / and a name separated by whitespace. While the address
1789 must be a full IPv4 address, any values beyond the mask length are subsequently
1794 # Comments must be prepended by the # sign!
1795 192.168.0.0/24 ws_test_network
1797 A partially matched name will be printed as "subnet-name.remaining-address".
1798 For example, "192.168.0.1" under the subnet above would be printed as
1799 "ws_test_network.1"; if the mask length above had been 16 rather than 24, the
1800 printed address would be ``ws_test_network.0.1".
1802 =item Name Resolution (ethers)
1804 The F<ethers> files are consulted to correlate 6-byte hardware addresses to
1805 names. First the personal F<ethers> file is tried and if an address is not
1806 found there the global F<ethers> file is tried next.
1808 Each line contains one hardware address and name, separated by
1809 whitespace. The digits of the hardware address are separated by colons
1810 (:), dashes (-) or periods (.). The same separator character must be
1811 used consistently in an address. The following three lines are valid
1812 lines of an F<ethers> file:
1814 ff:ff:ff:ff:ff:ff Broadcast
1815 c0-00-ff-ff-ff-ff TR_broadcast
1816 00.00.00.00.00.00 Zero_broadcast
1818 The global F<ethers> file is looked for in the F</etc> directory on
1819 UNIX-compatible systems, and in the main installation directory (for
1820 example, F<C:\Program Files\Wireshark>) on Windows systems.
1822 The personal F<ethers> file is looked for in the same directory as the personal
1825 Capture filter name resolution is handled by libpcap on UNIX-compatible
1826 systems and WinPcap on Windows. As such the Wireshark personal F<ethers> file
1827 will not be consulted for capture filter name resolution.
1829 =item Name Resolution (manuf)
1831 The F<manuf> file is used to match the 3-byte vendor portion of a 6-byte
1832 hardware address with the manufacturer's name; it can also contain well-known
1833 MAC addresses and address ranges specified with a netmask. The format of the
1834 file is the same as the F<ethers> files, except that entries of the form:
1838 can be provided, with the 3-byte OUI and the name for a vendor, and
1841 00-00-0C-07-AC/40 All-HSRP-routers
1843 can be specified, with a MAC address and a mask indicating how many bits
1844 of the address must match. The above entry, for example, has 40
1845 significant bits, or 5 bytes, and would match addresses from
1846 00-00-0C-07-AC-00 through 00-00-0C-07-AC-FF. The mask need not be a
1849 The F<manuf> file is looked for in the same directory as the global
1852 =item Name Resolution (services)
1854 The F<services> file is used to translate port numbers into names.
1856 The file has the standard F<services> file syntax; each line contains one
1857 (service) name and one transport identifier separated by white space. The
1858 transport identifier includes one port number and one transport protocol name
1859 (typically tcp, udp, or sctp) separated by a /.
1863 mydns 5045/udp # My own Domain Name Server
1864 mydns 5045/tcp # My own Domain Name Server
1866 =item Name Resolution (ipxnets)
1868 The F<ipxnets> files are used to correlate 4-byte IPX network numbers to
1869 names. First the global F<ipxnets> file is tried and if that address is not
1870 found there the personal one is tried next.
1872 The format is the same as the F<ethers>
1873 file, except that each address is four bytes instead of six.
1874 Additionally, the address can be represented as a single hexadecimal
1875 number, as is more common in the IPX world, rather than four hex octets.
1876 For example, these four lines are valid lines of an F<ipxnets> file:
1880 00:00:BE:EF IT_Server1
1883 The global F<ipxnets> file is looked for in the F</etc> directory on
1884 UNIX-compatible systems, and in the main installation directory (for
1885 example, F<C:\Program Files\Wireshark>) on Windows systems.
1887 The personal F<ipxnets> file is looked for in the same directory as the
1888 personal preferences file.
1894 B<TShark> uses UTF-8 to represent strings internally. In some cases the
1895 output might not be valid. For example, a dissector might generate
1896 invalid UTF-8 character sequences. Programs reading B<TShark> output
1897 should expect UTF-8 and be prepared for invalid output.
1899 If B<TShark> detects that it is writing to a TTY on UNIX or Linux and
1900 the locale does not support UTF-8, output will be re-encoded to match the
1903 If B<TShark> detects that it is writing to a TTY on Windows, output will be
1904 encoded as UTF-16LE.
1906 =head1 ENVIRONMENT VARIABLES
1910 =item WIRESHARK_APPDATA
1912 On Windows, Wireshark normally stores all application data in %APPDATA% or
1913 %USERPROFILE%. You can override the default location by exporting this
1914 environment variable to specify an alternate location.
1916 =item WIRESHARK_DEBUG_WMEM_OVERRIDE
1918 Setting this environment variable forces the wmem framework to use the
1919 specified allocator backend for *all* allocations, regardless of which
1920 backend is normally specified by the code. This is mainly useful to developers
1921 when testing or debugging. See I<README.wmem> in the source distribution for
1924 =item WIRESHARK_RUN_FROM_BUILD_DIRECTORY
1926 This environment variable causes the plugins and other data files to be loaded
1927 from the build directory (where the program was compiled) rather than from the
1928 standard locations. It has no effect when the program in question is running
1929 with root (or setuid) permissions on *NIX.
1931 =item WIRESHARK_DATA_DIR
1933 This environment variable causes the various data files to be loaded from
1934 a directory other than the standard locations. It has no effect when the
1935 program in question is running with root (or setuid) permissions on *NIX.
1937 =item ERF_RECORDS_TO_CHECK
1939 This environment variable controls the number of ERF records checked when
1940 deciding if a file really is in the ERF format. Setting this environment
1941 variable a number higher than the default (20) would make false positives
1944 =item IPFIX_RECORDS_TO_CHECK
1946 This environment variable controls the number of IPFIX records checked when
1947 deciding if a file really is in the IPFIX format. Setting this environment
1948 variable a number higher than the default (20) would make false positives
1951 =item WIRESHARK_ABORT_ON_DISSECTOR_BUG
1953 If this environment variable is set, B<TShark> will call abort(3)
1954 when a dissector bug is encountered. abort(3) will cause the program to
1955 exit abnormally; if you are running B<TShark> in a debugger, it
1956 should halt in the debugger and allow inspection of the process, and, if
1957 you are not running it in a debugger, it will, on some OSes, assuming
1958 your environment is configured correctly, generate a core dump file.
1959 This can be useful to developers attempting to troubleshoot a problem
1960 with a protocol dissector.
1962 =item WIRESHARK_ABORT_ON_TOO_MANY_ITEMS
1964 If this environment variable is set, B<TShark> will call abort(3)
1965 if a dissector tries to add too many items to a tree (generally this
1966 is an indication of the dissector not breaking out of a loop soon enough).
1967 abort(3) will cause the program to exit abnormally; if you are running
1968 B<TShark> in a debugger, it should halt in the debugger and allow
1969 inspection of the process, and, if you are not running it in a debugger,
1970 it will, on some OSes, assuming your environment is configured correctly,
1971 generate a core dump file. This can be useful to developers attempting to
1972 troubleshoot a problem with a protocol dissector.
1978 wireshark-filter(4), wireshark(1), editcap(1), pcap(3), dumpcap(1),
1979 text2pcap(1), mergecap(1), pcap-filter(7) or tcpdump(8)
1983 B<TShark> is part of the B<Wireshark> distribution. The latest version
1984 of B<Wireshark> can be found at L<https://www.wireshark.org>.
1986 HTML versions of the Wireshark project man pages are available at:
1987 L<https://www.wireshark.org/docs/man-pages>.
1991 B<TShark> uses the same packet dissection code that B<Wireshark> does,
1992 as well as using many other modules from B<Wireshark>; see the list of
1993 authors in the B<Wireshark> man page for a list of authors of that code.