1TSHARK(1) The Wireshark Network Analyzer TSHARK(1)
2
6 tshark - Dump and analyze network traffic
7
9 tshark [ -a <capture autostop condition> ] ... [ -b <capture ring buf‐
10 fer option>] ... [ -B <capture buffer size (Win32 only)> ] [ -c <cap‐
11 ture packet count> ] [ -C <configuration profile> ]
12 [ -d <layer type>==<selector>,<decode-as protocol> ] [ -D ]
13 [ -e <field> ] [ -E <field print option> ] [ -f <capture filter> ]
14 [ -F <file format> ] [ -h ] [ -i <capture interface>⎪- ] [ -l ] [ -L ]
15 [ -n ] [ -N <name resolving flags> ] [ -o <preference setting> ] ...
16 [ -p ] [ -q ] [ -r <infile> ] [ -R <read (display) filter> ] [ -s <cap‐
17 ture snaplen> ] [ -S ] [ -t ad⎪a⎪r⎪d⎪e ]
18 [ -T pdml⎪psml⎪ps⎪text⎪fields ] [ -v ] [ -V ] [ -w <outfile>⎪- ] [ -x ]
19 [ -X <eXtension option>] [ -y <capture link type> ] [ -z <statistics> ]
20 [ <capture filter> ]
21
23 TShark is a network protocol analyzer. It lets you capture packet data
24 from a live network, or read packets from a previously saved capture
25 file, either printing a decoded form of those packets to the standard
26 output or writing the packets to a file. TShark's native capture file
27 format is libpcap format, which is also the format used by tcpdump and
28 various other tools.
29 Without any options set, TShark will work much like tcpdump. It will
31 use the pcap library to capture traffic from the first available net‐
32 work interface and displays a summary line on stdout for each received
33 packet.
34 TShark is able to detect, read and write the same capture files that
36 are supported by Wireshark. The input file doesn't need a specific
37 filename extension; the file format and an optional gzip compression
38 will be automatically detected. Near the beginning of the DESCRIPTION
39 section of wireshark(1) or <http://www.wire‐
40 shark.org/docs/man-pages/wireshark.html> is a detailed description of
41 the way Wireshark handles this, which is the same way Tshark handles
42 this.
43 Compressed file support uses (and therefore requires) the zlib library.
45 If the zlib library is not present, TShark will compile, but will be
46 unable to read compressed files.
47 If the -w option is not specified, TShark writes to the standard output
49 the text of a decoded form of the packets it captures or reads. If the
50 -w option is specified, TShark writes to the file specified by that
51 option the raw data of the packets, along with the packets' time
52 stamps.
53 When writing a decoded form of packets, TShark writes, by default, a
55 summary line containing the fields specified by the preferences file
56 (which are also the fields displayed in the packet list pane in Wire‐
57 shark), although if it's writing packets as it captures them, rather
58 than writting packets from a saved capture file, it won't show the
59 "frame number" field. If the -V option is specified, it writes instead
60 a view of the details of the packet, showing all the fields of all pro‐
61 tocols in the packet.
62 If you want to write the decoded form of packets to a file, run TShark
64 without the -w option, and redirect its standard output to the file (do
65 not use the -w option).
66 When writing packets to a file, TShark, by default, writes the file in
68 libpcap format, and writes all of the packets it sees to the output
69 file. The -F option can be used to specify the format in which to
70 write the file. This list of available file formats is displayed by the
71 -F flag without a value. However, you can't specify a file format for a
72 live capture.
73 Read filters in TShark, which allow you to select which packets are to
75 be decoded or written to a file, are very powerful; more fields are
76 filterable in TShark than in other protocol analyzers, and the syntax
77 you can use to create your filters is richer. As TShark progresses,
78 expect more and more protocol fields to be allowed in read filters.
79 Packet capturing is performed with the pcap library. The capture fil‐
81 ter syntax follows the rules of the pcap library. This syntax is dif‐
82 ferent from the read filter syntax. A read filter can also be speci‐
83 fied when capturing, and only packets that pass the read filter will be
84 displayed or saved to the output file; note, however, that capture fil‐
85 ters are much more efficient than read filters, and it may be more dif‐
86 ficult for TShark to keep up with a busy network if a read filter is
87 specified for a live capture.
88 A capture or read filter can either be specified with the -f or -R
90 option, respectively, in which case the entire filter expression must
91 be specified as a single argument (which means that if it contains spa‐
92 ces, it must be quoted), or can be specified with command-line argu‐
93 ments after the option arguments, in which case all the arguments after
94 the filter arguments are treated as a filter expression. Capture fil‐
95 ters are supported only when doing a live capture; read filters are
96 supported when doing a live capture and when reading a capture file,
97 but require TShark to do more work when filtering, so you might be more
98 likely to lose packets under heavy load if you're using a read filter.
99 If the filter is specified with command-line arguments after the option
100 arguments, it's a capture filter if a capture is being done (i.e., if
101 no -r option was specified) and a read filter if a capture file is
102 being read (i.e., if a -r option was specified).
103
105 -a <capture autostop condition>
106 Specify a criterion that specifies when TShark is to stop writing
107 to a capture file. The criterion is of the form test:value, where
108 test is one of:
109 duration:value Stop writing to a capture file after value seconds
111 have elapsed.
112 filesize:value Stop writing to a capture file after it reaches a
114 size of value kilobytes (where a kilobyte is 1024 bytes). If this
115 option is used together with the -b option, TShark will stop writ‐
116 ing to the current capture file and switch to the next one if file‐
117 size is reached. When reading a capture file, TShark will stop
118 reading the file after the number of bytes read exceeds this number
119 (the complete packet will be read, so more bytes than this number
120 may be read).
121 files:value Stop writing to capture files after value number of
123 files were written.
124 -b <capture ring buffer option>
126 Cause TShark to run in "multiple files" mode. In "multiple files"
127 mode, TShark will write to several capture files. When the first
128 capture file fills up, TShark will switch writing to the next file
129 and so on.
130 The created filenames are based on the filename given with the -w
132 option, the number of the file and on the creation date and time,
133 e.g. outfile_00001_20050604120117.pcap, out‐
134 file_00001_20050604120523.pcap, ...
135 With the files option it's also possible to form a "ring buffer".
137 This will fill up new files until the number of files specified, at
138 which point TShark will discard the data in the first file and
139 start writing to that file and so on. If the files option is not
140 set, new files filled up until one of the capture stop conditions
141 match (or until the disk if full).
142 The criterion is of the form key:value, where key is one of:
144 duration:value switch to the next file after value seconds have
146 elapsed, even if the current file is not completely filled up.
147 filesize:value switch to the next file after it reaches a size of
149 value kilobytes (where a kilobyte is 1024 bytes).
150 files:value begin again with the first file after value number of
152 files were written (form a ring buffer).
153 -B <capture buffer size (Win32 only)>
155 Win32 only: set capture buffer size (in MB, default is 1MB). This
156 is used by the the capture driver to buffer packet data until that
157 data can be written to disk. If you encounter packet drops while
158 capturing, try to increase this size.
159 -c <capture packet count>
161 Set the maximum number of packets to read when capturing live data.
162 If reading a capture file, set the maximum number of packets to
163 read.
164 -C <configuration profile>
166 Run with the given configuration profile.
167 -d <layer type>==<selector>,<decode-as protocol>
169 Specify that if the layer type in question (for example, tcp.port
170 or udp.port for a TCP or UDP port number) has the specified selec‐
171 tor value, packets should be dissected as the specified protocol.
172 Example: -d tcp.port==8888,http will decode any traffic running
174 over TCP port 8888 as HTTP.
175 -D Print a list of the interfaces on which TShark can capture, and
177 exit. For each network interface, a number and an interface name,
178 possibly followed by a text description of the interface, is
179 printed. The interface name or the number can be supplied to the
180 -i option to specify an interface on which to capture.
181 This can be useful on systems that don't have a command to list
183 them (e.g., Windows systems, or UNIX systems lacking ifconfig -a);
184 the number can be useful on Windows 2000 and later systems, where
185 the interface name is a somewhat complex string.
186 Note that "can capture" means that TShark was able to open that
188 device to do a live capture. Depending on your system you may need
189 to run tshark from an account with special privileges (for example,
190 as root) to be able to capture network traffic. If TShark -D is
191 not run from such an account, it will not list any interfaces.
192 -e <field>
194 Add a field to the list of fields to display if -T fields is
195 selected. This option can be used multiple times on the command
196 line. At least one field must be provided if the -T fields option
197 is selected.
198 Example: -e frame.number -e ip.addr -e udp
200 Giving a protocol rather than a single field will print multiple
202 items of data about the protocol as a single field. Fields are
203 separated by tab characters by default. -E controls the format of
204 the printed fields.
205 -E <field print option>
207 Set an option controlling the printing of fields when -T fields is
208 selected.
209 Options are:
211 header=y⎪n If y, print a list of the field names given using -e as
213 the first line of the output; the field name will be separated
214 using the same character as the field values. Defaults to n.
215 separator=/t⎪/s⎪<character> Set the separator character to use for
217 fields. If /t tab will be used (this is the default), if /s, s
218 single space will be used. Otherwise any character that can be
219 accepted by the command line as part of the option may be used.
220 quote=d⎪s⎪n Set the quote character to use to surround fields. d
222 uses double-quotes, s single-quotes, n no quotes (the default).
223 -f <capture filter>
225 Set the capture filter expression.
226 -F <file format>
228 Set the file format of the output capture file written using the -w
229 option. The output written with the -w option is raw packet data,
230 not text, so there is no -F option to request text output. The
231 option -F without a value will list the available formats.
232 -h Print the version and options and exits.
234 -i <capture interface>⎪-
236 Set the name of the network interface or pipe to use for live
237 packet capture.
238 Network interface names should match one of the names listed in
240 "tshark -D" (described above); a number, as reported by "tshark
241 -D", can also be used. If you're using UNIX, "netstat -i" or
242 "ifconfig -a" might also work to list interface names, although not
243 all versions of UNIX support the -a option to ifconfig.
244 If no interface is specified, TShark searches the list of inter‐
246 faces, choosing the first non-loopback interface if there are any
247 non-loopback interfaces, and choosing the first loopback interface
248 if there are no non-loopback interfaces. If there are no interfaces
249 at all, TShark reports an error and doesn't start the capture.
250 Pipe names should be either the name of a FIFO (named pipe) or
252 ``-'' to read data from the standard input. Data read from pipes
253 must be in standard libpcap format.
254 Note: the Win32 version of TShark doesn't support capturing from
256 pipes!
257 -l Flush the standard output after the information for each packet is
259 printed. (This is not, strictly speaking, line-buffered if -V was
260 specified; however, it is the same as line-buffered if -V wasn't
261 specified, as only one line is printed for each packet, and, as -l
262 is normally used when piping a live capture to a program or script,
263 so that output for a packet shows up as soon as the packet is seen
264 and dissected, it should work just as well as true line-buffering.
265 We do this as a workaround for a deficiency in the Microsoft Visual
266 C++ C library.)
267 This may be useful when piping the output of TShark to another pro‐
269 gram, as it means that the program to which the output is piped
270 will see the dissected data for a packet as soon as TShark sees the
271 packet and generates that output, rather than seeing it only when
272 the standard output buffer containing that data fills up.
273 -L List the data link types supported by the interface and exit. The
275 reported link types can be used for the -y option.
276 -n Disable network object name resolution (such as hostname, TCP and
278 UDP port names), the -N flag might override this one.
279 -N <name resolving flags>
281 Turn on name resolving only for particular types of addresses and
282 port numbers, with name resolving for other types of addresses and
283 port numbers turned off. This flag overrides -n if both -N and -n
284 are present. If both -N and -n flags are not present, all name res‐
285 olutions are turned on.
286 The argument is a string that may contain the letters:
288 m to enable MAC address resolution
290 n to enable network address resolution
292 t to enable transport-layer port number resolution
294 C to enable concurrent (asynchronous) DNS lookups
296 -o <preference>:<value>
298 Set a preference value, overriding the default value and any value
299 read from a preference file. The argument to the option is a
300 string of the form prefname:value, where prefname is the name of
301 the preference (which is the same name that would appear in the
302 preference file), and value is the value to which it should be set.
303 -p Don't put the interface into promiscuous mode. Note that the
305 interface might be in promiscuous mode for some other reason;
306 hence, -p cannot be used to ensure that the only traffic that is
307 captured is traffic sent to or from the machine on which TShark is
308 running, broadcast traffic, and multicast traffic to addresses
309 received by that machine.
310 -q When capturing packets, don't display the continuous count of pack‐
312 ets captured that is normally shown when saving a capture to a
313 file; instead, just display, at the end of the capture, a count of
314 packets captured. On systems that support the SIGINFO signal, such
315 as various BSDs, you can cause the current count to be displayed by
316 typing your "status" character (typically control-T, although it
317 might be set to "disabled" by default on at least some BSDs, so
318 you'd have to explicitly set it to use it).
319 When reading a capture file, or when capturing and not saving to a
321 file, don't print packet information; this is useful if you're
322 using a -z option to calculate statistics and don't want the packet
323 information printed, just the statistics.
324 -r <infile>
326 Read packet data from infile, can be any supported capture file
327 format (including gzipped files). It's not possible to use named
328 pipes or stdin here!
329 -R <read (display) filter>
331 Cause the specified filter (which uses the syntax of read/display
332 filters, rather than that of capture filters) to be applied before
333 printing a decoded form of packets or writing packets to a file;
334 packets not matching the filter are discarded rather than being
335 printed or written.
336 -s <capture snaplen>
338 Set the default snapshot length to use when capturing live data.
339 No more than snaplen bytes of each network packet will be read into
340 memory, or saved to disk.
341 -S Decode and display packets even while writing raw packet data using
343 the -w option.
344 -t ad⎪a⎪r⎪d⎪e
346 Set the format of the packet timestamp printed in summary lines,
347 the default is relative. The format can be one of:
348 ad absolute with date: The absolute date and time is the actual
350 time and date the packet was captured
351 a absolute: The absolute time is the actual time the packet was
353 captured, with no date displayed
354 r relative: The relative time is the time elapsed between the first
356 packet and the current packet
357 d delta: The delta time is the time since the previous packet was
359 captured
360 e epoch: The time in seconds since epoch (Jan 1, 1970 00:00:00)
362 -T pdml⎪psml⎪ps⎪text⎪fields
364 Set the format of the output when viewing decoded packet data. The
365 options are one of:
366 pdml Packet Details Markup Language, an XML-based format for the
368 details of a decoded packet. This information is equivalent to the
369 packet details printed with the -V flag.
370 psml Packet Summary Markup Language, an XML-based format for the
372 summary information of a decoded packet. This information is
373 equivalent to the information shown in the one-line summary printed
374 by default.
375 ps PostScript for a human-readable one-line summary of each of the
377 packets, or a multi-line view of the details of each of the pack‐
378 ets, depending on whether the -V flag was specified.
379 text Text of a human-readable one-line summary of each of the pack‐
381 ets, or a multi-line view of the details of each of the packets,
382 depending on whether the -V flag was specified. This is the
383 default.
384 fields The values of fields specified with the -e option, in a form
386 specified by the -E option.
387 -v Print the version and exit.
389 -V Cause TShark to print a view of the packet details rather than a
391 one-line summary of the packet.
392 -w <outfile>⎪-
394 Write raw packet data to outfile or to the standard output if out‐
395 file is '-'.
396 NOTE: -w provides raw packet data, not text. If you want text out‐
398 put you need to redirect stdout (e.g. using '>'), don't use the -w
399 option for this.
400 -x Cause TShark to print a hex and ASCII dump of the packet data after
402 printing the summary or details.
403 -X <eXtension options>
405 Specify an option to be passed to a TShark module. The eXtension
406 option is in the form extension_key:value, where extension_key can
407 be:
408 lua_script:lua_script_filename tells Wireshark to load the given
410 script in addition to the default Lua scripts.
411 -y <capture link type>
413 Set the data link type to use while capturing packets. The values
414 reported by -L are the values that can be used.
415 -z <statistics>
417 Get TShark to collect various types of statistics and display the
418 result after finishing reading the capture file. Use the -q flag
419 if you're reading a capture file and only want the statistics
420 printed, not any per-packet information.
421 Note that the -z proto option is different - it doesn't cause sta‐
423 tistics to be gathered and printed when the capture is complete, it
424 modifies the regular packet summary output to include the values of
425 fields specified with the option. Therefore you must not use the
426 -q option, as that option would suppress the printing of the regu‐
427 lar packet summary output, and must also not use the -V option, as
428 that would cause packet detail information rather than packet sum‐
429 mary information to be printed.
430 Currently implemented statistics are:
432 -z dcerpc,rtt,uuid,major.minor[,filter]
434 Collect call/reply RTT data for DCERPC interface uuid, version
436 major.minor. Data collected is number of calls for each procedure,
437 MinRTT, MaxRTT and AvgRTT. Example: use -z
438 dcerpc,rtt,12345778-1234-abcd-ef00-0123456789ac,1.0 to collect data
439 for CIFS SAMR Interface. This option can be used multiple times on
440 the command line.
441 If the optional filterstring is provided, the stats will only be
443 calculated on those calls that match that filter. Example: use -z
444 dcerpc,rtt,12345778-1234-abcd-ef00-0123456789ac,1.0,ip.addr==1.2.3.4
445 to collect SAMR RTT statistics for a specific host.
446 -z io,phs[,filter]
448 Create Protocol Hierarchy Statistics listing both number of packets
450 and bytes. If no filter is specified the statistics will be calcu‐
451 lated for all packets. If a filters is specified statistics will
452 be only calculated for those packets that match the filter.
453 This option can be used multiple times on the command line.
455 -z io,stat,interval[,filter][,filter][,filter]...
457 Collect packet/bytes statistics for the capture in intervals of
459 interval seconds. Intervals can be specified either as whole or
460 fractional seconds. Interval can be specified in ms resolution.
461 If no filter is specified the statistics will be calculated for all
463 packets. If one or more filters are specified statistics will be
464 calculated for all filters and presented with one column of statis‐
465 tics for each filter.
466 This option can be used multiple times on the command line.
468 Example: -z io,stat,1,ip.addr==1.2.3.4 to generate 1 second statis‐
470 tics for all traffic to/from host 1.2.3.4.
471 Example: -z "io,stat,0.001,smb&&ip.addr==1.2.3.4" to generate 1ms
473 statistics for all SMB packets to/from host 1.2.3.4.
474 The examples above all use the standard syntax for generating sta‐
476 tistics which only calculates the number of packets and bytes in
477 each interval.
478 io,stat can also do much more statistics and calculate COUNT(),
480 SUM(), MIN(), MAX(), and AVG() using a slightly different filter
481 syntax:
482 [COUNT⎪SUM⎪MIN⎪MAX⎪AVG](<field>)<filter>
484 One important thing to note here is that the field that the calcu‐
486 lation is based on MUST also be part of the filter string or else
487 the calculation will fail.
488 So: -z io,stat,0.010,AVG(smb.time) does not work. Use -z
490 io,stat,0.010,AVG(smb.time)smb.time instead. Also be aware that a
491 field can exist multiple times inside the same packet and will then
492 be counted multiple times in those packets.
493 COUNT(<field>) can be used on any type which has a display filter
495 name. It will count how many times this particular field is
496 encountered in the filtered packet list.
497 Example: -z io,stat,0.010,COUNT(smb.sid)smb.sid This will count the
499 total number of SIDs seen in each 10ms interval.
500 SUM(<field>) can only be used on named fields of integer type.
502 This will sum together every occurence of this fields value for
503 each interval.
504 Example: -z io,stat,0.010,SUM(frame.pkt_len)frame.pkt_len This will
506 report the total number of bytes seen in all the packets within an
507 interval.
508 MIN/MAX/AVG(<field>) can only be used on named fields that are
510 either integers or relative time fields. This will calculate maxi‐
511 mum/minimum or average seen in each interval. If the field is a
512 relative time field the output will be presented in seconds and
513 three digits after the decimal point. The resolution for time cal‐
514 culations is 1ms and anything smaller will be truncated.
515 Example: -z
517 "io,stat,0.010,smb.time&&ip.addr==1.1.1.1,MIN(smb.time)smb.time&&ip.addr==1.1.1.1,MAX(smb.time)smb.time&&ip.addr==1.1.1.1,MAX(smb.time)smb.time&&ip.addr==1.1.1.1"
518 This will calculate statistics for all smb response times we see
520 to/from host 1.1.1.1 in 10ms intervals. The output will be dis‐
521 played in 4 columns; number of packets/bytes, minimum response
522 time, maximum response time and average response time.
523 -z conv,type[,filter]
525 Create a table that lists all conversations that could be seen in
527 the capture. type specifies which type of conversation we want to
528 generate the statistics for; currently the supported ones are
529 "eth" Ethernet
531 "fc" Fibre Channel
532 "fddi" FDDI
533 "ip" IP addresses
534 "ipx" IPX addresses
535 "tcp" TCP/IP socket pairs Both IPv4 and IPv6 are supported
536 "tr" Token Ring
537 "udp" UDP/IP socket pairs Both IPv4 and IPv6 are supported
538 If the optional filter string is specified, only those packets that
540 match the filter will be used in the calculations.
541 The table is presented with one line for each conversation and dis‐
543 plays number of packets/bytes in each direction as well as total
544 number of packets/bytes. The table is sorted according to total
545 number of bytes.
546 -z proto,colinfo,filter,field
548 Append all field values for the packet to the Info column of the
550 one-line summary output. This feature can be used to append arbi‐
551 trary fields to the Info column in addition to the normal content
552 of that column. field is the display-filter name of a field which
553 value should be placed in the Info column. filter is a filter
554 string that controls for which packets the field value will be pre‐
555 sented in the info column. field will only be presented in the Info
556 column for the packets which match filter.
557 NOTE: In order for TShark to be able to extract the field value
559 from the packet, field MUST be part of the filter string. If not,
560 TShark will not be able to extract its value.
561 For a simple example to add the "nfs.fh.hash" field to the Info
563 column for all packets containing the "nfs.fh.hash" field, use
564 -z proto,colinfo,nfs.fh.hash,nfs.fh.hash
566 To put "nfs.fh.hash" in the Info column but only for packets coming
568 from host 1.2.3.4 use:
569 -z "proto,colinfo,nfs.fh.hash && ip.src==1.2.3.4,nfs.fh.hash"
571 This option can be used multiple times on the command line.
573 -z rpc,rtt,program,version[,filter]
575 Collect call/reply RTT data for program/version. Data collected is
577 number of calls for each procedure, MinRTT, MaxRTT and AvgRTT.
578 Example: use -z rpc,rtt,100003,3 to collect data for NFS v3. This
579 option can be used multiple times on the command line.
580 If the optional filterstring is provided, the stats will only be
582 calculated on those calls that match that filter. Example: use -z
583 rpc,rtt,100003,3,nfs.fh.hash==0x12345678 to collect NFS v3 RTT sta‐
584 tistics for a specific file.
585 -z rpc,programs
587 Collect call/reply RTT data for all known ONC-RPC programs/ver‐
589 sions. Data collected is number of calls for each protocol/ver‐
590 sion, MinRTT, MaxRTT and AvgRTT. This option can only be used once
591 on the command line.
592 -z rtp,streams
594 Collect statistics for all RTP streams and calculate max. delta,
596 max. and mean jitter and packet loss percentages.
597 -z smb,rtt[,filter]
599 Collect call/reply RTT data for SMB. Data collected is number of
601 calls for each SMB command, MinRTT, MaxRTT and AvgRTT. Example:
602 use -z smb,rtt. The data will be presented as separate tables for
603 all normal SMB commands, all Transaction2 commands and all NT
604 Transaction commands. Only those commands that are seen in the
605 capture will have its stats displayed. Only the first command in a
606 xAndX command chain will be used in the calculation. So for common
607 SessionSetupAndX + TreeConnectAndX chains, only the SessionSetu‐
608 pAndX call will be used in the statistics. This is a flaw that
609 might be fixed in the future.
610 This option can be used multiple times on the command line.
612 If the optional filterstring is provided, the stats will only be
614 calculated on those calls that match that filter. Example: use -z
615 "smb,rtt,ip.addr==1.2.3.4" to only collect stats for SMB packets
616 echanged by the host at IP address 1.2.3.4 .
617 -z smb,sids
619 When this feature is used TShark will print a report with all the
621 discovered SID and account name mappings. Only those SIDs where
622 the account name is known will be presented in the table.
623 For this feature to work you will need to either to enable
625 "Edit/Preferences/Protocols/SMB/Snoop SID to name mappings" in the
626 preferences or you can override the preferences by specifying -o
627 "smb.sid_name_snooping:TRUE" on the TShark command line.
628 The current methods used by TShark to find the SID->name mapping is
630 relatively restricted but is hoped to be expanded in the future.
631 -z mgcp,rtd[,filter]
633 Collect requests/response RTD (Response Time Delay) data for MGCP.
635 This is similar to -z smb,rtt). Data collected is number of calls
636 for each known MGCP Type, MinRTD, MaxRTD and AvgRTD. Additionally
637 you get the number of duplicate requests/responses, unresponded
638 requests, responses ,which don't match with any request. Example:
639 use -z mgcp,rtd.
640 This option can be used multiple times on the command line.
642 If the optional filterstring is provided, the stats will only be
644 calculated on those calls that match that filter. Example: use -z
645 "mgcp,rtd,ip.addr==1.2.3.4" to only collect stats for MGCP packets
646 exchanged by the host at IP address 1.2.3.4 .
647 -z h225,counter[,filter]
649 Count ITU-T H.225 messages and their reasons. In the first column
651 you get a list of H.225 messages and H.225 message reasons, which
652 occur in the current capture file. The number of occurences of each
653 message or reason is displayed in the second column.
654 Example: use -z h225,counter.
656 This option can be used multiple times on the command line.
658 If the optional filterstring is provided, the stats will only be
660 calculated on those calls that match that filter. Example: use -z
661 "h225,counter,ip.addr==1.2.3.4" to only collect stats for H.225
662 packets exchanged by the host at IP address 1.2.3.4 .
663 -z h225,srt[,filter]
665 Collect requests/response SRT (Service Response Time) data for ITU-
667 T H.225 RAS. Data collected is number of calls of each ITU-T H.225
668 RAS Message Type, Minimum SRT, Maximum SRT, Average SRT, Minimum in
669 Frame, and Maximum in Frame. You will also get the number of Open
670 Requests (Unresponded Requests), Discarded Responses (Responses
671 without matching request) and Duplicate Messages. Example: use -z
672 h225,srt.
673 This option can be used multiple times on the command line.
675 If the optional filterstring is provided, the stats will only be
677 calculated on those calls that match that filter. Example: use -z
678 "h225,srt,ip.addr==1.2.3.4" to only collect stats for ITU-T H.225
679 RAS packets exchanged by the host at IP address 1.2.3.4 .
680 -z sip,stat[,filter]
682 This option will activate a counter for SIP messages. You will get
684 the number of occurences of each SIP Method and of each SIP Sta‐
685 tus-Code. Additionally you also get the number of resent SIP Mes‐
686 sages (only for SIP over UDP).
687 Example: use -z sip,stat.
689 This option can be used multiple times on the command line.
691 If the optional filter string is provided, the stats will only be
693 calculated on those calls that match that filter. Example: use -z
694 "sip,stat,ip.addr==1.2.3.4" to only collect stats for SIP packets
695 exchanged by the host at IP address 1.2.3.4 .
696
698 See the manual page of pcap-filter(4) or, if that doesn't exist, tcp‐
699 dump(8).
700
702 For a complete table of protocol and protocol fields that are filter‐
703 able in TShark see the wireshark-filter(4) manual page.
704
706 These files contains various Wireshark configuration values.
707 Preferences
709 The preferences files contain global (system-wide) and personal
710 preference settings. If the system-wide preference file exists, it
711 is read first, overriding the default settings. If the personal
712 preferences file exists, it is read next, overriding any previous
713 values. Note: If the command line option -o is used (possibly more
714 than once), it will in turn override values from the preferences
715 files.
716 The preferences settings are in the form prefname:value, one per
718 line, where prefname is the name of the preference and value is the
719 value to which it should be set; white space is allowed between :
720 and value. A preference setting can be continued on subsequent
721 lines by indenting the continuation lines with white space. A #
722 character starts a comment that runs to the end of the line:
723 # Capture in promiscuous mode?
725 # TRUE or FALSE (case-insensitive).
726 capture.prom_mode: TRUE
727 The global preferences file is looked for in the wireshark direc‐
729 tory under the share subdirectory of the main installation direc‐
730 tory (for example, /usr/local/share/wireshark/preferences) on UNIX-
731 compatible systems, and in the main installation directory (for
732 example, C:\Program Files\Wireshark\preferences) on Windows sys‐
733 tems.
734 The personal preferences file is looked for in $HOME/.wire‐
736 shark/preferences on UNIX-compatible systems and %APPDATA%\Wire‐
737 shark\preferences (or, if %APPDATA% isn't defined, %USERPRO‐
738 FILE%\Application Data\Wireshark\preferences) on Windows systems.
739 Disabled (Enabled) Protocols
741 The disabled_protos files contain system-wide and personal lists of
742 protocols that have been disabled, so that their dissectors are
743 never called. The files contain protocol names, one per line,
744 where the protocol name is the same name that would be used in a
745 display filter for the protocol:
746 http
748 tcp # a comment
749 The global disabled_protos file uses the same directory as the
751 global preferences file.
752 The personal disabled_protos file uses the same directory as the
754 personal preferences file.
755 Name Resolution (hosts)
757 If the personal hosts file exists, it is used to resolve IPv4 and
758 IPv6 addresses before any other attempts are made to resolve them.
759 The file has the standard hosts file syntax; each line contains one
760 IP address and name, separated by whitespace. The same directory as
761 for the personal preferences file is used.
762 Name Resolution (ethers)
764 The ethers files are consulted to correlate 6-byte hardware
765 addresses to names. First the personal ethers file is tried and if
766 an address is not found there the global ethers file is tried next.
767 Each line contains one hardware address and name, separated by
769 whitespace. The digits of the hardware address are separated by
770 colons (:), dashes (-) or periods (.). The same separator charac‐
771 ter must be used consistently in an address. The following three
772 lines are valid lines of an ethers file:
773 ff:ff:ff:ff:ff:ff Broadcast
775 c0-00-ff-ff-ff-ff TR_broadcast
776 00.00.00.00.00.00 Zero_broadcast
777 The global ethers file is looked for in the /etc directory on UNIX-
779 compatible systems, and in the main installation directory (for
780 example, C:\Program Files\Wireshark) on Windows systems.
781 The personal ethers file is looked for in the same directory as the
783 personal preferences file.
784 Name Resolution (manuf)
786 The manuf file is used to match the 3-byte vendor portion of a
787 6-byte hardware address with the manufacturer's name; it can also
788 contain well-known MAC addresses and address ranges specified with
789 a netmask. The format of the file is the same as the ethers files,
790 except that entries of the form:
791 00:00:0C Cisco
793 can be provided, with the 3-byte OUI and the name for a vendor, and
795 entries such as:
796 00-00-0C-07-AC/40 All-HSRP-routers
798 can be specified, with a MAC address and a mask indicating how many
800 bits of the address must match. The above entry, for example, has
801 40 significant bits, or 5 bytes, and would match addresses from
802 00-00-0C-07-AC-00 through 00-00-0C-07-AC-FF. The mask need not be a
803 multiple of 8.
804 The manuf file is looked for in the same directory as the global
806 preferences file.
807 Name Resolution (ipxnets)
809 The ipxnets files are used to correlate 4-byte IPX network numbers
810 to names. First the global ipxnets file is tried and if that
811 address is not found there the personal one is tried next.
812 The format is the same as the ethers file, except that each address
814 is four bytes instead of six. Additionally, the address can be
815 represented as a single hexadecimal number, as is more common in
816 the IPX world, rather than four hex octets. For example, these
817 four lines are valid lines of an ipxnets file:
818 C0.A8.2C.00 HR
820 c0-a8-1c-00 CEO
821 00:00:BE:EF IT_Server1
822 110f FileServer3
823 The global ipxnets file is looked for in the /etc directory on
825 UNIX-compatible systems, and in the main installation directory
826 (for example, C:\Program Files\Wireshark) on Windows systems.
827 The personal ipxnets file is looked for in the same directory as
829 the personal preferences file.
830
832 wireshark-filter(4), wireshark(1), editcap(1), pcap-filter(4), tcp‐
833 dump(8), pcap(3), dumpcap(1), text2pcap(1)
834
836 TShark is part of the Wireshark distribution. The latest version of
837 Wireshark can be found at <http://www.wireshark.org>.
838 HTML versions of the Wireshark project man pages are available at:
840 <http://www.wireshark.org/docs/man-pages>.
841
843 TShark uses the same packet dissection code that Wireshark does, as
844 well as using many other modules from Wireshark; see the list of
845 authors in the Wireshark man page for a list of authors of that code.
8461.0.0 2008-03-29 TSHARK(1)