2013-06-09 20:52:15 +00:00
=begin man
=encoding utf8
=end man
1998-09-16 02:39:15 +00:00
=head1 NAME
2006-05-31 19:12:15 +00:00
wireshark - Interactively dump and analyze network traffic
1998-09-16 02:39:15 +00:00
2009-05-12 21:10:38 +00:00
=head1 SYNOPSIS
1998-09-16 02:39:15 +00:00
2006-05-31 19:12:15 +00:00
B<wireshark>
2008-02-15 22:36:24 +00:00
S<[ B<-i> E<lt>capture interfaceE<gt>|- ]>
2019-11-10 22:33:52 +00:00
S<[ B<-f> E<lt>capture filterE<gt> ]>
S<[ B<-Y> E<lt>displaY filterE<gt> ]>
2006-01-11 21:36:00 +00:00
S<[ B<-w> E<lt>outfileE<gt> ]>
2019-11-10 22:33:52 +00:00
S<[ B<options> ]>
2006-01-11 21:36:00 +00:00
S<[ E<lt>infileE<gt> ]>
1998-09-16 02:39:15 +00:00
=head1 DESCRIPTION
2006-05-31 19:12:15 +00:00
B<Wireshark> is a GUI network protocol analyzer. It lets you
1999-11-29 07:33:53 +00:00
interactively browse packet data from a live network or from a
2021-03-13 07:31:08 +00:00
previously saved capture file. B<Wireshark>'s native capture file
formats are B<pcapng> format and B<pcap> format; it can read and write
both formats.. B<pcap> format is also the format used by B<tcpdump> and
various other tools; B<tcpdump>, when using newer verions of the
B<libpcap> library, can also read some pcapng files, and, on newer
versions of macOS, can read all pcapng files and can write them as well.
2004-04-23 19:53:36 +00:00
2021-03-13 07:31:08 +00:00
B<Wireshark> can also read / import the following file formats:
2004-04-23 19:53:36 +00:00
=over 4
=item *
2021-03-13 07:31:08 +00:00
Oracle (previously Sun) B<snoop> and B<atmsnoop> captures
2004-04-23 19:53:36 +00:00
=item *
2021-03-13 07:31:08 +00:00
Finisar (previously Shomiti) B<Surveyor> captures
2011-10-26 04:53:48 +00:00
=item *
2021-03-13 07:31:08 +00:00
Microsoft B<Network Monitor> captures
2004-04-23 19:53:36 +00:00
=item *
Novell B<LANalyzer> captures
=item *
AIX's B<iptrace> captures
=item *
Cinco Networks B<NetXRay> captures
=item *
2021-03-13 07:31:08 +00:00
NETSCOUT (previously Network Associates/Network General) Windows-based
B<Sniffer> captures
2004-04-23 19:53:36 +00:00
=item *
2021-03-13 07:31:08 +00:00
Network General/Network Associates DOS-based B<Sniffer> captures
(compressed or uncompressed)
2004-04-23 19:53:36 +00:00
=item *
2021-03-13 07:31:08 +00:00
LiveAction (previously WildPackets/Savvius) B<*Peek>/B<EtherHelp>/B<PacketGrabber> captures
2004-04-23 19:53:36 +00:00
=item *
B<RADCOM>'s WAN/LAN analyzer captures
=item *
2021-03-13 07:31:08 +00:00
Viavi (previously Network Instruments) B<Observer> captures
2004-04-23 19:53:36 +00:00
=item *
B<Lucent/Ascend> router debug output
=item *
2021-03-13 07:31:08 +00:00
captures from HP-UX B<nettl>
2004-04-23 19:53:36 +00:00
=item *
B<Toshiba's> ISDN routers dump output
=item *
the output from B<i4btrace> from the ISDN4BSD project
=item *
2021-03-13 07:31:08 +00:00
traces from the B<EyeSDN> USB S0
2004-04-23 19:53:36 +00:00
=item *
2021-03-13 07:31:08 +00:00
the B<IPLog> format output from the Cisco Secure Intrusion Detection System
2004-04-23 19:53:36 +00:00
=item *
B<pppd logs> (pppdump format)
=item *
the output from VMS's B<TCPIPtrace>/B<TCPtrace>/B<UCX$TRACE> utilities
=item *
the text output from the B<DBS Etherwatch> VMS utility
=item *
Visual Networks' B<Visual UpTime> traffic capture
=item *
the output from B<CoSine> L2 debug
=item *
2021-03-13 07:31:08 +00:00
the output from InfoVista (previously Accellent) B<5View> LAN agents
2004-04-23 19:53:36 +00:00
=item *
2008-02-15 22:36:24 +00:00
Endace Measurement Systems' ERF format captures
2004-04-23 19:53:36 +00:00
=item *
Linux Bluez Bluetooth stack B<hcidump -w> traces
2006-05-11 05:09:15 +00:00
=item *
Catapult DCT2000 .out files
2011-10-26 04:53:48 +00:00
=item *
Gammu generated text output from Nokia DCT3 phones in Netmonitor mode
=item *
IBM Series (OS/400) Comm traces (ASCII & UNICODE)
=item *
Juniper Netscreen snoop files
=item *
Symbian OS btsnoop files
2007-12-24 04:09:56 +00:00
=item *
TamoSoft CommView files
2011-10-26 04:53:48 +00:00
=item *
Textronix K12xx 32bit .rf5 format files
=item *
Textronix K12 text file format captures
2009-02-16 07:31:44 +00:00
=item *
Apple PacketLogger files
2011-10-26 04:53:48 +00:00
=item *
2021-03-13 07:31:08 +00:00
Captures from Aethra Telecommunications' PC108 software for their test
2011-10-26 04:53:48 +00:00
instruments
2021-03-13 07:31:08 +00:00
=item *
Citrix NetScaler Trace files
=item *
Android Logcat binary and text format logs
=item *
Colasoft Capsa and PacketBuilder captures
=item *
Micropross mplog files
=item *
Unigraf DPA-400 DisplayPort AUX channel monitor traces
=item *
802.15.4 traces from Daintree's Sensor Network Analyzer
2012-12-07 21:01:19 +00:00
=item *
MPEG-2 Transport Streams as defined in ISO/IEC 13818-1
2021-03-13 07:31:08 +00:00
=item *
Log files from the _candump_ utility
=item *
Logs from the BUSMASTER tool
=item *
Ixia IxVeriWave raw captures
2013-03-30 10:21:19 +00:00
=item *
Rabbit Labs CAM Inspector files
2015-08-12 01:32:18 +00:00
=item *
2021-03-13 07:31:08 +00:00
_systemd_ journal files
=item *
3GPP TS 32.423 trace files
2015-08-12 01:32:18 +00:00
2009-06-03 06:38:21 +00:00
=back
2004-04-23 19:53:36 +00:00
2006-05-31 19:12:15 +00:00
There is no need to tell B<Wireshark> what type of
2008-02-15 22:36:24 +00:00
file you are reading; it will determine the file type by itself.
2006-05-31 19:12:15 +00:00
B<Wireshark> is also capable of reading any of these file formats if they
are compressed using gzip. B<Wireshark> recognizes this directly from
2004-02-11 20:30:28 +00:00
the file; the '.gz' extension is not required for this purpose.
1999-08-03 16:33:12 +00:00
2006-05-31 19:12:15 +00:00
Like other protocol analyzers, B<Wireshark>'s main window shows 3 views
1999-12-16 08:05:46 +00:00
of a packet. It shows a summary line, briefly describing what the
2004-05-03 23:37:39 +00:00
packet is. A packet details display is shown, allowing you to drill
down to exact protocol or field that you interested in. Finally, a hex
dump shows you exactly what the packet looks like when it goes over the
wire.
1999-08-03 16:33:12 +00:00
2006-05-31 19:12:15 +00:00
In addition, B<Wireshark> has some features that make it unique. It can
1999-10-30 06:42:10 +00:00
assemble all the packets in a TCP conversation and show you the ASCII
2000-08-09 06:38:53 +00:00
(or EBCDIC, or hex) data in that conversation. Display filters in
2006-05-31 19:12:15 +00:00
B<Wireshark> are very powerful; more fields are filterable in B<Wireshark>
2000-08-09 06:38:53 +00:00
than in other protocol analyzers, and the syntax you can use to create
2006-05-31 19:12:15 +00:00
your filters is richer. As B<Wireshark> progresses, expect more and more
2000-08-09 06:38:53 +00:00
protocol fields to be allowed in display filters.
1999-08-03 16:33:12 +00:00
1999-12-16 08:05:46 +00:00
Packet capturing is performed with the pcap library. The capture filter
syntax follows the rules of the pcap library. This syntax is different
from the display filter syntax.
1998-09-16 02:39:15 +00:00
2008-02-15 22:36:24 +00:00
Compressed file support uses (and therefore requires) the zlib library.
2006-05-31 19:12:15 +00:00
If the zlib library is not present, B<Wireshark> will compile, but will
1999-12-16 08:05:46 +00:00
be unable to read compressed files.
1999-09-22 01:38:00 +00:00
2001-11-24 08:46:13 +00:00
The pathname of a capture file to be read can be specified with the
B<-r> option or can be specified as a command-line argument.
1998-09-16 02:39:15 +00:00
=head1 OPTIONS
2006-05-31 19:12:15 +00:00
Most users will want to start B<Wireshark> without options and configure
2011-09-23 04:33:07 +00:00
it from the menus instead. Those users may just skip this section.
2002-04-26 00:04:23 +00:00
2009-06-03 06:38:21 +00:00
=over 4
2019-11-10 22:33:52 +00:00
=item -a|--autostop E<lt>capture autostop conditionE<gt>
2001-12-04 07:32:05 +00:00
2006-05-31 19:12:15 +00:00
Specify a criterion that specifies when B<Wireshark> is to stop writing
2001-12-04 07:32:05 +00:00
to a capture file. The criterion is of the form I<test>B<:>I<value>,
where I<test> is one of:
2010-05-27 19:11:53 +00:00
B<duration>:I<value> Stop writing to a capture file after I<value> seconds have
2018-10-31 10:34:35 +00:00
elapsed. Floating point values (e.g. 0.5) are allowed.
2001-12-04 07:32:05 +00:00
2018-10-31 09:03:04 +00:00
B<files>:I<value> Stop writing to capture files after I<value> number of files
were written.
2010-05-27 19:11:53 +00:00
B<filesize>:I<value> Stop writing to a capture file after it reaches a size of
2013-12-02 19:17:12 +00:00
I<value> kB. If this option is used together with the -b option, Wireshark
2013-08-29 18:15:13 +00:00
will stop writing to the current capture file and switch to the next one if
filesize is reached. Note that the filesize is limited to a maximum value of
2 GiB.
2005-02-22 23:46:54 +00:00
2019-11-10 22:33:52 +00:00
B<packets>:I<value> Stop writing to a capture file after it contains I<value>
2018-10-31 09:03:04 +00:00
packets. Same as B<-c>E<lt>capture packet countE<gt>.
2001-12-04 07:32:05 +00:00
2019-11-10 22:33:52 +00:00
=item -b|--ring-buffer E<lt>capture ring buffer optionE<gt>
2001-12-04 09:56:10 +00:00
2008-02-15 22:36:24 +00:00
Cause B<Wireshark> to run in "multiple files" mode. In "multiple files" mode,
2011-09-23 04:33:07 +00:00
B<Wireshark> will write to several capture files. When the first capture file
2006-05-31 19:12:15 +00:00
fills up, B<Wireshark> will switch writing to the next file and so on.
2001-12-04 09:56:10 +00:00
2010-03-19 19:34:16 +00:00
The created filenames are based on the filename given with the B<-w> flag,
the number of the file and on the creation date and time,
2021-01-03 09:48:03 +00:00
e.g. outfile_00001_20210714120117.pcap, outfile_00002_20210714120523.pcap, ...
2001-12-04 09:56:10 +00:00
2008-02-15 22:36:24 +00:00
With the I<files> option it's also possible to form a "ring buffer".
This will fill up new files until the number of files specified,
at which point B<Wireshark> will discard the data in the first file and start
2011-09-23 04:33:07 +00:00
writing to that file and so on. If the I<files> option is not set,
2008-02-15 22:36:24 +00:00
new files filled up until one of the capture stop conditions match (or
2010-03-19 19:34:16 +00:00
until the disk is full).
2005-04-11 00:10:50 +00:00
The criterion is of the form I<key>B<:>I<value>,
where I<key> is one of:
2008-02-15 22:36:24 +00:00
B<duration>:I<value> switch to the next file after I<value> seconds have
2018-10-31 10:34:35 +00:00
elapsed, even if the current file is not completely filled up. Floating
point values (e.g. 0.5) are allowed.
2005-04-11 00:10:50 +00:00
2008-02-15 22:36:24 +00:00
B<files>:I<value> begin again with the first file after I<value> number of
2010-05-27 19:11:53 +00:00
files were written (form a ring buffer). This value must be less than 100000.
Caution should be used when using large numbers of files: some filesystems do
not handle many files in a single directory well. The B<files> criterion
2020-10-11 21:24:12 +00:00
requires one of the other criteria to be specified to
2017-06-27 20:04:33 +00:00
control when to go to the next file. It should be noted that each B<-b>
2020-10-11 21:24:12 +00:00
parameter takes exactly one criterion; to specify two criteria, each must be
2017-06-27 20:04:33 +00:00
preceded by the B<-b> option.
2010-05-27 19:11:53 +00:00
2018-10-31 09:03:04 +00:00
B<filesize>:I<value> switch to the next file after it reaches a size of
I<value> kB. Note that the filesize is limited to a maximum value of 2 GiB.
B<interval>:I<value> switch to the next file when the time is an exact
2019-11-10 22:33:52 +00:00
multiple of I<value> seconds.
2018-10-31 09:03:04 +00:00
B<packets>:I<value> switch to the next file after it contains I<value>
packets.
2013-12-02 19:17:12 +00:00
Example: B<-b filesize:1000 -b files:5> results in a ring buffer of five files
of size one megabyte each.
2003-05-15 13:40:20 +00:00
2019-11-10 22:33:52 +00:00
=item -B|--buffer-size E<lt>capture buffer sizeE<gt>
2010-05-27 19:13:26 +00:00
2013-12-02 19:17:12 +00:00
Set capture buffer size (in MiB, default is 2 MiB). This is used by
2010-05-27 19:13:26 +00:00
the capture driver to buffer packet data until that data can be written
to disk. If you encounter packet drops while capturing, try to increase
2012-10-01 07:14:03 +00:00
this size. Note that, while B<Wireshark> attempts to set the buffer size
2013-12-02 19:17:12 +00:00
to 2 MiB by default, and can be told to set it to a larger value, the
2010-05-27 19:13:26 +00:00
system or interface on which you're capturing might silently limit the
capture buffer size to a lower value or raise it to a higher value.
2010-11-27 16:51:24 +00:00
This is available on UNIX systems with libpcap 1.0.0 or later and on
2010-05-27 19:13:26 +00:00
Windows. It is not available on UNIX systems with earlier versions of
libpcap.
2005-05-30 04:46:25 +00:00
2011-09-23 04:33:07 +00:00
This option can occur multiple times. If used before the first
2011-06-28 22:02:43 +00:00
occurrence of the B<-i> option, it sets the default capture buffer size.
If used after an B<-i> option, it sets the capture buffer size for
the interface specified by the last B<-i> option occurring before
2011-09-23 04:33:07 +00:00
this option. If the capture buffer size is not set specifically,
2013-12-02 19:17:12 +00:00
the default capture buffer size is used instead.
2011-06-28 22:02:43 +00:00
2006-01-11 21:36:00 +00:00
=item -c E<lt>capture packet countE<gt>
1998-09-16 02:39:15 +00:00
2005-06-04 01:29:14 +00:00
Set the maximum number of packets to read when capturing live
2018-10-31 09:03:04 +00:00
data. Same as B<-a packets:>E<lt>capture packet countE<gt>.
1998-09-16 02:39:15 +00:00
2008-01-21 22:46:43 +00:00
=item -C E<lt>configuration profileE<gt>
Start with the given configuration profile.
2019-11-10 22:33:52 +00:00
=item --capture-comment E<lt>commentE<gt>
Set the capture file comment, if supported by the capture format.
2016-09-24 10:16:08 +00:00
=item -d E<lt>layer typeE<gt>==E<lt>selectorE<gt>,E<lt>decode-as protocolE<gt>
Like Wireshark's B<Decode As...> feature, this lets you specify how a
layer type should be dissected. If the layer type in question (for example,
B<tcp.port> or B<udp.port> for a TCP or UDP port number) has the specified
selector value, packets should be dissected as the specified protocol.
Example: B<-d tcp.port==8888,http> will decode any traffic running over
TCP port 8888 as HTTP.
See the tshark(1) manual page for more examples.
2019-11-10 22:33:52 +00:00
=item -D|--list-interfaces
2005-12-14 09:16:30 +00:00
2006-05-31 19:12:15 +00:00
Print a list of the interfaces on which B<Wireshark> can capture, and
2005-12-14 09:16:30 +00:00
exit. For each network interface, a number and an
interface name, possibly followed by a text description of the
interface, is printed. The interface name or the number can be supplied
to the B<-i> flag to specify an interface on which to capture.
2008-02-15 22:36:24 +00:00
This can be useful on systems that don't have a command to list them
2016-10-03 22:18:49 +00:00
(UNIX systems lacking B<ifconfig -a> or Linux systems lacking
B<ip link show>). The number can be useful on Windows systems, where
the interface name might be a long name or a GUID.
2005-12-14 09:16:30 +00:00
2006-05-31 19:12:15 +00:00
Note that "can capture" means that B<Wireshark> was able to open
2005-12-14 09:16:30 +00:00
that device to do a live capture; if, on your system, a program doing a
network capture must be run from an account with special privileges (for
2006-05-31 19:12:15 +00:00
example, as root), then, if B<Wireshark> is run with the B<-D> flag and
2005-12-14 09:16:30 +00:00
is not run from such an account, it will not list any interfaces.
2019-11-10 22:33:52 +00:00
=item --display E<lt>X display to useE<gt>
2006-08-13 00:13:22 +00:00
Specifies the X display to use. A hostname and screen (otherhost:0.0)
or just a screen (:0.0) can be specified. This option is not available
under Windows.
2019-11-10 22:33:52 +00:00
=item --disable-protocol E<lt>proto_nameE<gt>
Disable dissection of proto_name.
=item --disable-heuristic E<lt>short_nameE<gt>
Disable dissection of heuristic protocol.
=item --enable-protocol E<lt>proto_nameE<gt>
Enable dissection of proto_name.
=item --enable-heuristic E<lt>short_nameE<gt>
Enable dissection of heuristic protocol.
2006-01-11 21:36:00 +00:00
=item -f E<lt>capture filterE<gt>
1999-05-11 20:07:12 +00:00
2002-03-22 23:42:27 +00:00
Set the capture filter expression.
1999-05-11 20:07:12 +00:00
2011-09-23 04:33:07 +00:00
This option can occur multiple times. If used before the first
2011-06-28 22:02:43 +00:00
occurrence of the B<-i> option, it sets the default capture filter expression.
If used after an B<-i> option, it sets the capture filter expression for
the interface specified by the last B<-i> option occurring before
2011-09-23 04:33:07 +00:00
this option. If the capture filter expression is not set specifically,
2011-06-28 22:02:43 +00:00
the default capture filter expression is used if provided.
2014-12-20 22:13:05 +00:00
Pre-defined capture filter names, as shown in the GUI menu item Capture->Capture Filters,
can be used by prefixing the argument with "predef:".
Example: B<-f "predef:MyPredefinedHostOnlyFilter">
2016-10-19 18:53:40 +00:00
=item --fullscreen
Start Wireshark in full screen mode (kiosk mode). To exit from fullscreen mode,
open the View menu and select the Full Screen option. Alternatively, press the
F11 key (or Ctrl + Cmd + F for macOS).
2006-01-11 21:36:00 +00:00
=item -g E<lt>packet numberE<gt>
2005-05-31 21:30:40 +00:00
2005-06-04 01:29:14 +00:00
After reading in a capture file using the B<-r> flag, go to the given I<packet number>.
2005-05-31 21:30:40 +00:00
2019-11-10 22:33:52 +00:00
=item -h|--help
1998-09-17 02:01:50 +00:00
2019-11-10 22:33:52 +00:00
Print the version number and options and exit.
1998-09-17 02:01:50 +00:00
2006-06-01 20:40:22 +00:00
=item -H
Hide the capture info dialog during live packet capture.
2019-11-10 22:33:52 +00:00
=item -i|--interface E<lt>capture interfaceE<gt>|-
1998-09-16 02:39:15 +00:00
2002-12-29 22:40:10 +00:00
Set the name of the network interface or pipe to use for live packet
2008-02-15 22:36:24 +00:00
capture.
2002-12-29 22:40:10 +00:00
2002-11-03 17:38:27 +00:00
Network interface names should match one of the names listed in
2006-05-31 19:12:15 +00:00
"B<wireshark -D>" (described above); a number, as reported by
"B<wireshark -D>", can also be used. If you're using UNIX, "B<netstat
2018-12-05 15:43:45 +00:00
-i>", "B<ifconfig -a>" or "B<ip link>" might also work to list interface names,
2005-12-14 09:16:30 +00:00
although not all versions of UNIX support the B<-a> flag to B<ifconfig>.
2006-05-31 19:12:15 +00:00
If no interface is specified, B<Wireshark> searches the list of
2005-12-14 09:16:30 +00:00
interfaces, choosing the first non-loopback interface if there are any
non-loopback interfaces, and choosing the first loopback interface if
2011-09-23 04:33:07 +00:00
there are no non-loopback interfaces. If there are no interfaces at all,
2006-05-31 19:12:15 +00:00
B<Wireshark> reports an error and doesn't start the capture.
2002-12-29 22:40:10 +00:00
2018-11-16 23:24:52 +00:00
Pipe names should be either the name of a FIFO (named pipe) or "-" to
2011-09-23 04:33:07 +00:00
read data from the standard input. On Windows systems, pipe names must be
2018-11-16 23:24:52 +00:00
of the form "\\pipe\.\B<pipename>". Data read from pipes must be in
standard pcapng or pcap format. Pcapng data must have the same
endianness as the capturing host.
1998-09-16 02:39:15 +00:00
2018-11-16 23:24:52 +00:00
This option can occur multiple times. When capturing from multiple
2018-01-09 00:38:10 +00:00
interfaces, the capture file will be saved in pcapng format.
2011-06-28 22:02:43 +00:00
2019-11-10 22:33:52 +00:00
=item -I|--monitor-mode
2011-06-28 22:02:43 +00:00
Put the interface in "monitor mode"; this is supported only on IEEE
802.11 Wi-Fi interfaces, and supported only on some operating systems.
Note that in monitor mode the adapter might disassociate from the
network with which it's associated, so that you will not be able to use
any wireless networks with that adapter. This could prevent accessing
files on a network server, or resolving host names or network addresses,
if you are capturing in monitor mode and are not connected to another
network with another adapter.
2011-09-23 04:33:07 +00:00
This option can occur multiple times. If used before the first
2011-06-28 22:02:43 +00:00
occurrence of the B<-i> option, it enables the monitor mode for all interfaces.
If used after an B<-i> option, it enables the monitor mode for
the interface specified by the last B<-i> option occurring before
this option.
2012-03-15 15:15:18 +00:00
=item -j
Use after B<-J> to change the behavior when no exact match is found for
the filter. With this option select the first packet before.
2009-11-21 10:07:21 +00:00
=item -J E<lt>jump filterE<gt>
After reading in a capture file using the B<-r> flag, jump to the packet
2011-09-23 04:33:07 +00:00
matching the filter (display filter syntax). If no exact match is found
2009-11-21 10:07:21 +00:00
the first packet after that is selected.
1999-05-11 20:07:12 +00:00
=item -k
2002-03-22 23:42:27 +00:00
Start the capture session immediately. If the B<-i> flag was
2000-01-15 06:05:21 +00:00
specified, the capture uses the specified interface. Otherwise,
2006-05-31 19:12:15 +00:00
B<Wireshark> searches the list of interfaces, choosing the first
2000-01-16 02:48:12 +00:00
non-loopback interface if there are any non-loopback interfaces, and
choosing the first loopback interface if there are no non-loopback
2006-05-31 19:12:15 +00:00
interfaces; if there are no interfaces, B<Wireshark> reports an error and
2000-01-16 02:48:12 +00:00
doesn't start the capture.
1999-05-11 20:07:12 +00:00
2008-10-03 15:59:00 +00:00
=item -K E<lt>keytabE<gt>
Load kerberos crypto keys from the specified keytab file.
This option can be used multiple times to load keys from several files.
Example: B<-K krb5.keytab>
2001-05-01 00:41:46 +00:00
=item -l
2002-03-22 23:42:27 +00:00
Turn on automatic scrolling if the packet display is being updated
2001-05-01 00:41:46 +00:00
automatically as packets arrive during a capture (as specified by the
B<-S> flag).
2019-11-10 22:33:52 +00:00
=item -L|--list-data-link-types
2003-11-01 02:30:18 +00:00
List the data link types supported by the interface and exit.
2019-11-10 22:33:52 +00:00
=item --list-time-stamp-types
List time stamp types supported for the interface. If no time stamp type can be
set, no time stamp types are listed.
1998-09-17 02:01:50 +00:00
=item -n
2002-03-22 23:42:27 +00:00
Disable network object name resolution (such as hostname, TCP and UDP port
2005-06-04 01:29:14 +00:00
names), the B<-N> flag might override this one.
1998-09-17 02:01:50 +00:00
2006-01-11 21:36:00 +00:00
=item -N E<lt>name resolving flagsE<gt>
2001-05-31 08:36:46 +00:00
2005-06-04 01:29:14 +00:00
Turn on name resolving only for particular types of addresses and port
2002-03-22 23:42:27 +00:00
numbers, with name resolving for other types of addresses and port
2011-09-23 04:33:07 +00:00
numbers turned off. This flag overrides B<-n> if both B<-N> and B<-n> are
present. If both B<-N> and B<-n> flags are not present, all name resolutions
are turned on.
2005-06-04 01:29:14 +00:00
The argument is a string that may contain the letters:
B<m> to enable MAC address resolution
B<n> to enable network address resolution
2012-07-08 01:31:48 +00:00
B<N> to enable using external resolvers (e.g., DNS) for network address
resolution
2005-06-04 01:29:14 +00:00
B<t> to enable transport-layer port number resolution
2015-07-25 13:24:48 +00:00
B<d> to enable resolution from captured DNS packets
2018-10-05 06:54:55 +00:00
B<v> to enable VLAN IDs to names resolution
2006-01-11 21:36:00 +00:00
=item -o E<lt>preference/recent settingE<gt>
2000-07-09 04:09:09 +00:00
2008-02-15 22:36:24 +00:00
Set a preference or recent value, overriding the default value and any value
2011-09-23 04:33:07 +00:00
read from a preference/recent file. The argument to the flag is a string of
2005-05-30 04:06:22 +00:00
the form I<prefname>B<:>I<value>, where I<prefname> is the name of the
2008-02-15 22:36:24 +00:00
preference/recent value (which is the same name that would appear in the
preference/recent file), and I<value> is the value to which it should be set.
Since B<Ethereal> 0.10.12, the recent settings replaces the formerly used
2005-06-04 01:29:14 +00:00
-B, -P and -T flags to manipulate the GUI dimensions.
2000-07-09 04:09:09 +00:00
2008-02-15 22:36:24 +00:00
If I<prefname> is "uat", you can override settings in various user access
2011-09-23 04:33:07 +00:00
tables using the form uatB<:>I<uat filename>:I<uat record>. I<uat filename>
must be the name of a UAT file, e.g. I<user_dlts>. I<uat_record> must be in
the form of a valid record for that file, including quotes. For instance, to
2008-02-15 22:36:24 +00:00
specify a user DLT from the command line, you would use
2013-06-07 17:06:27 +00:00
-o "uat:user_dlts:\"User 0 (DLT=147)\",\"cops\",\"0\",\"\",\"0\",\"\""
2008-02-15 22:36:24 +00:00
2019-11-10 22:33:52 +00:00
=item -p|--no-promiscuous-mode
2000-09-15 05:32:49 +00:00
I<Don't> put the interface into promiscuous mode. Note that the
interface might be in promiscuous mode for some other reason; hence,
B<-p> cannot be used to ensure that the only traffic that is captured is
2006-05-31 19:12:15 +00:00
traffic sent to or from the machine on which B<Wireshark> is running,
2000-09-15 05:32:49 +00:00
broadcast traffic, and multicast traffic to addresses received by that
machine.
2011-09-23 04:33:07 +00:00
This option can occur multiple times. If used before the first
2011-06-28 22:02:43 +00:00
occurrence of the B<-i> option, no interface will be put into the
promiscuous mode.
If used after an B<-i> option, the interface specified by the last B<-i>
option occurring before this option will not be put into the
promiscuous mode.
2007-05-05 12:17:19 +00:00
=item -P E<lt>path settingE<gt>
2007-05-05 11:33:32 +00:00
2011-09-23 04:33:07 +00:00
Special path settings usually detected automatically. This is used for
2007-05-05 11:33:32 +00:00
special cases, e.g. starting Wireshark from a known location on an USB stick.
2007-05-05 12:17:19 +00:00
The criterion is of the form I<key>B<:>I<path>, where I<key> is one of:
2007-05-05 11:33:32 +00:00
2008-02-15 22:36:24 +00:00
B<persconf>:I<path> path of personal configuration files, like the
2007-05-05 11:33:32 +00:00
preferences files.
2008-02-15 22:36:24 +00:00
B<persdata>:I<path> path of personal data files, it's the folder initially
2011-09-23 04:33:07 +00:00
opened. After the very first initialization, the recent file will keep the
2007-05-05 11:33:32 +00:00
folder last used.
2019-11-10 22:33:52 +00:00
=item -r|--read-file E<lt>infileE<gt>
1998-09-16 02:39:15 +00:00
2008-02-15 22:36:24 +00:00
Read packet data from I<infile>, can be any supported capture file format
2011-09-23 04:33:07 +00:00
(including gzipped files). It's not possible to use named pipes or stdin
2012-05-07 19:53:49 +00:00
here! To capture from a pipe or from stdin use B<-i ->
1998-09-16 02:39:15 +00:00
2019-11-10 22:33:52 +00:00
=item -R|--read-filter E<lt>read (display) filterE<gt>
1999-08-08 01:29:24 +00:00
2000-02-19 00:18:45 +00:00
When reading a capture file specified with the B<-r> flag, causes the
specified filter (which uses the syntax of display filters, rather than
that of capture filters) to be applied to all packets read from the
capture file; packets not matching the filter are discarded.
1999-08-08 01:29:24 +00:00
2019-11-10 22:33:52 +00:00
=item -s|--snapshot-length E<lt>capture snaplenE<gt>
1998-09-16 02:39:15 +00:00
2009-10-20 20:14:23 +00:00
Set the default snapshot length to use when capturing live data.
1999-07-20 03:54:53 +00:00
No more than I<snaplen> bytes of each network packet will be read into
2009-02-23 19:00:30 +00:00
memory, or saved to disk. A value of 0 specifies a snapshot length of
2017-03-27 12:55:05 +00:00
262144, so that the full packet is captured; this is the default.
1998-09-16 02:39:15 +00:00
2011-09-23 04:33:07 +00:00
This option can occur multiple times. If used before the first
2011-06-28 22:02:43 +00:00
occurrence of the B<-i> option, it sets the default snapshot length.
If used after an B<-i> option, it sets the snapshot length for
the interface specified by the last B<-i> option occurring before
2011-09-23 04:33:07 +00:00
this option. If the snapshot length is not set specifically,
2011-06-28 22:02:43 +00:00
the default snapshot length is used if provided.
2012-03-15 15:15:18 +00:00
=item -S
Automatically update the packet display as packets are coming in.
2013-11-06 20:39:09 +00:00
=item -t a|ad|adoy|d|dd|e|r|u|ud|udoy
1998-09-27 22:12:47 +00:00
2002-03-22 23:42:27 +00:00
Set the format of the packet timestamp displayed in the packet list
2011-09-23 04:33:07 +00:00
window. The format can be one of:
2005-06-04 01:29:14 +00:00
2013-11-06 20:39:09 +00:00
B<a> absolute: The absolute time, as local time in your time zone,
is the actual time the packet was captured, with no date displayed
2005-06-04 01:29:14 +00:00
2013-11-06 20:39:09 +00:00
B<ad> absolute with date: The absolute date, displayed as YYYY-MM-DD,
and time, as local time in your time zone, is the actual time and date
the packet was captured
B<adoy> absolute with date using day of year: The absolute date,
displayed as YYYY/DOY, and time, as local time in your time zone,
is the actual time and date the packet was captured
2005-06-04 01:29:14 +00:00
B<d> delta: The delta time is the time since the previous packet was
captured
1998-09-27 22:12:47 +00:00
2008-02-15 22:36:24 +00:00
B<dd> delta_displayed: The delta_displayed time is the time since the
2007-03-23 18:08:17 +00:00
previous displayed packet was captured
2006-12-05 03:19:51 +00:00
B<e> epoch: The time in seconds since epoch (Jan 1, 1970 00:00:00)
2013-07-08 16:25:13 +00:00
B<r> relative: The relative time is the time elapsed between the first packet
and the current packet
2013-11-06 20:39:09 +00:00
B<u> UTC: The absolute time, as UTC, is the actual time the packet was
captured, with no date displayed
B<ud> UTC with date: The absolute date, displayed as YYYY-MM-DD,
and time, as UTC, is the actual time and date the packet was captured
2013-07-08 16:25:13 +00:00
2013-11-06 20:39:09 +00:00
B<udoy> UTC with date using day of year: The absolute date, displayed
as YYYY/DOY, and time, as UTC, is the actual time and date the packet
was captured
2013-07-08 16:25:13 +00:00
2009-10-20 20:14:23 +00:00
The default format is relative.
2009-07-13 23:35:26 +00:00
2019-11-10 22:33:52 +00:00
=item --time-stamp-type E<lt>typeE<gt>
Change the interface's timestamp method. See --list-time-stamp-types.
1998-09-16 02:39:15 +00:00
2019-11-10 22:33:52 +00:00
=item -u E<lt>s|hmsE<gt>
Output format of seconds (def: s: seconds)
=item -v|--version
Print the full version information and exit.
1998-09-16 02:39:15 +00:00
2006-01-11 21:36:00 +00:00
=item -w E<lt>outfileE<gt>
1998-09-16 02:39:15 +00:00
2019-11-10 22:33:52 +00:00
Set the default capture file name, or '-' for standard output.
1998-09-16 02:39:15 +00:00
2012-03-15 15:15:18 +00:00
=item -X E<lt>eXtension optionsE<gt>
Specify an option to be passed to an B<Wireshark> module. The eXtension option
is in the form I<extension_key>B<:>I<value>, where I<extension_key> can be:
B<lua_script>:I<lua_script_filename> tells B<Wireshark> to load the given script in addition to the
default Lua scripts.
2014-02-09 19:27:51 +00:00
B<lua_script>I<num>:I<argument> tells B<Wireshark> to pass the given argument
to the lua script identified by 'num', which is the number indexed order of the 'lua_script' command.
For example, if only one script was loaded with '-X lua_script:my.lua', then '-X lua_script1:foo'
will pass the string 'foo' to the 'my.lua' script. If two scripts were loaded, such as '-X lua_script:my.lua'
and '-X lua_script:other.lua' in that order, then a '-X lua_script2:bar' would pass the string 'bar' to the second lua
script, namely 'other.lua'.
2014-03-19 16:57:13 +00:00
B<read_format>:I<file_format> tells B<Wireshark> to use the given file format to read in the
file (the file given in the B<-r> command option).
2012-03-15 15:15:18 +00:00
B<stdin_descr>:I<description> tells B<Wireshark> to use the given description when
capturing from standard input (B<-i ->).
2019-11-10 22:33:52 +00:00
=item -y|--linktype E<lt>capture link typeE<gt>
2003-11-01 02:30:18 +00:00
If a capture is started from the command line with B<-k>, set the data
link type to use while capturing packets. The values reported by B<-L>
are the values that can be used.
2011-09-23 04:33:07 +00:00
This option can occur multiple times. If used before the first
2011-06-28 22:02:43 +00:00
occurrence of the B<-i> option, it sets the default capture link type.
If used after an B<-i> option, it sets the capture link type for
the interface specified by the last B<-i> option occurring before
2011-09-23 04:33:07 +00:00
this option. If the capture link type is not set specifically,
2011-06-28 22:02:43 +00:00
the default capture link type is used if provided.
2019-11-10 22:33:52 +00:00
=item -Y|--display-filter E<lt>displaY filterE<gt>
2013-03-30 12:15:42 +00:00
Start with the given display filter.
2006-01-11 21:36:00 +00:00
=item -z E<lt>statisticsE<gt>
2002-09-05 06:46:38 +00:00
2006-05-31 19:12:15 +00:00
Get B<Wireshark> to collect various types of statistics and display the result
2002-09-05 06:46:38 +00:00
in a window that updates in semi-real time.
2009-07-13 14:54:47 +00:00
2002-09-05 06:46:38 +00:00
Currently implemented statistics are:
2009-07-13 14:54:47 +00:00
=over 4
2015-06-05 20:17:13 +00:00
=item B<-z help>
Display all possible values for B<-z>.
=item B<-z> afp,srt[,I<filter>]
Show Apple Filing Protocol service response time statistics.
2012-03-15 15:15:18 +00:00
=item B<-z> conv,I<type>[,I<filter>]
Create a table that lists all conversations that could be seen in the
capture. I<type> specifies the conversation endpoint types for which we
want to generate the statistics; currently the supported ones are:
"eth" Ethernet addresses
"fc" Fibre Channel addresses
"fddi" FDDI addresses
"ip" IPv4 addresses
"ipv6" IPv6 addresses
"ipx" IPX addresses
"tcp" TCP/IP socket pairs Both IPv4 and IPv6 are supported
"tr" Token Ring addresses
"udp" UDP/IP socket pairs Both IPv4 and IPv6 are supported
If the optional I<filter> is specified, only those packets that match the
filter will be used in the calculations.
The table is presented with one line for each conversation and displays
the number of packets/bytes in each direction as well as the total
number of packets/bytes. By default, the table is sorted according to
the total number of packets.
These tables can also be generated at runtime by selecting the appropriate
conversation type from the menu "Tools/Statistics/Conversation List/".
Add DCE-RPC and ONC-RPC service response time dialogs.
Add RpcServiceResponseTimeDialog, which handles DCE-RPC and ONC-RPC
service response time statistics. Try to make it as lightweight as
possible, since we might want to pull this into the RPC dissectors
similar to the other SRT statistics.
Allow program names on the command line in place of numbers or UUIDs. Make
matches case-insensitive. E.g. the following are equivalent:
-z rpc,srt,100003,3
-z rpc,srt,nfs,3
-z rpc,srt,NFS,3
as are the following:
-z dcerpc,srt,f5cc5a18-4264-101a-8c59-08002b2f8426,56
-z dcerpc,srt,nspi,56
-z dcerpc,srt,NSPI,56
Change-Id: Ie451c64bf6fbc776f27d81e3bc248435c5cbc9e4
Reviewed-on: https://code.wireshark.org/review/9981
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
2015-08-11 18:48:07 +00:00
=item B<-z> dcerpc,srt,I<name-or-uuid>,I<major>.I<minor>[,I<filter>]
2002-10-25 01:08:49 +00:00
Add DCE-RPC and ONC-RPC service response time dialogs.
Add RpcServiceResponseTimeDialog, which handles DCE-RPC and ONC-RPC
service response time statistics. Try to make it as lightweight as
possible, since we might want to pull this into the RPC dissectors
similar to the other SRT statistics.
Allow program names on the command line in place of numbers or UUIDs. Make
matches case-insensitive. E.g. the following are equivalent:
-z rpc,srt,100003,3
-z rpc,srt,nfs,3
-z rpc,srt,NFS,3
as are the following:
-z dcerpc,srt,f5cc5a18-4264-101a-8c59-08002b2f8426,56
-z dcerpc,srt,nspi,56
-z dcerpc,srt,NSPI,56
Change-Id: Ie451c64bf6fbc776f27d81e3bc248435c5cbc9e4
Reviewed-on: https://code.wireshark.org/review/9981
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
2015-08-11 18:48:07 +00:00
Collect call/reply SRT (Service Response Time) data for DCERPC interface
I<name> or I<uuid>, version I<major>.I<minor>.
2009-07-13 14:54:47 +00:00
Data collected is the number of calls for each procedure, MinSRT, MaxSRT
2008-02-15 22:36:24 +00:00
and AvgSRT.
Add DCE-RPC and ONC-RPC service response time dialogs.
Add RpcServiceResponseTimeDialog, which handles DCE-RPC and ONC-RPC
service response time statistics. Try to make it as lightweight as
possible, since we might want to pull this into the RPC dissectors
similar to the other SRT statistics.
Allow program names on the command line in place of numbers or UUIDs. Make
matches case-insensitive. E.g. the following are equivalent:
-z rpc,srt,100003,3
-z rpc,srt,nfs,3
-z rpc,srt,NFS,3
as are the following:
-z dcerpc,srt,f5cc5a18-4264-101a-8c59-08002b2f8426,56
-z dcerpc,srt,nspi,56
-z dcerpc,srt,NSPI,56
Change-Id: Ie451c64bf6fbc776f27d81e3bc248435c5cbc9e4
Reviewed-on: https://code.wireshark.org/review/9981
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
2015-08-11 18:48:07 +00:00
Interface I<name> and I<uuid> are case-insensitive.
2009-07-13 14:54:47 +00:00
Example: S<B<-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0>> will collect data for the CIFS SAMR Interface.
2008-02-15 22:36:24 +00:00
This option can be used multiple times on the command line.
2002-10-25 01:08:49 +00:00
2009-07-13 14:54:47 +00:00
If the optional I<filter> is provided, the stats will only be calculated
2002-10-25 01:08:49 +00:00
on those calls that match that filter.
2009-07-13 14:54:47 +00:00
Example: S<B<-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0,ip.addr==1.2.3.4>> will collect SAMR
2003-06-21 01:42:46 +00:00
SRT statistics for a specific host.
2002-10-25 01:08:49 +00:00
2015-06-05 20:17:13 +00:00
=item B<-z> bootp,stat[,I<filter>]
Show DHCP (BOOTP) statistics.
2015-08-21 16:45:48 +00:00
=item B<-z> expert
Show expert information.
2012-03-15 15:15:18 +00:00
=item B<-z> fc,srt[,I<filter>]
2002-11-15 10:55:19 +00:00
2012-03-15 15:15:18 +00:00
Collect call/reply SRT (Service Response Time) data for FC. Data collected
is the number of calls for each Fibre Channel command, MinSRT, MaxSRT and AvgSRT.
2002-09-05 06:46:38 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z fc,srt>
will calculate the Service Response Time as the time delta between the
First packet of the exchange and the Last packet of the exchange.
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
The data will be presented as separate tables for all normal FC commands,
Only those commands that are seen in the capture will have its stats
displayed.
2009-07-13 14:54:47 +00:00
This option can be used multiple times on the command line.
2002-09-05 06:46:38 +00:00
2009-07-13 14:54:47 +00:00
If the optional I<filter> is provided, the stats will only be calculated
2002-09-27 11:07:16 +00:00
on those calls that match that filter.
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z "fc,srt,fc.id==01.02.03"> will collect stats only for
FC packets exchanged by the host at FC address 01.02.03 .
2006-04-24 23:09:34 +00:00
2012-03-15 15:15:18 +00:00
=item B<-z> h225,counter[I<,filter>]
2006-04-24 23:09:34 +00:00
2012-03-15 15:15:18 +00:00
Count ITU-T H.225 messages and their reasons. In the first column you get a
list of H.225 messages and H.225 message reasons which occur in the current
capture file. The number of occurrences of each message or reason is displayed
in the second column.
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z h225,counter>
2006-04-24 23:09:34 +00:00
2009-07-13 14:54:47 +00:00
This option can be used multiple times on the command line.
If the optional I<filter> is provided, the stats will only be calculated
2006-04-24 23:09:34 +00:00
on those calls that match that filter.
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z "h225,counter,ip.addr==1.2.3.4"> will collect stats only for
H.225 packets exchanged by the host at IP address 1.2.3.4 .
2003-01-22 00:40:36 +00:00
2012-03-15 15:15:18 +00:00
=item B<-z> h225,srt[I<,filter>]
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
Collect request/response SRT (Service Response Time) data for ITU-T H.225 RAS.
Data collected is the number of calls of each ITU-T H.225 RAS Message Type,
Minimum SRT, Maximum SRT, Average SRT, Minimum in Packet, and Maximum in Packet.
You will also get the number of Open Requests (Unresponded Requests),
Discarded Responses (Responses without matching request) and Duplicate Messages.
2003-01-22 00:40:36 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z h225,srt>
2003-01-22 00:40:36 +00:00
2008-02-15 22:36:24 +00:00
This option can be used multiple times on the command line.
2003-01-22 00:40:36 +00:00
2009-07-13 14:54:47 +00:00
If the optional I<filter> is provided, the stats will only be calculated
2003-01-22 00:40:36 +00:00
on those calls that match that filter.
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z "h225,srt,ip.addr==1.2.3.4"> will collect stats only for
ITU-T H.225 RAS packets exchanged by the host at IP address 1.2.3.4 .
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
=item B<-z> io,stat
2003-06-25 11:15:34 +00:00
2012-03-15 15:15:18 +00:00
Collect packet/bytes statistics for the capture in intervals of 1 second.
This option will open a window with up to 5 color-coded graphs where
number-of-packets-per-second or number-of-bytes-per-second statistics
can be calculated and displayed.
2003-06-25 11:15:34 +00:00
2008-02-15 22:36:24 +00:00
This option can be used multiple times on the command line.
2003-06-25 11:15:34 +00:00
2012-03-15 15:15:18 +00:00
This graph window can also be opened from the Analyze:Statistics:Traffic:IO-Stat
menu item.
2009-07-13 14:54:47 +00:00
=item B<-z> ldap,srt[,I<filter>]
2003-11-05 09:04:17 +00:00
Collect call/reply SRT (Service Response Time) data for LDAP. Data collected
2009-07-13 14:54:47 +00:00
is the number of calls for each implemented LDAP command, MinSRT, MaxSRT and AvgSRT.
Example: B<-z ldap,srt>
will calculate the Service Response Time as the time delta between the
2003-11-05 09:04:17 +00:00
Request and the Response.
The data will be presented as separate tables for all implemented LDAP commands,
Only those commands that are seen in the capture will have its stats
displayed.
2008-02-15 22:36:24 +00:00
This option can be used multiple times on the command line.
2003-11-05 09:04:17 +00:00
2009-07-13 14:54:47 +00:00
If the optional I<filter> is provided, the stats will only be calculated
2003-11-05 09:04:17 +00:00
on those calls that match that filter.
2009-07-13 14:54:47 +00:00
Example: use B<-z "ldap,srt,ip.addr==10.1.1.1"> will collect stats only for
2010-11-09 03:30:55 +00:00
LDAP packets exchanged by the host at IP address 10.1.1.1 .
2003-11-05 09:04:17 +00:00
2009-07-13 14:54:47 +00:00
The only LDAP commands that are currently implemented and for which the stats will be available are:
2003-11-05 09:04:17 +00:00
BIND
SEARCH
MODIFY
ADD
DELETE
MODRDN
COMPARE
EXTENDED
2009-07-13 14:54:47 +00:00
=item B<-z> megaco,srt[I<,filter>]
2008-12-31 15:26:48 +00:00
2009-07-13 14:54:47 +00:00
Collect request/response SRT (Service Response Time) data for MEGACO.
2011-09-23 04:33:07 +00:00
(This is similar to B<-z smb,srt>). Data collected is the number of calls
2008-12-31 15:26:48 +00:00
for each known MEGACO Command, Minimum SRT, Maximum SRT and Average SRT.
2009-07-13 14:54:47 +00:00
Example: B<-z megaco,srt>
2008-12-31 15:26:48 +00:00
This option can be used multiple times on the command line.
2009-07-13 14:54:47 +00:00
If the optional I<filter> is provided, the stats will only be calculated
2008-12-31 15:26:48 +00:00
on those calls that match that filter.
2009-07-13 14:54:47 +00:00
Example: B<-z "megaco,srt,ip.addr==1.2.3.4"> will collect stats only for
2008-12-31 15:26:48 +00:00
MEGACO packets exchanged by the host at IP address 1.2.3.4 .
2012-03-15 15:15:18 +00:00
=item B<-z> mgcp,srt[I<,filter>]
2003-08-24 03:31:54 +00:00
2012-03-15 15:15:18 +00:00
Collect request/response SRT (Service Response Time) data for MGCP.
(This is similar to B<-z smb,srt>). Data collected is the number of calls
for each known MGCP Type, Minimum SRT, Maximum SRT and Average SRT.
2003-08-24 20:32:40 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z mgcp,srt>
2003-08-24 03:31:54 +00:00
2012-03-15 15:15:18 +00:00
This option can be used multiple times on the command line.
2003-08-24 03:31:54 +00:00
2012-03-15 15:15:18 +00:00
If the optional I<filter> is provided, the stats will only be calculated
on those calls that match that filter.
2003-08-24 03:31:54 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z "mgcp,srt,ip.addr==1.2.3.4"> will collect stats only for
MGCP packets exchanged by the host at IP address 1.2.3.4 .
2003-08-24 03:31:54 +00:00
2015-08-31 23:06:33 +00:00
=item B<-z> mtp3,msus[,<filter>]
Show MTP3 MSU statistics.
2015-08-12 21:09:35 +00:00
=item B<-z> multicast,stat[,<filter>]
Show UDP multicast stream statistics.
2012-03-15 15:15:18 +00:00
=item B<-z> rpc,programs
2003-10-28 00:31:17 +00:00
2012-03-15 15:15:18 +00:00
Collect call/reply SRT data for all known ONC-RPC programs/versions.
Data collected is the number of calls for each protocol/version, MinSRT,
MaxSRT and AvgSRT.
2003-10-28 00:31:17 +00:00
Add DCE-RPC and ONC-RPC service response time dialogs.
Add RpcServiceResponseTimeDialog, which handles DCE-RPC and ONC-RPC
service response time statistics. Try to make it as lightweight as
possible, since we might want to pull this into the RPC dissectors
similar to the other SRT statistics.
Allow program names on the command line in place of numbers or UUIDs. Make
matches case-insensitive. E.g. the following are equivalent:
-z rpc,srt,100003,3
-z rpc,srt,nfs,3
-z rpc,srt,NFS,3
as are the following:
-z dcerpc,srt,f5cc5a18-4264-101a-8c59-08002b2f8426,56
-z dcerpc,srt,nspi,56
-z dcerpc,srt,NSPI,56
Change-Id: Ie451c64bf6fbc776f27d81e3bc248435c5cbc9e4
Reviewed-on: https://code.wireshark.org/review/9981
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
2015-08-11 18:48:07 +00:00
=item B<-z> rpc,srt,I<name-or-number>,I<version>[,<filter>]
2012-03-15 15:15:18 +00:00
Add DCE-RPC and ONC-RPC service response time dialogs.
Add RpcServiceResponseTimeDialog, which handles DCE-RPC and ONC-RPC
service response time statistics. Try to make it as lightweight as
possible, since we might want to pull this into the RPC dissectors
similar to the other SRT statistics.
Allow program names on the command line in place of numbers or UUIDs. Make
matches case-insensitive. E.g. the following are equivalent:
-z rpc,srt,100003,3
-z rpc,srt,nfs,3
-z rpc,srt,NFS,3
as are the following:
-z dcerpc,srt,f5cc5a18-4264-101a-8c59-08002b2f8426,56
-z dcerpc,srt,nspi,56
-z dcerpc,srt,NSPI,56
Change-Id: Ie451c64bf6fbc776f27d81e3bc248435c5cbc9e4
Reviewed-on: https://code.wireshark.org/review/9981
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
2015-08-11 18:48:07 +00:00
Collect call/reply SRT (Service Response Time) data for program
I<name>/I<version> or I<number>/I<version>.
Data collected is the number of calls for each procedure, MinSRT, MaxSRT and
AvgSRT.
Program I<name> is case-insensitive.
2012-03-15 15:15:18 +00:00
Example: B<-z rpc,srt,100003,3> will collect data for NFS v3.
2003-10-28 00:31:17 +00:00
2008-02-15 22:36:24 +00:00
This option can be used multiple times on the command line.
2003-10-28 00:31:17 +00:00
2009-07-13 14:54:47 +00:00
If the optional I<filter> is provided, the stats will only be calculated
2003-10-28 00:31:17 +00:00
on those calls that match that filter.
Add DCE-RPC and ONC-RPC service response time dialogs.
Add RpcServiceResponseTimeDialog, which handles DCE-RPC and ONC-RPC
service response time statistics. Try to make it as lightweight as
possible, since we might want to pull this into the RPC dissectors
similar to the other SRT statistics.
Allow program names on the command line in place of numbers or UUIDs. Make
matches case-insensitive. E.g. the following are equivalent:
-z rpc,srt,100003,3
-z rpc,srt,nfs,3
-z rpc,srt,NFS,3
as are the following:
-z dcerpc,srt,f5cc5a18-4264-101a-8c59-08002b2f8426,56
-z dcerpc,srt,nspi,56
-z dcerpc,srt,NSPI,56
Change-Id: Ie451c64bf6fbc776f27d81e3bc248435c5cbc9e4
Reviewed-on: https://code.wireshark.org/review/9981
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Gerald Combs <gerald@wireshark.org>
2015-08-11 18:48:07 +00:00
Example: S<B<-z rpc,srt,nfs,3,nfs.fh.hash==0x12345678>> will collect NFS v3
2012-03-15 15:15:18 +00:00
SRT statistics for a specific file.
2003-11-16 23:11:20 +00:00
2012-03-15 15:15:18 +00:00
=item B<-z> scsi,srt,I<cmdset>[,<filter>]
2003-11-16 23:11:20 +00:00
2012-03-15 15:15:18 +00:00
Collect call/reply SRT (Service Response Time) data for SCSI commandset <cmdset>.
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
Commandsets are 0:SBC 1:SSC 5:MMC
Data collected
is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.
Example: B<-z scsi,srt,0> will collect data for SCSI BLOCK COMMANDS (SBC).
2003-11-16 23:11:20 +00:00
2008-02-15 22:36:24 +00:00
This option can be used multiple times on the command line.
2003-11-16 23:11:20 +00:00
2009-07-13 14:54:47 +00:00
If the optional I<filter> is provided, the stats will only be calculated
2003-11-16 23:11:20 +00:00
on those calls that match that filter.
2009-07-13 14:54:47 +00:00
2012-03-15 15:15:18 +00:00
Example: B<-z scsi,srt,0,ip.addr==1.2.3.4> will collect SCSI SBC
SRT statistics for a specific iscsi/ifcp/fcip host.
2003-11-16 23:11:20 +00:00
2009-07-13 14:54:47 +00:00
=item B<-z> sip,stat[I<,filter>]
2003-11-16 23:11:20 +00:00
2011-09-23 04:33:07 +00:00
This option will activate a counter for SIP messages. You will get the number
of occurrences of each SIP Method and of each SIP Status-Code. Additionally you
2008-02-15 22:36:24 +00:00
also get the number of resent SIP Messages (only for SIP over UDP).
2004-05-01 21:33:44 +00:00
2009-07-13 14:54:47 +00:00
Example: B<-z sip,stat>
2004-05-01 21:33:44 +00:00
2008-02-15 22:36:24 +00:00
This option can be used multiple times on the command line.
2004-05-01 21:33:44 +00:00
2009-07-13 14:54:47 +00:00
If the optional I<filter> is provided, the stats will only be calculated
2004-05-01 21:33:44 +00:00
on those calls that match that filter.
2009-07-13 14:54:47 +00:00
Example: B<-z "sip,stat,ip.addr==1.2.3.4"> will collect stats only for
2004-05-01 21:33:44 +00:00
SIP packets exchanged by the host at IP address 1.2.3.4 .
2003-11-16 23:11:20 +00:00
2012-03-15 15:15:18 +00:00
=item B<-z> smb,srt[,I<filter>]
Collect call/reply SRT (Service Response Time) data for SMB. Data collected
is the number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.
Example: B<-z smb,srt>
The data will be presented as separate tables for all normal SMB commands,
all Transaction2 commands and all NT Transaction commands.
Only those commands that are seen in the capture will have their stats
displayed.
Only the first command in a xAndX command chain will be used in the
calculation. So for common SessionSetupAndX + TreeConnectAndX chains,
only the SessionSetupAndX call will be used in the statistics.
This is a flaw that might be fixed in the future.
This option can be used multiple times on the command line.
If the optional I<filter> is provided, the stats will only be calculated
on those calls that match that filter.
Example: B<-z "smb,srt,ip.addr==1.2.3.4"> will collect stats only for
SMB packets exchanged by the host at IP address 1.2.3.4 .
2009-07-13 14:54:47 +00:00
=item B<-z> voip,calls
2007-06-19 18:09:50 +00:00
This option will show a window that shows VoIP calls found in the capture file.
This is the same window shown as when you go to the Statistics Menu and choose
VoIP Calls.
2009-07-13 14:54:47 +00:00
Example: B<-z voip,calls>
2015-08-21 16:45:48 +00:00
=item B<-z> wlan,stat[,<filter>]
Show IEEE 802.11 network and station statistics.
2015-08-31 23:06:33 +00:00
=item B<-z> wsp,stat[,<filter>]
Show WSP packet counters.
2017-04-17 03:47:34 +00:00
=back
2009-07-13 14:54:47 +00:00
=back
2007-06-19 18:09:50 +00:00
1998-09-16 02:39:15 +00:00
=head1 INTERFACE
=head2 MENU ITEMS
=over 4
2004-05-22 13:49:01 +00:00
=item File:Open
=item File:Open Recent
2009-07-13 14:54:47 +00:00
=item File:Merge
2011-09-23 04:33:07 +00:00
Merge another capture file to the currently loaded one. The I<File:Merge>
2009-07-13 14:54:47 +00:00
dialog box allows the merge "Prepended", "Chronologically" or "Appended",
relative to the already loaded one.
2004-05-22 13:49:01 +00:00
=item File:Close
1998-09-16 02:39:15 +00:00
2003-12-08 17:54:32 +00:00
Open or close a capture file. The I<File:Open> dialog box
1999-08-10 07:16:47 +00:00
allows a filter to be specified; when the capture file is read, the
filter is applied to all packets read from the file, and packets not
2011-09-23 04:33:07 +00:00
matching the filter are discarded. The I<File:Open Recent> is a submenu
2004-03-13 19:51:07 +00:00
and will show a list of previously opened files.
1998-09-16 02:39:15 +00:00
2004-05-22 13:49:01 +00:00
=item File:Save
=item File:Save As
Allow the user to save either all of the current capture, or only the
packets that are currently being displayed from that capture.
Centralize the code to control whether "File:Save" and "File:Save As"
are enabled (and *always* have "File:Save As" enabled if you have a
capture; "File:Save" is enabled only if you have a live capture you've
not yet saved, although it does the same thing as "File:Save As").
Have the "save_file" member of a "capture_file" structure represent
*only* the file currently being *written* to by a capture, and, if there
is no capture currently in progress, have it be NULL; the name of the
file currently being *displayed" is in the "filename" member, and an
"is_tempfile" member indicates whether it's a temporary file for a live
capture or not.
Have "close_cap_file()" delete the current capture file if it's a
temporary capture file that hasn't been saved (in its entirety - saving
selected frames doesn't count). Do the same (if there *is* a current
capture file) when exiting.
The "Ready to load or capture" message is the only statusbar message in
the "main" context; "close_cap_file()" should never pop it, it should
only pop whatever message exists in the "file" context, and thus has no
need to take, as an argument, the context for the message it should pop.
Update the man page to reflect the new behavior of "File:Save" and
"File:Save As", and to reflect recent changes to "Display:Match Selected".
svn path=/trunk/; revision=1170
1999-11-30 20:50:15 +00:00
Save the current capture, or the packets currently displayed from that
2000-08-23 19:40:12 +00:00
capture, to a file. Check boxes let you select whether to save all
packets, or just those that have passed the current display filter and/or
2008-02-15 22:36:24 +00:00
those that are currently marked, and an option menu lets you select (from
a list of file formats in which at particular capture, or the packets
currently displayed from that capture, can be saved), a file format in
2000-08-23 19:40:12 +00:00
which to save it.
Allow the user to save either all of the current capture, or only the
packets that are currently being displayed from that capture.
Centralize the code to control whether "File:Save" and "File:Save As"
are enabled (and *always* have "File:Save As" enabled if you have a
capture; "File:Save" is enabled only if you have a live capture you've
not yet saved, although it does the same thing as "File:Save As").
Have the "save_file" member of a "capture_file" structure represent
*only* the file currently being *written* to by a capture, and, if there
is no capture currently in progress, have it be NULL; the name of the
file currently being *displayed" is in the "filename" member, and an
"is_tempfile" member indicates whether it's a temporary file for a live
capture or not.
Have "close_cap_file()" delete the current capture file if it's a
temporary capture file that hasn't been saved (in its entirety - saving
selected frames doesn't count). Do the same (if there *is* a current
capture file) when exiting.
The "Ready to load or capture" message is the only statusbar message in
the "main" context; "close_cap_file()" should never pop it, it should
only pop whatever message exists in the "file" context, and thus has no
need to take, as an argument, the context for the message it should pop.
Update the man page to reflect the new behavior of "File:Save" and
"File:Save As", and to reflect recent changes to "Display:Match Selected".
svn path=/trunk/; revision=1170
1999-11-30 20:50:15 +00:00
2005-06-04 04:57:10 +00:00
=item File:File Set:List Files
2008-03-17 21:26:54 +00:00
Show a dialog box that lists all files of the file set matching the currently
2011-09-23 04:33:07 +00:00
loaded file. A file set is a compound of files resulting from a capture using
2008-02-15 22:36:24 +00:00
the "multiple files" / "ringbuffer" mode, recognizable by the filename pattern,
2021-01-03 09:48:03 +00:00
e.g.: Filename_00001_20210714101530.pcap.
2005-06-04 04:57:10 +00:00
=item File:File Set:Next File
=item File:File Set:Previous File
2008-02-15 22:36:24 +00:00
If the currently loaded file is part of a file set (see above), open the
2005-06-04 04:57:10 +00:00
next / previous file in that set.
2004-03-13 19:51:07 +00:00
=item File:Export
1999-07-23 08:33:44 +00:00
2011-09-23 04:33:07 +00:00
Export captured data into an external format. Note: the data cannot be
2006-05-31 19:12:15 +00:00
imported back into Wireshark, so be sure to keep the capture file.
1999-07-23 08:33:44 +00:00
2004-03-13 19:51:07 +00:00
=item File:Print
1998-09-16 02:39:15 +00:00
2011-09-23 04:33:07 +00:00
Print packet data from the current capture. You can select the range of
2008-02-15 22:36:24 +00:00
packets to be printed (which packets are printed), and the output format of
2011-09-23 04:33:07 +00:00
each packet (how each packet is printed). The output format will be similar
2008-02-15 22:36:24 +00:00
to the displayed values, so a summary line, the packet details view, and/or
the hex dump of the packet can be printed.
2004-05-22 12:32:00 +00:00
2008-02-15 22:36:24 +00:00
Printing options can be set with the I<Edit:Preferences> menu item, or in the
2004-05-22 12:32:00 +00:00
dialog box popped up by this menu item.
1998-09-16 02:39:15 +00:00
=item File:Quit
2002-03-22 23:42:27 +00:00
Exit the application.
1998-09-16 02:39:15 +00:00
2009-05-02 06:44:59 +00:00
=item Edit:Copy:Description
2009-04-08 18:32:11 +00:00
2009-10-20 20:14:23 +00:00
Copies the description of the selected field in the protocol tree to
2009-04-08 18:32:11 +00:00
the clipboard.
=item Edit:Copy:Fieldname
2009-10-20 20:14:23 +00:00
Copies the fieldname of the selected field in the protocol tree to
2009-04-08 18:32:11 +00:00
the clipboard.
=item Edit:Copy:Value
2009-10-20 20:14:23 +00:00
Copies the value of the selected field in the protocol tree to
2009-04-08 18:32:11 +00:00
the clipboard.
2007-03-08 23:37:55 +00:00
=item Edit:Copy:As Filter
Create a display filter based on the data currently highlighted in the
packet details and copy that filter to the clipboard.
If that data is a field that can be tested in a display filter
expression, the display filter will test that field; otherwise, the
display filter will be based on the absolute offset within the packet.
Therefore it could be unreliable if the packet contains protocols with
variable-length headers, such as a source-routed token-ring packet.
2003-12-08 17:54:32 +00:00
=item Edit:Find Packet
2000-01-18 09:05:30 +00:00
2002-03-22 23:42:27 +00:00
Search forward or backward, starting with the currently selected packet
2003-09-09 02:41:00 +00:00
(or the most recently selected packet, if no packet is selected). Search
2008-02-15 22:36:24 +00:00
criteria can be a display filter expression, a string of hexadecimal
2003-09-09 02:41:00 +00:00
digits, or a text string.
2003-09-10 22:33:31 +00:00
When searching for a text string, you can search the packet data, or you
can search the text in the Info column in the packet list pane or in the
2004-05-03 23:37:39 +00:00
packet details pane.
2003-09-10 22:33:31 +00:00
2003-09-09 02:41:00 +00:00
Hexadecimal digits can be separated by colons, periods, or dashes.
Text string searches can be ASCII or Unicode (or both), and may be
case insensitive.
2002-05-03 21:55:15 +00:00
=item Edit:Find Next
=item Edit:Find Previous
2008-02-15 22:36:24 +00:00
Search forward / backward for a packet matching the filter from the previous
search, starting with the currently selected packet (or the most recently
2004-05-22 13:49:01 +00:00
selected packet, if no packet is selected).
2000-01-18 09:05:30 +00:00
2009-07-13 14:54:47 +00:00
=item Edit:Mark Packet (toggle)
Mark (or unmark if currently marked) the selected packet. The field
"frame.marked" is set for packets that are marked, so that, for example,
a display filters can be used to display only marked packets, and so that
2013-06-07 17:06:27 +00:00
the L</"Edit:Find Packet"> dialog can be used to find the next or previous
2009-07-13 14:54:47 +00:00
marked packet.
=item Edit:Find Next Mark
=item Edit:Find Previous Mark
Find next/previous marked packet.
=item Edit:Mark All Packets
=item Edit:Unmark All Packets
Mark / Unmark all packets that are currently displayed.
2005-04-11 00:10:50 +00:00
=item Edit:Time Reference:Set Time Reference (toggle)
2003-09-12 02:48:23 +00:00
Set (or unset if currently set) the selected packet as a Time Reference packet.
When a packet is set as a Time Reference packet, the timestamps in the packet
2004-05-03 23:37:39 +00:00
list pane will be replaced with the string "*REF*".
2003-09-12 02:48:23 +00:00
The relative time timestamp in later packets will then be calculated relative
2008-02-15 22:36:24 +00:00
to the timestamp of this Time Reference packet and not the first packet in
2003-09-12 02:48:23 +00:00
the capture.
2004-05-03 23:37:39 +00:00
Packets that have been selected as Time Reference packets will always be
displayed in the packet list pane. Display filters will not affect or
hide these packets.
2003-09-12 02:48:23 +00:00
2009-05-02 06:44:59 +00:00
If there is a column displayed for "Cumulative Bytes" this counter will
2003-12-08 17:54:32 +00:00
be reset at every Time Reference packet.
2003-09-12 02:48:23 +00:00
2004-03-13 19:51:07 +00:00
=item Edit:Time Reference:Find Next
=item Edit:Time Reference:Find Previous
2004-05-22 13:49:01 +00:00
Search forward / backward for a time referenced packet.
2004-03-13 19:51:07 +00:00
2008-01-21 22:27:02 +00:00
=item Edit:Configuration Profiles
Manage configuration profiles to be able to use more than one set of
preferences and configurations.
1998-10-13 02:10:57 +00:00
=item Edit:Preferences
1998-09-16 02:39:15 +00:00
2005-04-11 00:10:50 +00:00
Set the GUI, capture, printing and protocol options
2013-06-07 17:06:27 +00:00
(see L</Preferences> dialog below).
1999-12-10 06:28:24 +00:00
2004-05-03 23:37:39 +00:00
=item View:Main Toolbar
2004-05-22 12:32:00 +00:00
2004-05-03 23:37:39 +00:00
=item View:Filter Toolbar
2004-05-22 12:32:00 +00:00
2004-05-03 23:48:00 +00:00
=item View:Statusbar
2004-05-03 23:37:39 +00:00
Show or hide the main window controls.
=item View:Packet List
2004-05-22 12:32:00 +00:00
2004-05-03 23:37:39 +00:00
=item View:Packet Details
2004-05-22 12:32:00 +00:00
2004-05-03 23:37:39 +00:00
=item View:Packet Bytes
Show or hide the main window panes.
2004-03-13 19:51:07 +00:00
2005-06-04 04:57:10 +00:00
=item View:Time Display Format
2005-04-11 00:10:50 +00:00
2005-06-04 04:57:10 +00:00
Set the format of the packet timestamp displayed in the packet list window.
2005-04-11 00:10:50 +00:00
2005-06-04 04:57:10 +00:00
=item View:Name Resolution:Resolve Name
1999-06-19 08:48:30 +00:00
2009-05-02 06:44:59 +00:00
Try to resolve a name for the currently selected item.
2004-03-13 19:51:07 +00:00
2005-06-04 04:57:10 +00:00
=item View:Name Resolution:Enable for ... Layer
2004-03-13 19:51:07 +00:00
Enable or disable translation of addresses to names in the display.
2005-06-04 04:57:10 +00:00
=item View:Colorize Packet List
2011-09-23 04:33:07 +00:00
Enable or disable the coloring rules. Disabling will improve performance.
2005-06-04 04:57:10 +00:00
2004-03-13 19:51:07 +00:00
=item View:Auto Scroll in Live Capture
Enable or disable the automatic scrolling of the
packet list while a live capture is in progress.
=item View:Zoom In
=item View:Zoom Out
2004-05-22 13:49:01 +00:00
Zoom into / out of the main window data (by changing the font size).
2004-03-13 19:51:07 +00:00
=item View:Normal Size
Reset the zoom factor of zoom in / zoom out back to normal font size.
1999-06-19 08:48:30 +00:00
2005-06-04 04:57:10 +00:00
=item View:Resize All Columns
2005-04-11 00:10:50 +00:00
2005-06-04 04:57:10 +00:00
Resize all columns to best fit the current packet display.
2005-04-11 00:10:50 +00:00
2013-10-23 14:24:17 +00:00
=item View:Expand / Collapse Subtrees
2002-01-11 09:02:15 +00:00
2013-10-23 14:24:17 +00:00
Expands / Collapses the currently selected item and it's subtrees in the packet details.
2002-01-11 09:02:15 +00:00
2005-06-04 04:57:10 +00:00
=item View:Expand All
1999-08-28 23:47:50 +00:00
2005-06-04 04:57:10 +00:00
=item View:Collapse All
2004-05-22 12:32:00 +00:00
2005-06-04 04:57:10 +00:00
Expand / Collapse all branches of the packet details.
2004-05-22 12:32:00 +00:00
2009-07-13 14:54:47 +00:00
=item View:Colorize Conversation
Select color for a conversation.
=item View:Reset Coloring 1-10
Reset Color for a conversation.
2004-05-22 13:49:01 +00:00
=item View:Coloring Rules
2004-05-22 12:32:00 +00:00
Change the foreground and background colors of the packet information in
the list of packets, based upon display filters. The list of display
filters is applied to each packet sequentially. After the first display
filter matches a packet, any additional display filters in the list are
ignored. Therefore, if you are filtering on the existence of protocols,
you should list the higher-level protocols first, and the lower-level
protocols last.
2003-08-27 22:55:51 +00:00
=over
=item How Colorization Works
2011-09-23 04:33:07 +00:00
Packets are colored according to a list of color filters. Each filter
consists of a name, a filter expression and a coloration. A packet is
colored according to the first filter that it matches. Color filter
2003-08-18 21:27:11 +00:00
expressions use exactly the same syntax as display filter expressions.
2004-09-05 15:06:26 +00:00
2006-05-31 19:12:15 +00:00
When Wireshark starts, the color filters are loaded from:
2004-09-05 15:06:26 +00:00
=over
2013-06-07 17:06:27 +00:00
=item 1.
The user's personal color filters file or, if that does not exist,
=item 2.
2004-09-05 15:06:26 +00:00
2013-06-07 17:06:27 +00:00
The global color filters file.
2004-09-05 15:06:26 +00:00
=back
2003-08-18 21:27:11 +00:00
If neither of these exist then the packets will not be colored.
2003-08-27 22:55:51 +00:00
=back
2003-08-18 21:27:11 +00:00
2003-12-08 17:54:32 +00:00
=item View:Show Packet In New Window
1999-09-11 15:47:38 +00:00
2004-05-03 23:37:39 +00:00
Create a new window containing a packet details view and a hex dump
2003-12-08 17:54:32 +00:00
window of the currently selected packet; this window will continue to
2004-05-03 23:37:39 +00:00
display that packet's details and data even if another packet is
2003-12-08 17:54:32 +00:00
selected.
1999-09-11 15:47:38 +00:00
2003-12-08 17:54:32 +00:00
=item View:Reload
1999-09-11 15:47:38 +00:00
2008-02-15 22:36:24 +00:00
Reload a capture file. Same as I<File:Close> and I<File:Open> the same
2003-12-08 17:54:32 +00:00
file again.
1999-09-11 15:47:38 +00:00
2005-04-11 00:10:50 +00:00
=item Go:Back
Go back in previously visited packets history.
=item Go:Forward
Go forward in previously visited packets history.
2004-03-13 19:51:07 +00:00
=item Go:Go To Packet
Go to a particular numbered packet.
=item Go:Go To Corresponding Packet
2004-05-03 23:37:39 +00:00
If a field in the packet details pane containing a packet number is
2004-03-13 19:51:07 +00:00
selected, go to the packet number specified by that field. (This works
2004-05-03 23:37:39 +00:00
only if the dissector that put that entry into the packet details put it
into the details as a filterable field rather than just as text.) This
can be used, for example, to go to the packet for the request
corresponding to a reply, or the reply corresponding to a request, if
that packet number has been put into the packet details.
2004-03-13 19:51:07 +00:00
2009-07-13 14:54:47 +00:00
=item Go:Previous Packet
=item Go:Next Packet
2004-03-13 19:51:07 +00:00
=item Go:First Packet
=item Go:Last Packet
2009-07-13 14:54:47 +00:00
Go to the previous / next / first / last packet in the capture.
2004-03-13 19:51:07 +00:00
2010-12-07 11:59:15 +00:00
=item Go:Previous Packet In Conversation
=item Go:Next Packet In Conversation
2011-09-23 04:17:16 +00:00
Go to the previous / next packet of the conversation (TCP, UDP or IP)
2010-12-07 11:59:15 +00:00
2005-06-04 04:57:10 +00:00
=item Capture:Interfaces
Shows a dialog box with all currently known interfaces and displaying the
2011-09-23 04:33:07 +00:00
current network traffic amount. Capture sessions can be started from here.
2005-06-04 04:57:10 +00:00
Beware: keeping this box open results in high system load!
=item Capture:Options
2013-06-07 17:06:27 +00:00
Initiate a live packet capture (see L</"Capture Options Dialog">
below). If no filename is specified, a temporary file will be created
2011-09-23 04:33:07 +00:00
to hold the capture. The location of the file can be chosen by setting your
TMPDIR environment variable before starting B<Wireshark>. Otherwise, the
2008-02-15 22:36:24 +00:00
default TMPDIR location is system-dependent, but is likely either F</var/tmp>
2005-06-04 04:57:10 +00:00
or F</tmp>.
2003-12-08 17:54:32 +00:00
=item Capture:Start
2000-02-29 06:24:41 +00:00
2011-09-23 04:33:07 +00:00
Start a live packet capture with the previously selected options. This won't
2010-11-09 03:30:55 +00:00
open the options dialog box, and can be convenient for repeatedly capturing
2005-06-04 04:57:10 +00:00
with the same options.
2000-02-29 06:24:41 +00:00
2003-12-08 17:54:32 +00:00
=item Capture:Stop
2000-02-29 06:24:41 +00:00
2005-06-04 04:57:10 +00:00
Stop a running live capture.
2000-02-29 06:24:41 +00:00
2005-06-04 04:57:10 +00:00
=item Capture:Restart
2005-04-11 00:10:50 +00:00
2008-02-15 22:36:24 +00:00
While a live capture is running, stop it and restart with the same options
2011-09-23 04:33:07 +00:00
again. This can be convenient to remove irrelevant packets, if no valuable
2005-06-04 04:57:10 +00:00
packets were captured so far.
2005-04-11 00:10:50 +00:00
2003-12-08 17:54:32 +00:00
=item Capture:Capture Filters
Edit the saved list of capture filters, allowing filters to be added,
changed, or deleted.
=item Analyze:Display Filters
Edit the saved list of display filters, allowing filters to be added,
changed, or deleted.
2009-07-13 14:54:47 +00:00
=item Analyze:Display Filter Macros
Create shortcuts for complex macros
2004-05-22 12:32:00 +00:00
=item Analyze:Apply as Filter
2003-12-08 17:54:32 +00:00
2007-03-08 23:37:55 +00:00
Create a display filter based on the data currently highlighted in the
packet details and apply the filter.
2003-12-08 17:54:32 +00:00
If that data is a field that can be tested in a display filter
expression, the display filter will test that field; otherwise, the
2007-03-08 23:37:55 +00:00
display filter will be based on the absolute offset within the packet.
Therefore it could be unreliable if the packet contains protocols with
2003-12-08 17:54:32 +00:00
variable-length headers, such as a source-routed token-ring packet.
The B<Selected> option creates a display filter that tests for a match
of the data; the B<Not Selected> option creates a display filter that
tests for a non-match of the data. The B<And Selected>, B<Or Selected>,
B<And Not Selected>, and B<Or Not Selected> options add to the end of
2007-03-08 23:37:55 +00:00
the display filter in the strip at the top (or bottom) an AND or OR
operator followed by the new display filter expression.
2003-12-08 17:54:32 +00:00
2020-10-07 18:11:02 +00:00
=item Analyze:Prepare as Filter
2003-12-08 17:54:32 +00:00
2007-03-08 23:37:55 +00:00
Create a display filter based on the data currently highlighted in the
2011-09-23 04:33:07 +00:00
packet details. The filter strip at the top (or bottom) is updated but
2007-03-08 23:37:55 +00:00
it is not yet applied.
2003-12-08 17:54:32 +00:00
=item Analyze:Enabled Protocols
Allow protocol dissection to be enabled or disabled for a specific
protocol. Individual protocols can be enabled or disabled by clicking
on them in the list or by highlighting them and pressing the space bar.
The entire list can be enabled, disabled, or inverted using the buttons
below the list.
When a protocol is disabled, dissection in a particular packet stops
2006-05-31 19:12:15 +00:00
when that protocol is reached, and Wireshark moves on to the next packet.
2003-12-08 17:54:32 +00:00
Any higher-layer protocols that would otherwise have been processed will
not be displayed. For example, disabling TCP will prevent the dissection
and display of TCP, HTTP, SMTP, Telnet, and any other protocol exclusively
dependent on TCP.
2006-05-31 19:12:15 +00:00
The list of protocols can be saved, so that Wireshark will start up with
2003-12-08 17:54:32 +00:00
the protocols in that list disabled.
=item Analyze:Decode As
If you have a packet selected, present a dialog allowing you to change
which dissectors are used to decode this packet. The dialog has one
panel each for the link layer, network layer and transport layer
protocol/port numbers, and will allow each of these to be changed
independently. For example, if the selected packet is a TCP packet to
2006-05-31 19:12:15 +00:00
port 12345, using this dialog you can instruct Wireshark to decode all
2003-12-08 17:54:32 +00:00
packets to or from that TCP port as HTTP packets.
=item Analyze:User Specified Decodes
2001-02-14 07:15:39 +00:00
2002-03-22 23:42:27 +00:00
Create a new window showing whether any protocol ID to dissector
2001-02-14 07:15:39 +00:00
mappings have been changed by the user. This window also allows the
user to reset all decodes to their default values.
2003-12-08 17:54:32 +00:00
=item Analyze:Follow TCP Stream
1998-09-16 02:39:15 +00:00
2002-03-22 23:42:27 +00:00
If you have a TCP packet selected, display the contents of the data
stream for the TCP connection to which that packet belongs, as text, in
a separate window, and leave the list of packets in a filtered state,
with only those packets that are part of that TCP connection being
displayed. You can revert to your old view by pressing ENTER in the
display filter text box, thereby invoking your old display filter (or
resetting it back to no display filter).
1999-10-30 06:42:10 +00:00
2003-03-10 04:27:01 +00:00
The window in which the data stream is displayed lets you select:
2000-08-09 06:38:53 +00:00
2003-03-10 04:27:01 +00:00
=over 8
2000-08-09 06:38:53 +00:00
2003-03-10 04:27:01 +00:00
=item *
2000-08-09 06:38:53 +00:00
whether to display the entire conversation, or one or the other side of
it;
2003-03-10 04:27:01 +00:00
=item *
2000-08-09 06:38:53 +00:00
whether the data being displayed is to be treated as ASCII or EBCDIC
text or as raw hex data;
2009-06-03 06:38:21 +00:00
=back
2000-08-09 06:38:53 +00:00
and lets you print what's currently being displayed, using the same
print options that are used for the I<File:Print Packet> menu item, or
save it as text to a file.
1998-09-16 02:39:15 +00:00
2009-07-13 14:54:47 +00:00
=item Analyze:Follow UDP Stream
2018-09-13 15:40:27 +00:00
=item Analyze:Follow TLS Stream
2009-07-13 14:54:47 +00:00
(Similar to Analyze:Follow TCP Stream)
=item Analyze:Expert Info
=item Analyze:Expert Info Composite
(Kind of) a log of anomalies found by Wireshark in a capture file.
=item Analyze:Conversation Filter
2004-03-13 19:51:07 +00:00
=item Statistics:Summary
2003-09-02 22:10:32 +00:00
Show summary information about the capture, including elapsed time,
packet counts, byte counts, and the like. If a display filter is in
effect, summary information will be shown about the capture and about
the packets currently being displayed.
2004-03-13 19:51:07 +00:00
=item Statistics:Protocol Hierarchy
2001-03-22 23:54:47 +00:00
2002-03-22 23:42:27 +00:00
Show the number of packets, and the number of bytes in those packets,
for each protocol in the trace. It organizes the protocols in the same
hierarchy in which they were found in the trace. Besides counting the
packets in which the protocol exists, a count is also made for packets
in which the protocol is the last protocol in the stack. These
last-protocol counts show you how many packets (and the byte count
associated with those packets) B<ended> in a particular protocol. In
the table, they are listed under "End Packets" and "End Bytes".
2001-03-22 23:54:47 +00:00
2009-07-13 14:54:47 +00:00
=item Statistics:Conversations
2011-09-23 04:33:07 +00:00
Lists of conversations; selectable by protocol. See Statistics:Conversation List below.
2009-07-13 14:54:47 +00:00
=item Statistics:End Points
List of End Point Addresses by protocol with packets/bytes/.... counts.
=item Statistics:Packet Lengths
Grouped counts of packet lengths (0-19 bytes, 20-39 bytes, ...)
2019-06-20 13:16:41 +00:00
=item Statistics:I/O Graphs
2002-11-15 10:55:19 +00:00
Open a window where up to 5 graphs in different colors can be displayed
2003-12-08 17:54:32 +00:00
to indicate number of packets or number of bytes per second for all packets
2002-11-15 10:55:19 +00:00
matching the specified filter.
2003-12-08 17:54:32 +00:00
By default only one graph will be displayed showing number of packets per second.
2002-11-15 10:55:19 +00:00
2003-06-10 17:34:01 +00:00
The top part of the window contains the graphs and scales for the X and
Y axis. If the graph is too long to fit inside the window there is a
horizontal scrollbar below the drawing area that can scroll the graphs
to the left or the right. The horizontal axis displays the time into
the capture and the vertical axis will display the measured quantity at
that time.
Below the drawing area and the scrollbar are the controls. On the
bottom left there will be five similar sets of controls to control each
2009-05-02 06:44:59 +00:00
individual graph such as "Display:<button>" which button will toggle
2003-06-10 17:34:01 +00:00
that individual graph on/off. If <button> is ticked, the graph will be
2018-04-09 04:11:26 +00:00
displayed. "Color:<color>" which is just a button to show which color
will be used to draw that graph. Finally "Filter:<filter-text>" which
can be used to specify a display filter for that particular graph.
2003-06-10 17:34:01 +00:00
If filter-text is empty then all packets will be used to calculate the
quantity for that graph. If filter-text is specified only those packets
that match that display filter will be considered in the calculation of
quantity.
To the right of the 5 graph controls there are four menus to control
global aspects of the draw area and graphs. The "Unit:" menu is used to
2003-12-08 17:54:32 +00:00
control what to measure; "packets/tick", "bytes/tick" or "advanced..."
2003-06-10 17:34:01 +00:00
2003-12-08 17:54:32 +00:00
packets/tick will measure the number of packets matching the (if
2008-02-15 22:36:24 +00:00
specified) display filter for the graph in each measurement interval.
2003-06-10 17:34:01 +00:00
2003-12-08 17:54:32 +00:00
bytes/tick will measure the total number of bytes in all packets matching
2003-06-10 17:34:01 +00:00
the (if specified) display filter for the graph in each measurement
interval.
2002-11-29 11:37:33 +00:00
advanced... see below
2003-06-10 17:34:01 +00:00
"Tick interval:" specifies what measurement intervals to use. The
default is 1 second and means that the data will be counted over 1
2008-02-15 22:36:24 +00:00
second intervals.
2002-11-29 11:37:33 +00:00
2003-06-10 17:34:01 +00:00
"Pixels per tick:" specifies how many pixels wide each measurement
2008-02-15 22:36:24 +00:00
interval will be in the drawing area. The default is 5 pixels per tick.
2002-11-29 11:37:33 +00:00
2003-06-10 17:34:01 +00:00
"Y-scale:" controls the max value for the y-axis. Default value is
2006-05-31 19:12:15 +00:00
"auto" which means that B<Wireshark> will try to adjust the maxvalue
2003-06-10 17:34:01 +00:00
automatically.
2002-11-29 11:37:33 +00:00
2003-06-10 17:34:01 +00:00
"advanced..." If Unit:advanced... is selected the window will display
two more controls for each of the five graphs. One control will be a
menu where the type of calculation can be selected from
2003-10-15 13:10:54 +00:00
SUM,COUNT,MAX,MIN,AVG and LOAD, and one control, textbox, where the name of a
2003-06-10 17:34:01 +00:00
single display filter field can be specified.
2002-11-29 11:37:33 +00:00
The following restrictions apply to type and field combinations:
2004-07-10 01:01:41 +00:00
SUM: available for all types of integers and will calculate the SUM of
2010-11-09 03:30:55 +00:00
all occurrences of this field in the measurement interval. Note that
2004-07-10 02:07:23 +00:00
some field can occur multiple times in the same packet and then all
instances will be summed up. Example: 'tcp.len' which will count the
amount of payload data transferred across TCP in each interval.
2004-07-10 01:01:41 +00:00
2011-09-23 04:33:07 +00:00
COUNT: available for all field types. This will COUNT the number of times
certain field occurs in each interval. Note that some fields
2004-07-10 01:01:41 +00:00
may occur multiple times in each packet and if that is the case
then each instance will be counted independently and COUNT
will be greater than the number of packets.
2011-09-23 04:33:07 +00:00
MAX: available for all integer and relative time fields. This will calculate
2004-07-10 01:01:41 +00:00
the max seen integer/time value seen for the field during the interval.
Example: 'smb.time' which will plot the maximum SMB response time.
2011-09-23 04:33:07 +00:00
MIN: available for all integer and relative time fields. This will calculate
2004-07-10 01:01:41 +00:00
the min seen integer/time value seen for the field during the interval.
Example: 'smb.time' which will plot the minimum SMB response time.
2002-11-29 11:37:33 +00:00
2004-07-10 01:01:41 +00:00
AVG: available for all integer and relative time fields.This will
calculate the average seen integer/time value seen for the field during
the interval. Example: 'smb.time' which will plot the average SMB
response time.
LOAD: available only for relative time fields (response times).
2002-11-29 11:37:33 +00:00
Example of advanced:
Display how NFS response time MAX/MIN/AVG changes over time:
2004-07-10 01:01:41 +00:00
Set first graph to:
filter:nfs&&rpc.time
Calc:MAX rpc.time
Set second graph to
filter:nfs&&rpc.time
Calc:AVG rpc.time
Set third graph to
2002-11-29 11:37:33 +00:00
2004-07-10 01:01:41 +00:00
filter:nfs&&rpc.time
Calc:MIN rpc.time
2002-11-29 11:37:33 +00:00
Example of advanced:
2004-07-10 01:01:41 +00:00
Display how the average packet size from host a.b.c.d changes over time.
2002-11-29 11:37:33 +00:00
2004-07-10 01:01:41 +00:00
Set first graph to
2002-11-29 11:37:33 +00:00
2004-07-10 01:01:41 +00:00
filter:ip.addr==a.b.c.d&&frame.pkt_len
Calc:AVG frame.pkt_len
2002-11-29 11:37:33 +00:00
2003-10-15 13:10:54 +00:00
LOAD:
2008-02-15 22:36:24 +00:00
The LOAD io-stat type is very different from anything you have ever seen
2010-11-09 03:30:55 +00:00
before! While the response times themselves as plotted by MIN,MAX,AVG are
2008-02-15 22:36:24 +00:00
indications on the Server load (which affects the Server response time),
2003-10-15 13:10:54 +00:00
the LOAD measurement measures the Client LOAD.
2008-02-15 22:36:24 +00:00
What this measures is how much workload the client generates,
i.e. how fast will the client issue new commands when the previous ones
2003-10-15 13:10:54 +00:00
completed.
i.e. the level of concurrency the client can maintain.
The higher the number, the more and faster is the client issuing new
2011-09-23 04:33:07 +00:00
commands. When the LOAD goes down, it may be due to client load making
2003-10-15 13:10:54 +00:00
the client slower in issuing new commands (there may be other reasons as
2004-07-10 01:01:41 +00:00
well, maybe the client just doesn't have any commands it wants to issue
2003-10-15 13:10:54 +00:00
right then).
Load is measured in concurrency/number of overlapping i/o and the value
1000 means there is a constant load of one i/o.
In each tick interval the amount of overlap is measured.
See the graph below containing three commands:
Below the graph are the LOAD values for each interval that would be calculated.
2004-09-05 15:06:26 +00:00
| | | | | | | | |
| | | | | | | | |
| | o=====* | | | | | |
| | | | | | | | |
| o========* | o============* | | |
| | | | | | | | |
--------------------------------------------------> Time
500 1500 500 750 1000 500 0 0
2003-10-15 13:10:54 +00:00
2004-03-13 19:51:07 +00:00
=item Statistics:Conversation List
2003-04-27 21:52:24 +00:00
2004-03-13 19:51:07 +00:00
This option will open a new window that displays a list of all
conversations between two endpoints. The list has one row for each
unique conversation and displays total number of packets/bytes seen as
well as number of packets/bytes in each direction.
By default the list is sorted according to the number of packets but by
clicking on the column header; it is possible to re-sort the list in
ascending or descending order by any column.
2008-02-15 22:36:24 +00:00
By first selecting a conversation by clicking on it and then using the
2004-03-13 19:51:07 +00:00
right mouse button (on those platforms that have a right
2020-02-12 10:52:25 +00:00
mouse button) Wireshark will display a popup menu offering several different
2004-03-13 19:51:07 +00:00
filter operations to apply to the capture.
2006-05-22 08:21:22 +00:00
These statistics windows can also be invoked from the Wireshark command
2008-02-15 22:36:24 +00:00
line using the B<-z conv> argument.
2004-03-13 19:51:07 +00:00
2009-07-13 14:54:47 +00:00
=item Statistics:Service Response Time
=over 4
=item *
AFP
=item *
CAMEL
=item *
DCE-RPC
2004-03-13 19:51:07 +00:00
2008-02-15 22:36:24 +00:00
Open a window to display Service Response Time statistics for an
2004-03-13 19:51:07 +00:00
arbitrary DCE-RPC program
interface and display B<Procedure>, B<Number of Calls>, B<Minimum SRT>,
B<Maximum SRT> and B<Average SRT> for all procedures for that
program/version. These windows opened will update in semi-real time to
reflect changes when doing live captures or when reading new capture
2006-05-31 19:12:15 +00:00
files into B<Wireshark>.
2004-03-13 19:51:07 +00:00
This dialog will also allow an optional filter string to be used.
2008-02-15 22:36:24 +00:00
If an optional filter string is used only such DCE-RPC request/response pairs
2011-09-23 04:33:07 +00:00
that match that filter will be used to calculate the statistics. If no filter
2004-03-13 19:51:07 +00:00
string is specified all request/response pairs will be used.
2009-07-13 14:54:47 +00:00
=item *
Diameter
=item *
Fibre Channel
2004-03-13 19:51:07 +00:00
Open a window to display Service Response Time statistics for Fibre Channel
and display B<FC Type>, B<Number of Calls>, B<Minimum SRT>,
B<Maximum SRT> and B<Average SRT> for all FC types.
These windows opened will update in semi-real time to
reflect changes when doing live captures or when reading new capture
2006-05-31 19:12:15 +00:00
files into B<Wireshark>.
2004-03-13 19:51:07 +00:00
The Service Response Time is calculated as the time delta between the
First packet of the exchange and the Last packet of the exchange.
This dialog will also allow an optional filter string to be used.
2008-02-15 22:36:24 +00:00
If an optional filter string is used only such FC first/last exchange pairs
2011-09-23 04:33:07 +00:00
that match that filter will be used to calculate the statistics. If no filter
2004-03-13 19:51:07 +00:00
string is specified all request/response pairs will be used.
2009-07-13 14:54:47 +00:00
=item *
GTP
=item *
H.225 RAS
Collect requests/response SRT (Service Response Time) data for ITU-T H.225 RAS.
Data collected is B<number of calls> for each known ITU-T H.225 RAS Message Type,
B<Minimum SRT>, B<Maximum SRT>, B<Average SRT>, B<Minimum in Packet>, and B<Maximum in Packet>.
You will also get the number of B<Open Requests> (Unresponded Requests),
B<Discarded Responses> (Responses without matching request) and Duplicate Messages.
These windows opened will update in semi-real time to reflect changes when
doing live captures or when reading new capture files into B<Wireshark>.
You can apply an optional filter string in a dialog box, before starting
2011-09-23 04:33:07 +00:00
the calculation. The statistics will only be calculated
2009-07-13 14:54:47 +00:00
on those calls matching that filter.
=item *
LDAP
=item *
MEGACO
=item *
MGCP
Collect requests/response SRT (Service Response Time) data for MGCP.
Data collected is B<number of calls> for each known MGCP Type,
B<Minimum SRT>, B<Maximum SRT>, B<Average SRT>, B<Minimum in Packet>, and B<Maximum in Packet>.
These windows opened will update in semi-real time to reflect changes when
doing live captures or when reading new capture files into B<Wireshark>.
You can apply an optional filter string in a dialog box, before starting
2011-09-23 04:33:07 +00:00
the calculation. The statistics will only be calculated
2009-07-13 14:54:47 +00:00
on those calls matching that filter.
=item *
NCP
=item *
ONC-RPC
2004-03-13 19:51:07 +00:00
Open a window to display statistics for an arbitrary ONC-RPC program interface
and display B<Procedure>, B<Number of Calls>, B<Minimum SRT>, B<Maximum SRT> and B<Average SRT> for all procedures for that program/version.
2003-08-21 17:48:04 +00:00
These windows opened will update in semi-real time to reflect changes when
2006-05-31 19:12:15 +00:00
doing live captures or when reading new capture files into B<Wireshark>.
2003-04-27 21:52:24 +00:00
2004-03-13 19:51:07 +00:00
This dialog will also allow an optional filter string to be used.
2008-02-15 22:36:24 +00:00
If an optional filter string is used only such ONC-RPC request/response pairs
2011-09-23 04:33:07 +00:00
that match that filter will be used to calculate the statistics. If no filter
2004-03-13 19:51:07 +00:00
string is specified all request/response pairs will be used.
2008-02-15 22:36:24 +00:00
By first selecting a conversation by clicking on it and then using the
2004-03-13 19:51:07 +00:00
right mouse button (on those platforms that have a right
2020-02-12 10:52:25 +00:00
mouse button) Wireshark will display a popup menu offering several different
2004-03-13 19:51:07 +00:00
filter operations to apply to the capture.
2009-07-13 14:54:47 +00:00
=item *
RADIUS
=item *
SCSI
=item *
SMB
2004-03-13 19:51:07 +00:00
Collect call/reply SRT (Service Response Time) data for SMB. Data collected
2009-07-13 14:54:47 +00:00
is the number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.
2004-03-13 19:51:07 +00:00
The data will be presented as separate tables for all normal SMB commands,
all Transaction2 commands and all NT Transaction commands.
Only those commands that are seen in the capture will have its stats
displayed.
Only the first command in a xAndX command chain will be used in the
calculation. So for common SessionSetupAndX + TreeConnectAndX chains,
only the SessionSetupAndX call will be used in the statistics.
This is a flaw that might be fixed in the future.
2003-04-27 21:52:24 +00:00
You can apply an optional filter string in a dialog box, before starting
2011-09-23 04:33:07 +00:00
the calculation. The stats will only be calculated
2003-04-27 21:52:24 +00:00
on those calls matching that filter.
2008-02-15 22:36:24 +00:00
By first selecting a conversation by clicking on it and then using the
2004-03-13 19:51:07 +00:00
right mouse button (on those platforms that have a right
2020-02-12 10:52:25 +00:00
mouse button) Wireshark will display a popup menu offering several different
2004-03-13 19:51:07 +00:00
filter operations to apply to the capture.
2009-07-13 14:54:47 +00:00
=item *
2003-10-28 00:31:17 +00:00
2009-07-13 14:54:47 +00:00
SMB2
2003-10-28 00:31:17 +00:00
2009-07-13 14:54:47 +00:00
=back
2003-10-28 00:31:17 +00:00
2009-07-13 14:54:47 +00:00
=item Statistics:BOOTP-DHCP
2003-11-16 23:11:20 +00:00
2009-07-13 14:54:47 +00:00
=item Statistics:Compare
Compare two Capture Files
=item Statistics:Flow Graph
Flow Graph: General/TCP
=item Statistics:HTTP
HTTP Load Distribution, Packet Counter & Requests
=item Statistics:IP Addresses
Count/Rate/Percent by IP Address
=item Statistics:IP Destinations
Count/Rate/Percent by IP Address/protocol/port
=item Statistics:IP Protocol Types
Count/Rate/Percent by IP Protocol Types
=item Statistics:ONC-RPC Programs
2011-03-23 20:00:13 +00:00
This dialog will open a window showing aggregated SRT statistics for all
2009-07-13 14:54:47 +00:00
ONC-RPC Programs/versions that exist in the capture file.
=item Statistics:TCP Stream Graph
2010-11-09 03:30:55 +00:00
Graphs: Round Trip; Throughput; Time-Sequence (Stevens); Time-Sequence (tcptrace)
2009-07-13 14:54:47 +00:00
=item Statistics:UDP Multicast streams
2009-10-20 20:14:23 +00:00
Multicast Streams Counts/Rates/... by Source/Destination Address/Port pairs
2009-07-13 14:54:47 +00:00
=item Statistics:WLAN Traffic
2010-11-09 03:30:55 +00:00
WLAN Traffic Statistics
2009-07-13 14:54:47 +00:00
=item Telephony:ITU-T H.225
2004-03-13 19:51:07 +00:00
2011-09-23 04:33:07 +00:00
Count ITU-T H.225 messages and their reasons. In the first column you get a
2004-03-13 19:51:07 +00:00
list of H.225 messages and H.225 message reasons, which occur in the current
2011-09-23 04:33:07 +00:00
capture file. The number of occurrences of each message or reason will be displayed
2004-03-13 19:51:07 +00:00
in the second column.
This window opened will update in semi-real time to reflect changes when
2006-05-31 19:12:15 +00:00
doing live captures or when reading new capture files into B<Wireshark>.
2004-03-13 19:51:07 +00:00
You can apply an optional filter string in a dialog box, before starting
2011-09-23 04:33:07 +00:00
the counter. The statistics will only be calculated
2004-03-13 19:51:07 +00:00
on those calls matching that filter.
2009-07-13 14:54:47 +00:00
=item Telephony:SIP
2004-05-01 21:33:44 +00:00
2011-09-23 04:33:07 +00:00
Activate a counter for SIP messages. You will get the number of occurrences of each
SIP Method and of each SIP Status-Code. Additionally you also get the number of
2008-02-15 22:36:24 +00:00
resent SIP Messages (only for SIP over UDP).
2004-05-01 21:33:44 +00:00
This window opened will update in semi-real time to reflect changes when
2006-05-31 19:12:15 +00:00
doing live captures or when reading new capture files into B<Wireshark>.
2004-05-01 21:33:44 +00:00
You can apply an optional filter string in a dialog box, before starting
2011-09-23 04:33:07 +00:00
the counter. The statistics will only be calculated
2004-05-01 21:33:44 +00:00
on those calls matching that filter.
2009-07-13 14:54:47 +00:00
=item Tools:Firewall ACL Rules
2004-03-13 19:51:07 +00:00
2003-12-08 17:54:32 +00:00
=item Help:Contents
Some help texts.
=item Help:Supported Protocols
List of supported protocols and display filter protocol fields.
2005-04-11 00:10:50 +00:00
=item Help:Manual Pages
Display locally installed HTML versions of these manual pages in a web browser.
2006-05-31 19:12:15 +00:00
=item Help:Wireshark Online
2005-04-11 00:10:50 +00:00
2006-07-09 22:45:48 +00:00
Various links to online resources to be open in a web browser, like
2014-09-17 00:08:53 +00:00
L<https://www.wireshark.org>.
2005-04-11 00:10:50 +00:00
2006-05-31 19:12:15 +00:00
=item Help:About Wireshark
2003-12-08 17:54:32 +00:00
2013-06-07 17:06:27 +00:00
See various information about Wireshark (see L</About> dialog below), like the
2004-05-22 12:32:00 +00:00
version, the folders used, the available plugins, ...
2003-12-08 17:54:32 +00:00
2003-03-10 04:27:01 +00:00
=back
2002-11-15 10:55:19 +00:00
1998-09-16 02:39:15 +00:00
=head2 WINDOWS
=over 4
=item Main Window
2008-02-15 22:36:24 +00:00
The main window contains the usual things like the menu, some toolbars, the
2011-09-23 04:33:07 +00:00
main area and a statusbar. The main area is split into three panes, you can
2004-05-22 12:32:00 +00:00
resize each pane using a "thumb" at the right end of each divider line.
2011-09-23 04:33:07 +00:00
The main window is much more flexible than before. The layout of the main
2004-05-22 12:32:00 +00:00
window can be customized by the I<Layout> page in the dialog box popped
2008-02-15 22:36:24 +00:00
up by I<Edit:Preferences>, the following will describe the layout with the
2004-05-22 12:32:00 +00:00
default settings.
1998-09-16 02:39:15 +00:00
2000-05-10 06:00:22 +00:00
=over 6
2004-05-22 12:32:00 +00:00
=item Main Toolbar
2011-09-23 04:33:07 +00:00
Some menu items are available for quick access here. There is no way to
2008-02-15 22:36:24 +00:00
customize the items in the toolbar, however the toolbar can be hidden by
2004-05-22 12:32:00 +00:00
I<View:Main Toolbar>.
=item Filter Toolbar
2008-02-15 22:36:24 +00:00
A display filter can be entered into the filter toolbar.
2004-05-22 12:32:00 +00:00
A filter for HTTP, HTTPS, and DNS traffic might look like this:
2015-08-19 03:03:41 +00:00
tcp.port in {80 443 53}
2004-05-22 12:32:00 +00:00
Selecting the I<Filter:> button lets you choose from a list of named
filters that you can optionally save. Pressing the Return or Enter
keys, or selecting the I<Apply> button, will cause the filter to be
applied to the current list of packets. Selecting the I<Reset> button
clears the display filter so that all packets are displayed (again).
2008-02-15 22:36:24 +00:00
There is no way to customize the items in the toolbar, however the toolbar
2004-05-22 12:32:00 +00:00
can be hidden by I<View:Filter Toolbar>.
=item Packet List Pane
2000-05-10 06:00:22 +00:00
1998-10-13 02:10:57 +00:00
The top pane contains the list of network packets that you can scroll
2000-05-10 06:00:22 +00:00
through and select. By default, the packet number, packet timestamp,
source and destination addresses, protocol, and description are
displayed for each packet; the I<Columns> page in the dialog box popped
up by I<Edit:Preferences> lets you change this (although, unfortunately,
you currently have to save the preferences, and exit and restart
2006-05-31 19:12:15 +00:00
Wireshark, for those changes to take effect).
2000-05-10 06:00:22 +00:00
If you click on the heading for a column, the display will be sorted by
that column; clicking on the heading again will reverse the sort order
for that column.
An effort is made to display information as high up the protocol stack
as possible, e.g. IP addresses are displayed for IP packets, but the
MAC layer address is displayed for unknown packet types.
The right mouse button can be used to pop up a menu of operations.
2000-08-23 19:40:12 +00:00
The middle mouse button can be used to mark a packet.
2004-05-22 12:32:00 +00:00
=item Packet Details Pane
1998-09-16 02:39:15 +00:00
2004-05-03 23:37:39 +00:00
The middle pane contains a display of the details of the
currently-selected packet. The display shows each field and its value
in each protocol header in the stack. The right mouse button can be
used to pop up a menu of operations.
1998-09-16 02:39:15 +00:00
2004-05-22 12:32:00 +00:00
=item Packet Bytes Pane
2000-05-10 06:00:22 +00:00
2008-02-15 22:36:24 +00:00
The lowest pane contains a hex and ASCII dump of the actual packet data.
2004-05-03 23:37:39 +00:00
Selecting a field in the packet details highlights the corresponding
1998-10-13 02:10:57 +00:00
bytes in this section.
1998-09-16 02:39:15 +00:00
2000-08-23 19:40:12 +00:00
The right mouse button can be used to pop up a menu of operations.
2004-05-22 12:32:00 +00:00
=item Statusbar
2000-05-10 06:00:22 +00:00
2009-05-02 06:44:59 +00:00
The statusbar is divided into three parts, on the left some context dependent
2008-02-15 22:36:24 +00:00
things are shown, like information about the loaded file, in the center the
2008-01-21 22:27:02 +00:00
number of packets are displayed, and on the right the current configuration
profile.
1998-09-16 02:39:15 +00:00
2004-05-22 12:32:00 +00:00
The statusbar can be hidden by I<View:Statusbar>.
1998-09-16 02:39:15 +00:00
2000-05-10 06:00:22 +00:00
=back
1998-10-13 02:10:57 +00:00
=item Preferences
1998-09-16 02:39:15 +00:00
1999-12-16 08:05:46 +00:00
The I<Preferences> dialog lets you control various personal preferences
2006-05-31 19:12:15 +00:00
for the behavior of B<Wireshark>.
1998-09-16 02:39:15 +00:00
1998-10-13 02:10:57 +00:00
=over 6
2002-01-11 09:02:15 +00:00
=item User Interface Preferences
1999-12-16 06:20:18 +00:00
2002-01-11 09:02:15 +00:00
The I<User Interface> page is used to modify small aspects of the GUI to
your own personal taste:
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2317
2000-08-21 08:15:48 +00:00
=over 6
=item Selection Bars
2004-05-03 23:37:39 +00:00
The selection bar in the packet list and packet details can have either
a "browse" or "select" behavior. If the selection bar has a "browse"
2002-01-11 09:02:15 +00:00
behavior, the arrow keys will move an outline of the selection bar,
2004-05-03 23:37:39 +00:00
allowing you to browse the rest of the list or details without changing
the selection until you press the space bar. If the selection bar has a
2002-01-11 09:02:15 +00:00
"select" behavior, the arrow keys will move the selection bar and change
2004-05-03 23:37:39 +00:00
the selection to the new item in the packet list or packet details.
2002-01-11 09:02:15 +00:00
=item Save Window Position
2006-05-22 08:14:01 +00:00
If this item is selected, the position of the main Wireshark window will
2006-05-31 19:12:15 +00:00
be saved when Wireshark exits, and used when Wireshark is started again.
2002-01-11 09:02:15 +00:00
=item Save Window Size
2006-05-22 08:14:01 +00:00
If this item is selected, the size of the main Wireshark window will
2006-05-31 19:12:15 +00:00
be saved when Wireshark exits, and used when Wireshark is started again.
2002-01-11 09:02:15 +00:00
2008-01-21 22:08:50 +00:00
=item Save Window Maximized state
If this item is selected the maximize state of the main Wireshark window
will be saved when Wireshark exists, and used when Wireshark is started again.
2003-10-14 23:20:17 +00:00
=item File Open Dialog Behavior
2006-05-31 19:12:15 +00:00
This item allows the user to select how Wireshark handles the listing
2003-10-14 23:20:17 +00:00
of the "File Open" Dialog when opening trace files. "Remember Last
2006-05-31 19:12:15 +00:00
Directory" causes Wireshark to automatically position the dialog in the
directory of the most recently opened file, even between launches of Wireshark.
2003-10-14 23:20:17 +00:00
"Always Open in Directory" allows the user to define a persistent directory
that the dialog will always default to.
2004-05-22 12:32:00 +00:00
=item Directory
2003-10-14 23:20:17 +00:00
Allows the user to specify a persistent File Open directory. Trailing
slashes or backslashes will automatically be added.
2008-01-21 22:08:50 +00:00
=item File Open Preview timeout
2008-03-09 19:48:50 +00:00
This items allows the user to define how much time is spend reading the
capture file to present preview data in the File Open dialog.
2008-01-21 22:08:50 +00:00
=item Open Recent maximum list entries
2011-09-23 04:33:07 +00:00
The File menu supports a recent file list. This items allows the user to
2008-03-09 19:48:50 +00:00
specify how many files are kept track of in this list.
2008-01-21 22:08:50 +00:00
=item Ask for unsaved capture files
2008-03-09 19:48:50 +00:00
When closing a capture file or Wireshark itself if the file isn't saved yet
the user is presented the option to save the file when this item is set.
2008-01-21 22:08:50 +00:00
=item Wrap during find
2010-11-09 03:30:55 +00:00
This items determines the behavior when reaching the beginning or the end
2011-09-23 04:33:07 +00:00
of a capture file. When set the search wraps around and continues, otherwise
2008-03-09 19:48:50 +00:00
it stops.
2008-01-21 22:08:50 +00:00
=item Settings dialogs show a save button
2008-03-09 19:48:50 +00:00
This item determines if the various dialogs sport an explicit Save button
2010-11-09 03:30:55 +00:00
or that save is implicit in OK / Apply.
2008-03-09 19:48:50 +00:00
2008-01-21 22:08:50 +00:00
=item Web browser command
2011-09-23 04:33:07 +00:00
This entry specifies the command line to launch a web browser. It is used
to access online content, like the Wiki and user guide. Use '%s' to place
2008-03-09 19:48:50 +00:00
the request URL in the command line.
2004-05-22 12:32:00 +00:00
=back
=item Layout Preferences
The I<Layout> page lets you specify the general layout of the main window.
2008-02-15 22:36:24 +00:00
You can choose from six different layouts and fill the three panes with the
2004-05-22 12:32:00 +00:00
contents you like.
2008-01-21 22:08:50 +00:00
=over 6
=item Scrollbars
The vertical scrollbars in the three panes can be set to be either on
the left or the right.
=item Alternating row colors
=item Hex Display
The highlight method in the hex dump display for the selected protocol
item can be set to use either inverse video, or bold characters.
=item Toolbar style
=item Filter toolbar placement
=item Custom window title
=back
2004-05-22 12:32:00 +00:00
=item Column Preferences
The I<Columns> page lets you specify the number, title, and format
of each column in the packet list.
The I<Column title> entry is used to specify the title of the column
displayed at the top of the packet list. The type of data that the column
displays can be specified using the I<Column format> option menu.
The row of buttons on the left perform the following actions:
=over 6
=item New
Adds a new column to the list.
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2317
2000-08-21 08:15:48 +00:00
2004-05-22 12:32:00 +00:00
=item Delete
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2317
2000-08-21 08:15:48 +00:00
2004-05-22 12:32:00 +00:00
Deletes the currently selected list item.
2000-08-23 19:40:12 +00:00
2004-05-22 12:32:00 +00:00
=item Up / Down
Moves the selected list item up or down one position.
2000-08-23 19:40:12 +00:00
Instead of each set of built-in preferences having "ok", "save",
"cancel", and "delete" methods, give them:
"fetch" - fetch from the notebook tab any values not already
stored in "prefs", and store them there, but doesn't apply them;
"apply" - apply the settings in "prefs";
"destroy" - clean up any windows created from the tab.
As we no longer have "cancel" methods, we don't have per-preference code
to revert preference values; instead, we have the common preference
dialog box code make a copy of all the current preferences, and, when
the "Cancel" button is clicked, free the current preferences and copy
the saved preferences to it, and apply the preferences.
Add an "Apply" button to the preference dialog box, which applies the
current preferences without closing the dialog box.
Treat a request to delete the preferences dialog box as equivalent to
clicking "Cancel".
Have a "remember_ptree_widget()" routine to remember all protocol tree
widgets, and use the list of those widgets when we set GUI preferences
for the protocol tree widgets, rather than setting the main protocol
tree widget and then using the list of packet windows. Move that code
out of "main.c" to "proto_draw.c", as it's not used by anything in
"main.c", but is used by stuff in "proto_draw.c".
Make the font one of the preferences we can set on the fly for protocol
tree widgets. Also make it something we can set on the fly for the
packet list widget.
svn path=/trunk/; revision=2317
2000-08-21 08:15:48 +00:00
=back
2004-05-22 12:32:00 +00:00
=item Font Preferences
The I<Font> page lets you select the font to be used for most text.
=item Color Preferences
The I<Colors> page can be used to change the color of the text
2011-09-23 04:33:07 +00:00
displayed in the TCP stream window and for marked packets. To change a color,
2008-02-15 22:36:24 +00:00
simply select an attribute from the "Set:" menu and use the color selector to
2004-05-22 12:32:00 +00:00
get the desired color. The new text colors are displayed as a sample text.
2002-01-11 09:02:15 +00:00
=item Capture Preferences
The I<Capture> page lets you specify various parameters for capturing
live packet data; these are used the first time a capture is started.
The I<Interface:> combo box lets you specify the interface from which to
capture packet data, or the name of a FIFO from which to get the packet
2003-11-01 02:30:18 +00:00
data.
The I<Data link type:> option menu lets you, for some interfaces, select
the data link header you want to see on the packets you capture. For
example, in some OSes and with some versions of libpcap, you can choose,
on an 802.11 interface, whether the packets should appear as Ethernet
packets (with a fake Ethernet header) or as 802.11 packets.
The I<Limit each packet to ... bytes> check box lets you set the
snapshot length to use when capturing live data; turn on the check box,
and then set the number of bytes to use as the snapshot length.
The I<Filter:> text entry lets you set a capture filter expression to be
used when capturing.
2003-11-18 04:19:48 +00:00
If any of the environment variables SSH_CONNECTION, SSH_CLIENT,
2006-09-15 21:35:01 +00:00
REMOTEHOST, DISPLAY, or SESSIONNAME are set, Wireshark will create a
2003-11-18 04:19:48 +00:00
default capture filter that excludes traffic from the hosts and ports
defined in those variables.
2003-11-01 02:30:18 +00:00
The I<Capture packets in promiscuous mode> check box lets you specify
whether to put the interface in promiscuous mode when capturing.
The I<Update list of packets in real time> check box lets you specify
that the display should be updated as packets are seen.
The I<Automatic scrolling in live capture> check box lets you specify
whether, in an "Update list of packets in real time" capture, the packet
list pane should automatically scroll to show the most recently captured
packets.
2002-01-11 09:02:15 +00:00
2004-05-22 12:32:00 +00:00
=item Printing Preferences
The radio buttons at the top of the I<Printing> page allow you choose
between printing packets with the I<File:Print Packet> menu item as text
or PostScript, and sending the output directly to a command or saving it
to a file. The I<Command:> text entry box, on UNIX-compatible systems,
is the command to send files to (usually B<lpr>), and the I<File:> entry
2008-02-15 22:36:24 +00:00
box lets you enter the name of the file you wish to save to.
2004-05-22 12:32:00 +00:00
Additionally, you can select the I<File:> button to browse the file
system for a particular save file.
2008-01-21 22:08:50 +00:00
=item Name Resolution Preferences
The I<Enable MAC name resolution>, I<Enable network name resolution> and
I<Enable transport name resolution> check boxes let you specify whether
MAC addresses, network addresses, and transport-layer port numbers
should be translated to names.
The I<Enable concurrent DNS name resolution> allows Wireshark to send out
multiple name resolution requests and not wait for the result before
2011-09-23 04:33:07 +00:00
continuing dissection. This speeds up dissection with network name
resolution but initially may miss resolutions. The number of concurrent
2008-01-21 22:08:50 +00:00
requests can be set here as well.
I<SMI paths>
I<SMI modules>
=item RTP Player Preferences
This page allows you to select the number of channels visible in the
2011-09-23 04:33:07 +00:00
RTP player window. It determines the height of the window, more channels
2008-01-21 22:08:50 +00:00
are possible and visible by means of a scroll bar.
2000-07-09 04:09:09 +00:00
=item Protocol Preferences
2006-05-31 19:12:15 +00:00
There are also pages for various protocols that Wireshark dissects,
controlling the way Wireshark handles those protocols.
2000-07-09 04:09:09 +00:00
1999-12-16 06:20:18 +00:00
=back
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
=item Edit Capture Filter List
=item Edit Display Filter List
=item Capture Filter
=item Display Filter
=item Read Filter
=item Search Filter
The I<Edit Capture Filter List> dialog lets you create, modify, and
delete capture filters, and the I<Edit Display Filter List> dialog lets
you create, modify, and delete display filters.
The I<Capture Filter> dialog lets you do all of the editing operations
listed, and also lets you choose or construct a filter to be used when
capturing packets.
The I<Display Filter> dialog lets you do all of the editing operations
listed, and also lets you choose or construct a filter to be used to
filter the current capture being viewed.
The I<Read Filter> dialog lets you do all of the editing operations
listed, and also lets you choose or construct a filter to be used to
as a read filter for a capture file you open.
1999-12-10 06:28:24 +00:00
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
The I<Search Filter> dialog lets you do all of the editing operations
listed, and also lets you choose or construct a filter expression to be
used in a find operation.
1999-12-10 06:28:24 +00:00
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
In all of those dialogs, the I<Filter name> entry specifies a
descriptive name for a filter, e.g. B<Web and DNS traffic>. The
I<Filter string> entry is the text that actually describes the filtering
action to take, as described above.The dialog buttons perform the
following actions:
1998-12-29 04:05:38 +00:00
=over 6
=item New
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
If there is text in the two entry boxes, creates a new associated list
1999-12-10 06:28:24 +00:00
item.
1998-12-29 04:05:38 +00:00
2004-03-13 19:51:07 +00:00
=item Edit
1998-12-29 04:05:38 +00:00
1999-12-10 06:28:24 +00:00
Modifies the currently selected list item to match what's in the entry
boxes.
1998-12-29 04:05:38 +00:00
=item Delete
Deletes the currently selected list item.
2001-01-02 01:32:21 +00:00
=item Add Expression...
1998-12-29 04:05:38 +00:00
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
For display filter expressions, pops up a dialog box to allow you to
construct a filter expression to test a particular field; it offers
lists of field names, and, when appropriate, lists from which to select
tests to perform on the field and values with which to compare it. In
that dialog box, the OK button will cause the filter expression you
constructed to be entered into the I<Filter string> entry at the current
cursor position.
1998-12-29 04:05:38 +00:00
=item OK
2001-01-28 21:30:53 +00:00
In the I<Capture Filter> dialog, closes the dialog box and makes the
filter in the I<Filter string> entry the filter in the I<Capture
Preferences> dialog. In the I<Display Filter> dialog, closes the dialog
box and makes the filter in the I<Filter string> entry the current
display filter, and applies it to the current capture. In the I<Read
Filter> dialog, closes the dialog box and makes the filter in the
2008-02-15 22:36:24 +00:00
I<Filter string> entry the filter in the I<Open Capture File> dialog.
2001-01-28 21:30:53 +00:00
In the I<Search Filter> dialog, closes the dialog box and makes the
2003-12-08 17:54:32 +00:00
filter in the I<Filter string> entry the filter in the I<Find Packet>
2001-01-28 21:30:53 +00:00
dialog.
2001-01-02 01:32:21 +00:00
=item Apply
Have separate capture and display filter lists; some filter dialog boxes
use the capture filter lists, and others use the display filter list, as
appropriate.
Have separate menu items for editing the capture and display filter
lists.
Have separate "~/.ethereal/cfilters" and "~/.ethereal/dfilters" files
for the two lists; if either of those files isn't found, we try
"~/.ethereal/filters", which means that you will start out with two
identical lists holding all your filters - if certain filters belong
only in one list, you'll have to delete them by hand from the other
list.
Do I/O error checking when reading and writing filter lists; when
writing a filter list, write it to a new file, and then rename the new
file on top of the old file, so that you don't lose your old filter list
if, for example, you run out of disk space or disk quota.
svn path=/trunk/; revision=2948
2001-01-28 09:13:10 +00:00
Makes the filter in the I<Filter string> entry the current display
filter, and applies it to the current capture.
1998-12-29 04:05:38 +00:00
=item Save
2004-10-26 23:30:33 +00:00
If the list of filters being edited is the list of
capture filters, saves the current filter list to the personal capture
filters file, and if the list of filters being edited is the list of
display filters, saves the current filter list to the personal display
filters file.
1998-12-29 04:05:38 +00:00
2001-01-28 21:30:53 +00:00
=item Close
1998-12-29 04:05:38 +00:00
2001-01-28 21:30:53 +00:00
Closes the dialog without doing anything with the filter in the I<Filter
string> entry.
1998-12-29 04:05:38 +00:00
=back
2004-05-22 12:32:00 +00:00
=item The Color Filters Dialog
This dialog displays a list of color filters and allows it to be
modified.
=over
=item THE FILTER LIST
2011-09-23 04:33:07 +00:00
Single rows may be selected by clicking. Multiple rows may be selected
2004-05-22 12:32:00 +00:00
by using the ctrl and shift keys in combination with the mouse button.
=item NEW
Adds a new filter at the bottom of the list and opens the Edit Color
2011-09-23 04:33:07 +00:00
Filter dialog box. You will have to alter the filter expression at
least before the filter will be accepted. The format of color filter
expressions is identical to that of display filters. The new filter is
2004-05-22 12:32:00 +00:00
selected, so it may immediately be moved up and down, deleted or edited.
To avoid confusion all filters are unselected before the new filter is
created.
=item EDIT
Opens the Edit Color Filter dialog box for the selected filter. (If this
button is disabled you may have more than one filter selected, making it
ambiguous which is to be edited.)
2007-11-24 11:38:16 +00:00
=item ENABLE
Enables the selected color filter(s).
=item DISABLE
Disables the selected color filter(s).
2004-05-22 12:32:00 +00:00
=item DELETE
Deletes the selected color filter(s).
=item EXPORT
Allows you to choose a file in which to save the current list of color
2011-09-23 04:33:07 +00:00
filters. You may also choose to save only the selected filters. A
2004-05-22 12:32:00 +00:00
button is provided to save the filters in the global color filters file
(you must have sufficient permissions to write this file, of course).
=item IMPORT
Allows you to choose a file containing color filters which are then
2011-09-23 04:33:07 +00:00
added to the bottom of the current list. All the added filters are
2004-05-22 12:32:00 +00:00
selected, so they may be moved to the correct position in the list as a
2011-09-23 04:33:07 +00:00
group. To avoid confusion, all filters are unselected before the new
filters are imported. A button is provided to load the filters from the
2004-05-22 12:32:00 +00:00
global color filters file.
=item CLEAR
Deletes your personal color filters file, reloads the global
color filters file, if any, and closes the dialog.
=item UP
Moves the selected filter(s) up the list, making it more likely that
they will be used to color packets.
=item DOWN
Moves the selected filter(s) down the list, making it less likely that
they will be used to color packets.
=item OK
Closes the dialog and uses the color filters as they stand.
=item APPLY
Colors the packets according to the current list of color filters, but
does not close the dialog.
=item SAVE
Saves the current list of color filters in your personal color filters
2011-09-23 04:33:07 +00:00
file. Unless you do this they will not be used the next time you start
2006-05-31 19:12:15 +00:00
Wireshark.
2004-05-22 12:32:00 +00:00
=item CLOSE
2011-09-23 04:33:07 +00:00
Closes the dialog without changing the coloration of the packets. Note
2004-05-22 12:32:00 +00:00
that changes you have made to the current list of color filters are not
undone.
=back
2013-06-07 17:06:27 +00:00
=item Capture Options Dialog
1998-10-13 02:10:57 +00:00
2013-06-07 17:06:27 +00:00
The I<Capture Options Dialog> lets you specify various parameters for
1998-10-13 02:10:57 +00:00
capturing live packet data.
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
The I<Interface:> field lets you specify the interface from which to
2002-01-11 09:02:15 +00:00
capture packet data or a command from which to get the packet data via a
pipe.
2004-03-13 19:51:07 +00:00
The I<Link layer header type:> field lets you specify the interfaces link
2011-09-23 04:33:07 +00:00
layer header type. This field is usually disabled, as most interface have
2004-03-13 19:51:07 +00:00
only one header type.
2002-01-11 09:02:15 +00:00
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
The I<Capture packets in promiscuous mode> check box lets you specify
whether the interface should be put into promiscuous mode when
capturing.
2002-01-11 09:02:15 +00:00
2004-03-13 19:51:07 +00:00
The I<Limit each packet to ... bytes> check box and field lets you
specify a maximum number of bytes per packet to capture and save; if the
2017-03-27 12:55:05 +00:00
check box is not checked, the limit will be 262144 bytes.
2004-03-13 19:51:07 +00:00
The I<Capture Filter:> entry lets you specify the capture filter using a
2002-01-11 09:02:15 +00:00
tcpdump-style filter string as described above.
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
The I<File:> entry lets you specify the file into which captured packets
should be saved, as in the I<Printer Options> dialog above. If not
specified, the captured packets will be saved in a temporary file; you
can save those packets to a file with the I<File:Save As> menu item.
2004-03-13 19:51:07 +00:00
The I<Use multiple files> check box lets you specify that the capture
2011-09-23 04:33:07 +00:00
should be done in "multiple files" mode. This option is disabled, if the
2004-03-13 19:51:07 +00:00
I<Update list of packets in real time> option is checked.
2003-05-15 13:40:20 +00:00
2004-03-13 19:51:07 +00:00
The I<Next file every ... megabyte(s)> check box and fields lets
you specify that a switch to a next file should be done
2011-09-23 04:33:07 +00:00
if the specified filesize is reached. You can also select the appropriate
2013-08-29 18:15:13 +00:00
unit, but beware that the filesize has a maximum of 2 GiB.
2008-02-15 22:36:24 +00:00
The check box is forced to be checked, as "multiple files" mode requires a
2004-03-13 19:51:07 +00:00
file size to be specified.
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
2008-02-15 22:36:24 +00:00
The I<Next file every ... minute(s)> check box and fields lets
2004-03-13 19:51:07 +00:00
you specify that the switch to a next file should be done after the specified
time has elapsed, even if the specified capture size is not reached.
2008-02-15 22:36:24 +00:00
The I<Ring buffer with ... files> field lets you specify the number
2013-12-02 19:17:12 +00:00
of files of a ring buffer. This feature will capture into the first file
again, after the specified number of files have been used.
2004-03-13 19:51:07 +00:00
2008-02-15 22:36:24 +00:00
The I<Stop capture after ... files> field lets you specify the number
2004-03-13 19:51:07 +00:00
of capture files used, until the capture is stopped.
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
2004-03-13 19:51:07 +00:00
The I<Stop capture after ... packet(s)> check box and field let
2006-05-31 19:12:15 +00:00
you specify that Wireshark should stop capturing after having captured
some number of packets; if the check box is not checked, Wireshark will
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
not stop capturing at some fixed number of captured packets.
2008-02-15 22:36:24 +00:00
The I<Stop capture after ... megabyte(s)> check box and field lets
you specify that Wireshark should stop capturing after the file to which
captured packets are being saved grows as large as or larger than some
2011-09-23 04:33:07 +00:00
specified number of megabytes. If the check box is not checked, Wireshark
2008-02-15 22:36:24 +00:00
will not stop capturing at some capture file size (although the operating
system on which Wireshark is running, or the available disk space, may still
2011-09-23 04:33:07 +00:00
limit the maximum size of a capture file). This option is disabled, if
2008-02-15 22:36:24 +00:00
"multiple files" mode is used,
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
The I<Stop capture after ... second(s)> check box and field let you
2006-05-31 19:12:15 +00:00
specify that Wireshark should stop capturing after it has been capturing
for some number of seconds; if the check box is not checked, Wireshark
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
will not stop capturing after some fixed time has elapsed.
2004-03-13 19:51:07 +00:00
The I<Update list of packets in real time> check box lets you specify
whether the display should be updated as packets are captured and, if
you specify that, the I<Automatic scrolling in live capture> check box
lets you specify the packet list pane should automatically scroll to
show the most recently captured packets as new packets arrive.
Have Wiretap set the snapshot length to 0 if it can't be derived from
reading the capture file. Have callers of "wtap_snapshot_length()"
treat a value of 0 as "unknown", and default to WTAP_MAX_PACKET_SIZE (so
that, when writing a capture file in a format that *does* store the
snapshot length, we can at least put *something* in the file).
If we don't know the snapshot length of the current capture file, don't
display a value in the summary window.
Don't use "cfile.snap" as the snapshot length option when capturing -
doing so causes Ethereal to default, when capturing, to the snapshot
length of the last capture file that you read in, rather than to the
snapshot length of the last capture you did (or the initial default of
"no snapshot length").
Redo the "Capture Options" dialog box to group options into sections
with frames around them, and add units to the snapshot length, maximum
file size, and capture duration options, as per a suggestion by Ulf
Lamping. Also add units to the capture count option.
Make the snapshot length, capture count, maximum file size, and capture
duration options into a combination of a check box and a spin button.
If the check box is not checked, the limit in question is inactive
(snapshot length of 65535, no max packet count, no max file size, no max
capture duration); if it's checked, the spinbox specifies the limit.
Default all of the check boxes to "not checked" and all of the spin
boxes to small values.
Use "gtk_toggle_button_get_active()" rather than directly fetching the
state of a check box.
svn path=/trunk/; revision=4709
2002-02-08 10:07:41 +00:00
The I<Enable MAC name resolution>, I<Enable network name resolution> and
I<Enable transport name resolution> check boxes let you specify whether
MAC addresses, network addresses, and transport-layer port numbers
should be translated to names.
1998-10-13 02:10:57 +00:00
2004-05-22 12:32:00 +00:00
=item About
2006-05-31 19:12:15 +00:00
The I<About> dialog lets you view various information about Wireshark.
2004-05-22 12:32:00 +00:00
2006-05-31 19:12:15 +00:00
=item About:Wireshark
2004-05-22 12:32:00 +00:00
2008-02-15 22:36:24 +00:00
The I<Wireshark> page lets you view general information about Wireshark,
2004-05-22 12:32:00 +00:00
like the installed version, licensing information and such.
=item About:Authors
The I<Authors> page shows the author and all contributors.
=item About:Folders
2006-05-31 19:12:15 +00:00
The I<Folders> page lets you view the directory names where Wireshark is
2004-05-22 12:32:00 +00:00
searching it's various configuration and other files.
=item About:Plugins
1999-12-13 12:29:42 +00:00
2004-05-22 12:32:00 +00:00
The I<Plugins> page lets you view the dissector plugin modules
2001-01-28 21:22:54 +00:00
available on your system.
The I<Plugins List> shows the name and version of each dissector plugin
2005-07-19 20:44:45 +00:00
module found on your system.
On Unix-compatible systems, the plugins are looked for in the following
2006-05-31 19:12:15 +00:00
directories: the F<lib/wireshark/plugins/$VERSION> directory under the
2001-10-23 08:15:11 +00:00
main installation directory (for example,
2006-05-31 19:12:15 +00:00
F</usr/local/lib/wireshark/plugins/$VERSION>), and then
F<$HOME/.wireshark/plugins>.
2005-07-19 20:44:45 +00:00
On Windows systems, the plugins are looked for in the following
directories: F<plugins\$VERSION> directory under the main installation
2006-05-31 19:12:15 +00:00
directory (for example, F<C:\Program Files\Wireshark\plugins\$VERSION>),
and then F<%APPDATA%\Wireshark\plugins\$VERSION> (or, if %APPDATA% isn't
defined, F<%USERPROFILE%\Application Data\Wireshark\plugins\$VERSION>).
2005-07-19 20:44:45 +00:00
$VERSION is the version number of the plugin interface, which
2006-05-31 19:12:15 +00:00
is typically the version number of Wireshark. Note that a dissector
2001-10-23 08:15:11 +00:00
plugin module may support more than one protocol; there is not
necessarily a one-to-one correspondence between dissector plugin modules
and protocols. Protocols supported by a dissector plugin module are
enabled and disabled using the I<Edit:Protocols> dialog box, just as
2006-05-31 19:12:15 +00:00
protocols built into Wireshark are.
1999-12-13 12:29:42 +00:00
2003-03-10 04:27:01 +00:00
=back
1999-10-10 16:25:28 +00:00
=head1 CAPTURE FILTER SYNTAX
2012-02-03 09:07:24 +00:00
See the manual page of pcap-filter(7) or, if that doesn't exist, tcpdump(8),
2020-09-17 21:16:50 +00:00
or, if that doesn't exist, L<https://gitlab.com/wireshark/wireshark/-/wikis/CaptureFilters>.
1999-10-10 16:25:28 +00:00
2003-10-01 20:36:36 +00:00
=head1 DISPLAY FILTER SYNTAX
1999-07-15 15:33:52 +00:00
2003-10-01 14:59:41 +00:00
For a complete table of protocol and protocol fields that are filterable
2006-07-09 22:45:48 +00:00
in B<Wireshark> see the wireshark-filter(4) manual page.
1999-07-15 15:33:52 +00:00
1999-11-20 03:39:27 +00:00
=head1 FILES
1999-11-20 03:56:10 +00:00
2006-05-31 19:12:15 +00:00
These files contains various B<Wireshark> configuration settings.
2005-06-04 04:14:02 +00:00
=over 4
=item Preferences
2005-07-19 20:44:45 +00:00
The F<preferences> files contain global (system-wide) and personal
2011-09-23 04:33:07 +00:00
preference settings. If the system-wide preference file exists, it is
read first, overriding the default settings. If the personal preferences
file exists, it is read next, overriding any previous values. Note: If
2005-07-19 20:44:45 +00:00
the command line flag B<-o> is used (possibly more than once), it will
in turn override values from the preferences files.
2005-06-04 04:14:02 +00:00
2008-02-15 22:36:24 +00:00
The preferences settings are in the form I<prefname>B<:>I<value>,
2005-06-04 04:14:02 +00:00
one per line,
2005-07-19 20:44:45 +00:00
where I<prefname> is the name of the preference
and I<value> is the value to
2005-03-01 00:05:57 +00:00
which it should be set; white space is allowed between B<:> and
I<value>. A preference setting can be continued on subsequent lines by
indenting the continuation lines with white space. A B<#> character
2005-06-09 19:49:56 +00:00
starts a comment that runs to the end of the line:
# Vertical scrollbars should be on right side?
# TRUE or FALSE (case-insensitive).
gui.scrollbar_on_right: TRUE
2000-07-09 04:09:09 +00:00
2006-05-31 19:12:15 +00:00
The global preferences file is looked for in the F<wireshark> directory
2005-07-19 20:44:45 +00:00
under the F<share> subdirectory of the main installation directory (for
2006-05-31 19:12:15 +00:00
example, F</usr/local/share/wireshark/preferences>) on UNIX-compatible
2005-07-19 20:44:45 +00:00
systems, and in the main installation directory (for example,
2006-05-31 19:12:15 +00:00
F<C:\Program Files\Wireshark\preferences>) on Windows systems.
2005-06-04 04:14:02 +00:00
2017-03-03 11:31:14 +00:00
The personal preferences file is looked for in
F<$XDG_CONFIG_HOME/wireshark/preferences>
(or, if F<$XDG_CONFIG_HOME/wireshark> does not exist while F<$HOME/.wireshark>
is present, F<$HOME/.wireshark/preferences>) on
2006-05-31 19:12:15 +00:00
UNIX-compatible systems and F<%APPDATA%\Wireshark\preferences> (or, if
2005-06-04 04:14:02 +00:00
%APPDATA% isn't defined, F<%USERPROFILE%\Application
2006-05-31 19:12:15 +00:00
Data\Wireshark\preferences>) on Windows systems.
2000-07-09 04:09:09 +00:00
2005-06-04 04:14:02 +00:00
Note: Whenever the preferences are saved by using the I<Save> button
2001-10-23 08:15:11 +00:00
in the I<Edit:Preferences> dialog box, your personal preferences file
2008-02-15 22:36:24 +00:00
will be overwritten with the new settings, destroying any comments and
2005-06-09 19:49:56 +00:00
unknown/obsolete settings that were in the file.
2000-07-09 04:09:09 +00:00
2005-06-04 04:14:02 +00:00
=item Recent
2005-07-19 20:44:45 +00:00
The F<recent> file contains personal settings (mostly GUI related) such
2011-09-23 04:33:07 +00:00
as the current B<Wireshark> window size. The file is saved at program exit and
read in at program start automatically. Note: The command line flag B<-o>
2005-07-19 20:44:45 +00:00
may be used to override settings from this file.
2005-06-04 04:14:02 +00:00
2005-07-19 20:44:45 +00:00
The settings in this file have the same format as in the F<preferences>
files, and the same directory as for the personal preferences file is
used.
2005-06-04 04:14:02 +00:00
2006-05-22 08:14:01 +00:00
Note: Whenever Wireshark is closed, your recent file
2008-02-15 22:36:24 +00:00
will be overwritten with the new settings, destroying any comments and
2005-06-09 19:49:56 +00:00
unknown/obsolete settings that were in the file.
2005-06-04 04:14:02 +00:00
=item Disabled (Enabled) Protocols
2005-07-19 20:44:45 +00:00
The F<disabled_protos> files contain system-wide and personal lists of
2003-08-07 00:56:30 +00:00
protocols that have been disabled, so that their dissectors are never
2005-07-19 20:44:45 +00:00
called. The files contain protocol names, one per line, where the
2003-08-07 00:56:30 +00:00
protocol name is the same name that would be used in a display filter
2005-06-09 19:49:56 +00:00
for the protocol:
http
tcp # a comment
2005-07-19 20:44:45 +00:00
If a protocol is listed in the global F<disabled_protos> file, it is not
displayed in the I<Analyze:Enabled Protocols> dialog box, and so cannot
be enabled by the user.
The global F<disabled_protos> file uses the same directory as the global
preferences file.
The personal F<disabled_protos> file uses the same directory as the
personal preferences file.
2003-08-07 00:56:30 +00:00
2005-07-19 20:44:45 +00:00
Note: Whenever the disabled protocols list is saved by using the I<Save>
button in the I<Analyze:Enabled Protocols> dialog box, your personal
disabled protocols file will be overwritten with the new settings,
destroying any comments that were in the file.
2003-08-07 00:56:30 +00:00
2005-06-04 04:14:02 +00:00
=item Name Resolution (hosts)
2005-07-19 20:44:45 +00:00
If the personal F<hosts> file exists, it is
used to resolve IPv4 and IPv6 addresses before any other
attempts are made to resolve them. The file has the standard F<hosts>
2005-01-13 09:09:56 +00:00
file syntax; each line contains one IP address and name, separated by
2011-09-23 04:33:07 +00:00
whitespace. The same directory as for the personal preferences file is used.
2005-01-13 09:09:56 +00:00
2010-04-12 21:35:19 +00:00
Capture filter name resolution is handled by libpcap on UNIX-compatible
2013-07-28 21:12:07 +00:00
systems and WinPcap on Windows. As such the Wireshark personal F<hosts> file
2010-04-12 21:35:19 +00:00
will not be consulted for capture filter name resolution.
2015-05-27 14:40:38 +00:00
=item Name Resolution (subnets)
2016-07-15 00:21:58 +00:00
If an IPv4 address cannot be translated via name resolution (no exact
2015-05-27 14:40:38 +00:00
match is found) then a partial match is attempted via the F<subnets> file.
2017-01-23 03:51:54 +00:00
Both the global F<subnets> file and personal F<subnets> files are used
if they exist.
2015-05-27 14:40:38 +00:00
Each line of this file consists of an IPv4 address, a subnet mask length
separated only by a / and a name separated by whitespace. While the address
must be a full IPv4 address, any values beyond the mask length are subsequently
ignored.
An example is:
# Comments must be prepended by the # sign!
192.168.0.0/24 ws_test_network
A partially matched name will be printed as "subnet-name.remaining-address".
For example, "192.168.0.1" under the subnet above would be printed as
"ws_test_network.1"; if the mask length above had been 16 rather than 24, the
printed address would be ``ws_test_network.0.1".
2005-06-04 04:14:02 +00:00
=item Name Resolution (ethers)
2008-02-15 22:36:24 +00:00
The F<ethers> files are consulted to correlate 6-byte hardware addresses to
2011-09-23 04:33:07 +00:00
names. First the personal F<ethers> file is tried and if an address is not
2005-07-24 14:35:12 +00:00
found there the global F<ethers> file is tried next.
2005-06-04 04:14:02 +00:00
2005-07-19 20:44:45 +00:00
Each line contains one hardware address and name, separated by
whitespace. The digits of the hardware address are separated by colons
(:), dashes (-) or periods (.). The same separator character must be
2011-09-23 04:33:07 +00:00
used consistently in an address. The following three lines are valid
2005-07-19 20:44:45 +00:00
lines of an F<ethers> file:
1999-11-21 16:32:23 +00:00
ff:ff:ff:ff:ff:ff Broadcast
c0-00-ff-ff-ff-ff TR_broadcast
00.00.00.00.00.00 Zero_broadcast
2005-07-19 20:44:45 +00:00
The global F<ethers> file is looked for in the F</etc> directory on
2001-10-11 01:21:50 +00:00
UNIX-compatible systems, and in the main installation directory (for
2006-05-31 19:12:15 +00:00
example, F<C:\Program Files\Wireshark>) on Windows systems.
2005-06-04 04:14:02 +00:00
2008-02-15 22:36:24 +00:00
The personal F<ethers> file is looked for in the same directory as the personal
2005-06-04 04:14:02 +00:00
preferences file.
2010-04-12 21:35:19 +00:00
Capture filter name resolution is handled by libpcap on UNIX-compatible
2013-07-28 21:12:07 +00:00
systems and WinPcap on Windows. As such the Wireshark personal F<ethers> file
2010-04-12 21:35:19 +00:00
will not be consulted for capture filter name resolution.
2005-06-04 04:14:02 +00:00
=item Name Resolution (manuf)
2008-02-15 22:36:24 +00:00
The F<manuf> file is used to match the 3-byte vendor portion of a 6-byte
hardware address with the manufacturer's name; it can also contain well-known
MAC addresses and address ranges specified with a netmask. The format of the
2005-07-19 20:44:45 +00:00
file is the same as the F<ethers> files, except that entries such as:
2002-09-09 19:53:38 +00:00
00:00:0C Cisco
can be provided, with the 3-byte OUI and the name for a vendor, and
2005-07-19 20:44:45 +00:00
entries such as:
2002-09-09 19:53:38 +00:00
00-00-0C-07-AC/40 All-HSRP-routers
can be specified, with a MAC address and a mask indicating how many bits
2011-09-23 04:33:07 +00:00
of the address must match. The above entry, for example, has 40
2005-07-19 20:44:45 +00:00
significant bits, or 5 bytes, and would match addresses from
2011-09-23 04:33:07 +00:00
00-00-0C-07-AC-00 through 00-00-0C-07-AC-FF. The mask need not be a
2002-09-09 19:53:38 +00:00
multiple of 8.
2001-10-21 19:54:49 +00:00
2005-07-19 20:44:45 +00:00
The F<manuf> file is looked for in the same directory as the global
preferences file.
2005-06-04 04:14:02 +00:00
2015-05-27 15:08:26 +00:00
=item Name Resolution (services)
The F<services> file is used to translate port numbers into names.
2017-01-23 03:51:54 +00:00
Both the global F<services> file and personal F<services> files are used
if they exist.
2015-05-27 15:08:26 +00:00
The file has the standard F<services> file syntax; each line contains one
(service) name and one transport identifier separated by white space. The
transport identifier includes one port number and one transport protocol name
(typically tcp, udp, or sctp) separated by a /.
An example is:
mydns 5045/udp # My own Domain Name Server
mydns 5045/tcp # My own Domain Name Server
2005-06-04 04:14:02 +00:00
=item Name Resolution (ipxnets)
2008-02-15 22:36:24 +00:00
The F<ipxnets> files are used to correlate 4-byte IPX network numbers to
2011-09-23 04:33:07 +00:00
names. First the global F<ipxnets> file is tried and if that address is not
2005-06-04 04:14:02 +00:00
found there the personal one is tried next.
The format is the same as the F<ethers>
2008-02-15 22:36:24 +00:00
file, except that each address is four bytes instead of six.
2005-07-19 20:44:45 +00:00
Additionally, the address can be represented as a single hexadecimal
2008-02-15 22:36:24 +00:00
number, as is more common in the IPX world, rather than four hex octets.
2005-01-13 09:09:56 +00:00
For example, these four lines are valid lines of an F<ipxnets> file:
1999-11-21 16:32:23 +00:00
C0.A8.2C.00 HR
c0-a8-1c-00 CEO
00:00:BE:EF IT_Server1
110f FileServer3
1999-11-20 03:39:27 +00:00
2005-07-19 20:44:45 +00:00
The global F<ipxnets> file is looked for in the F</etc> directory on
2005-06-04 04:14:02 +00:00
UNIX-compatible systems, and in the main installation directory (for
2006-05-31 19:12:15 +00:00
example, F<C:\Program Files\Wireshark>) on Windows systems.
2005-06-04 04:14:02 +00:00
2005-07-19 20:44:45 +00:00
The personal F<ipxnets> file is looked for in the same directory as the
personal preferences file.
2005-06-04 04:14:02 +00:00
=item Capture Filters
2004-10-26 23:30:33 +00:00
2008-02-15 22:36:24 +00:00
The F<cfilters> files contain system-wide and personal capture filters.
Each line contains one filter, starting with the string displayed in the
2005-06-09 19:49:56 +00:00
dialog box in quotation marks, followed by the filter string itself:
"HTTP" port 80
"DCERPC" port 135
2005-06-04 04:14:02 +00:00
2008-02-15 22:36:24 +00:00
The global F<cfilters> file uses the same directory as the
2005-06-09 08:03:34 +00:00
global preferences file.
2008-02-15 22:36:24 +00:00
The personal F<cfilters> file uses the same directory as the personal
2011-09-23 04:33:07 +00:00
preferences file. It is written through the Capture:Capture Filters
2005-07-19 20:44:45 +00:00
dialog.
If the global F<cfilters> file exists, it is used only if the personal
F<cfilters> file does not exist; global and personal capture filters are
not merged.
2005-06-04 04:14:02 +00:00
=item Display Filters
2008-02-15 22:36:24 +00:00
The F<dfilters> files contain system-wide and personal display filters.
Each line contains one filter, starting with the string displayed in the
2005-06-09 19:49:56 +00:00
dialog box in quotation marks, followed by the filter string itself:
"HTTP" http
"DCERPC" dcerpc
2005-06-04 04:14:02 +00:00
2008-02-15 22:36:24 +00:00
The global F<dfilters> file uses the same directory as the
2005-06-09 08:03:34 +00:00
global preferences file.
2008-02-15 22:36:24 +00:00
The personal F<dfilters> file uses the same directory as the
2011-09-23 04:33:07 +00:00
personal preferences file. It is written through the Analyze:Display
2005-07-19 20:44:45 +00:00
Filters dialog.
If the global F<dfilters> file exists, it is used only if the personal
F<dfilters> file does not exist; global and personal display filters are
not merged.
2005-06-04 04:14:02 +00:00
=item Color Filters (Coloring Rules)
The F<colorfilters> files contain system-wide and personal color filters.
2005-06-09 19:49:56 +00:00
Each line contains one filter, starting with the string displayed in the
2011-09-23 04:33:07 +00:00
dialog box, followed by the corresponding display filter. Then the
2005-06-09 19:49:56 +00:00
background and foreground colors are appended:
# a comment
@tcp@tcp@[59345,58980,65534][0,0,0]
@udp@udp@[28834,57427,65533][0,0,0]
2005-06-04 04:14:02 +00:00
2008-02-15 22:36:24 +00:00
The global F<colorfilters> file uses the same directory as the
2005-06-09 08:03:34 +00:00
global preferences file.
2005-06-04 04:14:02 +00:00
2008-02-15 22:36:24 +00:00
The personal F<colorfilters> file uses the same directory as the
2011-09-23 04:33:07 +00:00
personal preferences file. It is written through the View:Coloring Rules
2005-07-19 20:44:45 +00:00
dialog.
If the global F<colorfilters> file exists, it is used only if the personal
F<colorfilters> file does not exist; global and personal color filters are
not merged.
=item Plugins
See above in the description of the About:Plugins page.
2005-06-04 04:14:02 +00:00
=back
2003-08-27 22:55:51 +00:00
2009-10-20 20:14:23 +00:00
=head1 ENVIRONMENT VARIABLES
=over 4
2019-07-29 00:17:04 +00:00
=item WIRESHARK_CONFIG_DIR
2013-09-13 20:15:46 +00:00
2019-07-29 00:17:04 +00:00
This environment variable overrides the location of personal configuration
files. It defaults to F<$XDG_CONFIG_HOME/wireshark> (or F<$HOME/.wireshark> if
the former is missing while the latter exists). On Windows,
F<%APPDATA%\Wireshark> is used instead. Available since Wireshark 3.0.
2013-09-13 20:15:46 +00:00
2013-03-11 19:17:26 +00:00
=item WIRESHARK_DEBUG_WMEM_OVERRIDE
Setting this environment variable forces the wmem framework to use the
specified allocator backend for *all* allocations, regardless of which
backend is normally specified by the code. This is mainly useful to developers
when testing or debugging. See I<README.wmem> in the source distribution for
details.
2010-02-24 05:13:27 +00:00
=item WIRESHARK_RUN_FROM_BUILD_DIRECTORY
This environment variable causes the plugins and other data files to be loaded
from the build directory (where the program was compiled) rather than from the
standard locations. It has no effect when the program in question is running
with root (or setuid) permissions on *NIX.
=item WIRESHARK_DATA_DIR
This environment variable causes the various data files to be loaded from
a directory other than the standard locations. It has no effect when the
program in question is running with root (or setuid) permissions on *NIX.
=item ERF_RECORDS_TO_CHECK
This environment variable controls the number of ERF records checked when
deciding if a file really is in the ERF format. Setting this environment
variable a number higher than the default (20) would make false positives
less likely.
2010-10-20 18:00:25 +00:00
=item IPFIX_RECORDS_TO_CHECK
This environment variable controls the number of IPFIX records checked when
deciding if a file really is in the IPFIX format. Setting this environment
variable a number higher than the default (20) would make false positives
less likely.
2010-04-13 22:08:56 +00:00
=item WIRESHARK_ABORT_ON_DISSECTOR_BUG
2010-04-14 00:46:29 +00:00
If this environment variable is set, B<Wireshark> will call abort(3)
when a dissector bug is encountered. abort(3) will cause the program to
exit abnormally; if you are running B<Wireshark> in a debugger, it
should halt in the debugger and allow inspection of the process, and, if
you are not running it in a debugger, it will, on some OSes, assuming
2010-05-27 19:11:53 +00:00
your environment is configured correctly, generate a core dump file.
2010-04-14 00:46:29 +00:00
This can be useful to developers attempting to troubleshoot a problem
with a protocol dissector.
2010-04-13 22:08:56 +00:00
2013-06-05 14:08:40 +00:00
=item WIRESHARK_ABORT_ON_TOO_MANY_ITEMS
If this environment variable is set, B<Wireshark> will call abort(3)
if a dissector tries to add too many items to a tree (generally this
is an indication of the dissector not breaking out of a loop soon enough).
abort(3) will cause the program to exit abnormally; if you are running
B<Wireshark> in a debugger, it should halt in the debugger and allow
inspection of the process, and, if you are not running it in a debugger,
it will, on some OSes, assuming your environment is configured correctly,
generate a core dump file. This can be useful to developers attempting to
troubleshoot a problem with a protocol dissector.
2011-08-29 23:16:57 +00:00
=item WIRESHARK_QUIT_AFTER_CAPTURE
2011-08-29 23:25:29 +00:00
Cause B<Wireshark> to exit after the end of the capture session. This
doesn't automatically start a capture; you must still use B<-k> to do
that. You must also specify an autostop condition, e.g. B<-c> or B<-a
duration:...>. This means that you will not be able to see the results
of the capture after it stops; it's primarily useful for testing.
2011-08-29 23:16:57 +00:00
2021-06-15 21:50:46 +00:00
=item WIRESHARK_LOG_LEVEL
This environment variable controls the verbosity of diagnostic messages to
the console. From less verbose to most verbose levels can be C<critical>,
2021-06-21 21:39:54 +00:00
C<warning>, C<message>, C<info>, C<debug> or C<noisy>. Levels above the
current level are also active. Levels C<critical> and C<error> are always
active.
=item WIRESHARK_LOG_FATAL
Sets the fatal log level. Fatal log levels cause the progeam to abort.
The fatal log level be set to C<critical> or C<warning>. C<Error> is
always fatal.
2021-06-15 21:50:46 +00:00
=item WIRESHARK_LOG_DOMAINS
2021-06-21 21:39:54 +00:00
This environment variable selects which log domains are active. The filter is
2021-06-15 21:50:46 +00:00
given as a case-insensitive comma separated list. If set only the included
domains will be enabled. The default domain is always considered to be enabled.
Domain filter lists can be preceded by '!' to invert the sense of the match.
=item WIRESHARK_LOG_DEBUG
2021-06-21 21:39:54 +00:00
List of domains with C<debug> log level. This sets the level of the provided
log domains and takes precedence over the active domains filter. If preceded
by '!' this disables the C<debug> level instead.
=item WIRESHARK_LOG_NOISY
Same as above but for C<noisy> log level instead.
2021-06-15 21:50:46 +00:00
2009-10-20 20:14:23 +00:00
=back
2021-06-18 01:02:26 +00:00
=head1 AUTHORS
Wireshark would not be the powerful, featureful application it is without the generous contributions of hundreds of developers.
A complete list of authors can be found in the AUTHORS file in Wireshark's source code repository and at L<https://www.wireshark.org/about.html#authors>.
1998-09-16 02:39:15 +00:00
=head1 SEE ALSO
2012-02-03 09:07:24 +00:00
wireshark-filter(4), tshark(1), editcap(1), pcap(3), dumpcap(1), mergecap(1),
2013-05-20 02:21:07 +00:00
text2pcap(1), pcap-filter(7) or tcpdump(8)
1998-09-16 02:39:15 +00:00
=head1 NOTES
2006-05-31 19:12:15 +00:00
The latest version of B<Wireshark> can be found at
2014-09-17 00:08:53 +00:00
L<https://www.wireshark.org>.
2006-07-09 22:45:48 +00:00
HTML versions of the Wireshark project man pages are available at:
2014-09-17 00:08:53 +00:00
L<https://www.wireshark.org/docs/man-pages>.