'\" t .\" Title: wireshark .\" Author: [see the "AUTHOR(S)" section] .\" Generator: Asciidoctor 2.0.20 .\" Date: 2023-10-05 .\" Manual: \ \& .\" Source: \ \& .\" Language: English .\" .TH "WIRESHARK" "1" "2023-10-05" "\ \&" "\ \&" .ie \n(.g .ds Aq \(aq .el .ds Aq ' .ss \n[.ss] 0 .nh .ad l .de URL \fI\\$2\fP <\\$1>\\$3 .. .als MTO URL .if \n[.g] \{\ . mso www.tmac . am URL . ad l . . . am MTO . ad l . . . LINKSTYLE blue R < > .\} .SH "NAME" wireshark \- Interactively dump and analyze network traffic .SH "SYNOPSIS" .sp \fBwireshark\fP [\~\fB\-i\fP\~|\-\~] [\~\fB\-f\fP\~\~] [\~\fB\-Y\fP\~\~] [\~\fB\-w\fP\~\~] [\~\fBoptions\fP\~] [\~\~] .SH "DESCRIPTION" .sp \fBWireshark\fP is a GUI network protocol analyzer. It lets you interactively browse packet data from a live network or from a previously saved capture file. \fBWireshark\fP\*(Aqs native capture file formats are \fBpcapng\fP format and \fBpcap\fP format; it can read and write both formats.. \fBpcap\fP format is also the format used by \fBtcpdump\fP and various other tools; \fBtcpdump\fP, when using newer verions of the \fBlibpcap\fP library, can also read some pcapng files, and, on newer versions of macOS, can read all pcapng files and can write them as well. .sp \fBWireshark\fP can also read / import the following file formats: .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Oracle (previously Sun) \fBsnoop\fP and \fBatmsnoop\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Finisar (previously Shomiti) \fBSurveyor\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Microsoft \fBNetwork Monitor\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Novell \fBLANalyzer\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} AIX\(cqs \fBiptrace\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Cinco Networks \fBNetXRay\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} NETSCOUT (previously Network Associates/Network General) Windows\-based \fBSniffer\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Network General/Network Associates DOS\-based \fBSniffer\fP captures (compressed or uncompressed) .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} LiveAction (previously WildPackets/Savvius) \fB*Peek\fP/\fBEtherHelp\fP/\fBPacketGrabber\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} \fBRADCOM\fP\*(Aqs WAN/LAN analyzer captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Viavi (previously Network Instruments) \fBObserver\fP captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} \fBLucent/Ascend\fP router debug output .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} captures from HP\-UX \fBnettl\fP .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} \fBToshiba\(cqs\fP ISDN routers dump output .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} the output from \fBi4btrace\fP from the ISDN4BSD project .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} traces from the \fBEyeSDN\fP USB S0 .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} the \fBIPLog\fP format output from the Cisco Secure Intrusion Detection System .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} \fBpppd logs\fP (pppdump format) .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} the output from VMS\(cqs \fBTCPIPtrace\fP/\fBTCPtrace\fP/\fBUCX$TRACE\fP utilities .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} the text output from the \fBDBS Etherwatch\fP VMS utility .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Visual Networks\*(Aq \fBVisual UpTime\fP traffic capture .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} the output from \fBCoSine\fP L2 debug .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} the output from InfoVista (previously Accellent) \fB5View\fP LAN agents .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Endace Measurement Systems\*(Aq ERF format captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Linux Bluez Bluetooth stack \fBhcidump \-w\fP traces .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Catapult DCT2000 .out files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Gammu generated text output from Nokia DCT3 phones in Netmonitor mode .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} IBM Series (OS/400) Comm traces (ASCII & UNICODE) .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Juniper Netscreen snoop files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Symbian OS btsnoop files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} TamoSoft CommView files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Tektronix K12xx 32bit .rf5 format files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Tektronix K12 text file format captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Apple PacketLogger files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Captures from Aethra Telecommunications\*(Aq PC108 software for their test instruments .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Citrix NetScaler Trace files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Android Logcat binary and text format logs .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Colasoft Capsa and PacketBuilder captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Micropross mplog files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Unigraf DPA\-400 DisplayPort AUX channel monitor traces .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} 802.15.4 traces from Daintree\(cqs Sensor Network Analyzer .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} MPEG\-2 Transport Streams as defined in ISO/IEC 13818\-1 .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Log files from the \fIcandump\fP utility .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Logs from the BUSMASTER tool .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Ixia IxVeriWave raw captures .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} Rabbit Labs CAM Inspector files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} \fIsystemd\fP journal files .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} 3GPP TS 32.423 trace files .RE .sp There is no need to tell \fBWireshark\fP what type of file you are reading; it will determine the file type by itself. \fBWireshark\fP is also capable of reading any of these file formats if they are compressed using gzip. \fBWireshark\fP recognizes this directly from the file; the \*(Aq.gz\*(Aq extension is not required for this purpose. .sp Like other protocol analyzers, \fBWireshark\fP\*(Aqs main window shows 3 views of a packet. It shows a summary line, briefly describing what the 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. .sp In addition, \fBWireshark\fP has some features that make it unique. It can assemble all the packets in a TCP conversation and show you the ASCII (or EBCDIC, or hex) data in that conversation. Display filters in \fBWireshark\fP are very powerful; more fields are filterable in \fBWireshark\fP than in other protocol analyzers, and the syntax you can use to create your filters is richer. As \fBWireshark\fP progresses, expect more and more protocol fields to be allowed in display filters. .sp 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. .sp Compressed file support uses (and therefore requires) the zlib library. If the zlib library is not present, \fBWireshark\fP will compile, but will be unable to read compressed files. .sp The pathname of a capture file to be read can be specified with the \fB\-r\fP option or can be specified as a command\-line argument. .SH "OPTIONS" .sp Most users will want to start \fBWireshark\fP without options and configure it from the menus instead. Those users may just skip this section. .sp \-a|\-\-autostop .RS 4 .sp Specify a criterion that specifies when \fBWireshark\fP is to stop writing to a capture file. The criterion is of the form \fItest:value\fP, where \fItest\fP is one of: .sp \fBduration\fP:\fIvalue\fP Stop writing to a capture file after \fIvalue\fP seconds have elapsed. Floating point values (e.g. 0.5) are allowed. .sp \fBfiles\fP:\fIvalue\fP Stop writing to capture files after \fIvalue\fP number of files were written. .sp \fBfilesize\fP:\fIvalue\fP Stop writing to a capture file after it reaches a size of \fIvalue\fP kB. If this option is used together with the \-b option, Wireshark 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. .sp \fBpackets\fP:\fIvalue\fP Stop writing to a capture file after it contains \fIvalue\fP packets. Acts the same as \fB\-c\fP. .RE .sp \-b|\-\-ring\-buffer .RS 4 .sp Cause \fBWireshark\fP to run in "multiple files" mode. In "multiple files" mode, \fBWireshark\fP will write to several capture files. When the first capture file fills up, \fBWireshark\fP will switch writing to the next file and so on. .sp The created filenames are based on the filename given with the \fB\-w\fP flag, the number of the file and on the creation date and time, e.g. outfile_00001_20230714120117.pcap, outfile_00002_20230714120523.pcap, ... .sp With the \fIfiles\fP option it\(cqs also possible to form a "ring buffer". This will fill up new files until the number of files specified, at which point \fBWireshark\fP will discard the data in the first file and start writing to that file and so on. If the \fIfiles\fP option is not set, new files filled up until one of the capture stop conditions match (or until the disk is full). .sp The criterion is of the form \fIkey:value\fP, where \fIkey\fP is one of: .sp \fBduration\fP:\fIvalue\fP switch to the next file after \fIvalue\fP seconds have elapsed, even if the current file is not completely filled up. Floating point values (e.g. 0.5) are allowed. .sp \fBfiles\fP:\fIvalue\fP begin again with the first file after \fIvalue\fP number of 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 \fBfiles\fP criterion requires one of the other criteria to be specified to control when to go to the next file. It should be noted that each \fB\-b\fP parameter takes exactly one criterion; to specify two criteria, each must be preceded by the \fB\-b\fP option. .sp \fBfilesize\fP:\fIvalue\fP switch to the next file after it reaches a size of \fIvalue\fP kB. Note that the filesize is limited to a maximum value of 2 GiB. .sp \fBinterval\fP:\fIvalue\fP switch to the next file when the time is an exact multiple of \fIvalue\fP seconds. .sp \fBpackets\fP:\fIvalue\fP switch to the next file after it contains \fIvalue\fP packets. .sp Example: \fB\-b filesize:1000 \-b files:5\fP results in a ring buffer of five files of size one megabyte each. .RE .sp \-B|\-\-buffer\-size .RS 4 .sp Set capture buffer size (in MiB, default is 2 MiB). This is used by 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 this size. Note that, while \fBWireshark\fP attempts to set the buffer size to 2 MiB by default, and can be told to set it to a larger value, the system or interface on which you\(cqre capturing might silently limit the capture buffer size to a lower value or raise it to a higher value. .sp This is available on UNIX systems with libpcap 1.0.0 or later and on Windows. It is not available on UNIX systems with earlier versions of libpcap. .sp This option can occur multiple times. If used before the first occurrence of the \fB\-i\fP option, it sets the default capture buffer size. If used after an \fB\-i\fP option, it sets the capture buffer size for the interface specified by the last \fB\-i\fP option occurring before this option. If the capture buffer size is not set specifically, the default capture buffer size is used instead. .RE .sp \-c .RS 4 .sp Set the maximum number of packets to read when capturing live data. Acts the same as \fB\-a packets:\fP. .RE .sp \-C .RS 4 .sp Start with the given configuration profile. .RE .sp \-\-capture\-comment .RS 4 .sp When performing a capture file from the command line, with the \fB\-k\fP flag, add a capture comment to the output file, if supported by the capture format. .sp This option may be specified multiple times. Note that Wireshark currently only displays the first comment of a capture file. .RE .sp \-d ==, .RS 4 .sp Like Wireshark\(cqs \fBDecode As...\fP feature, this lets you specify how a layer type should be dissected. If the layer type in question (for example, \fBtcp.port\fP or \fBudp.port\fP for a TCP or UDP port number) has the specified selector value, packets should be dissected as the specified protocol. .sp Example: \fB\-d tcp.port==8888,http\fP will decode any traffic running over TCP port 8888 as HTTP. .sp See the tshark(1) manual page for more examples. .RE .sp \-D|\-\-list\-interfaces .RS 4 .sp Print a list of the interfaces on which \fBWireshark\fP can capture, and 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 \fB\-i\fP flag to specify an interface on which to capture. .sp This can be useful on systems that don\(cqt have a command to list them (UNIX systems lacking \fBifconfig \-a\fP or Linux systems lacking \fBip link show\fP). The number can be useful on Windows systems, where the interface name might be a long name or a GUID. .sp Note that "can capture" means that \fBWireshark\fP was able to open 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 example, as root), then, if \fBWireshark\fP is run with the \fB\-D\fP flag and is not run from such an account, it will not list any interfaces. .RE .sp \-\-display .RS 4 .sp 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. .RE .sp \-\-disable\-protocol .RS 4 .sp Disable dissection of proto_name. .RE .sp \-\-disable\-heuristic .RS 4 .sp Disable dissection of heuristic protocol. .RE .sp \-\-enable\-protocol .RS 4 .sp Enable dissection of proto_name. .RE .sp \-\-enable\-heuristic .RS 4 .sp Enable dissection of heuristic protocol. .RE .sp \-f .RS 4 .sp Set the capture filter expression. .sp This option can occur multiple times. If used before the first occurrence of the \fB\-i\fP option, it sets the default capture filter expression. If used after an \fB\-i\fP option, it sets the capture filter expression for the interface specified by the last \fB\-i\fP option occurring before this option. If the capture filter expression is not set specifically, the default capture filter expression is used if provided. .sp 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: \fB\-f "predef:MyPredefinedHostOnlyFilter"\fP .RE .sp \-\-fullscreen .RS 4 .sp 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). .RE .sp \-g .RS 4 .sp After reading in a capture file using the \fB\-r\fP flag, go to the given \fIpacket number\fP. .RE .sp \-h|\-\-help .RS 4 .sp Print the version number and options and exit. .RE .sp \-H .RS 4 .sp Hide the capture info dialog during live packet capture. .RE .sp \-i|\-\-interface |\- .RS 4 .sp Set the name of the network interface or pipe to use for live packet capture. .sp Network interface names should match one of the names listed in "\fBwireshark \-D\fP" (described above); a number, as reported by "\fBwireshark \-D\fP", can also be used. If you\(cqre using UNIX, "\fBnetstat \-i\fP", "\fBifconfig \-a\fP" or "\fBip link\fP" might also work to list interface names, although not all versions of UNIX support the \fB\-a\fP option to \fBifconfig\fP. .sp If no interface is specified, \fBWireshark\fP searches the list of interfaces, choosing the first non\-loopback interface if there are any non\-loopback interfaces, and choosing the first loopback interface if there are no non\-loopback interfaces. If there are no interfaces at all, \fBWireshark\fP reports an error and doesn\(cqt start the capture. .sp Pipe names should be either the name of a FIFO (named pipe) or "\-" to read data from the standard input. On Windows systems, pipe names must be of the form "\(rs\(rs.\(rspipe\(rs\fBpipename\fP". Data read from pipes must be in standard pcapng or pcap format. Pcapng data must have the same endianness as the capturing host. .sp "TCP@:" causes \fBWireshark\fP to attempt to connect to the specified port on the specified host and read pcapng or pcap data. .sp This option can occur multiple times. When capturing from multiple interfaces, the capture file will be saved in pcapng format. .RE .sp \-I|\-\-monitor\-mode .RS 4 .sp Put the interface in "monitor mode"; this is supported only on IEEE 802.11 Wi\-Fi interfaces, and supported only on some operating systems. .sp Note that in monitor mode the adapter might disassociate from the network with which it\(cqs 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. .sp This option can occur multiple times. If used before the first occurrence of the \fB\-i\fP option, it enables the monitor mode for all interfaces. If used after an \fB\-i\fP option, it enables the monitor mode for the interface specified by the last \fB\-i\fP option occurring before this option. .RE .sp \-j .RS 4 .sp Use after \fB\-J\fP to change the behavior when no exact match is found for the filter. With this option select the first packet before. .RE .sp \-J .RS 4 .sp After reading in a capture file using the \fB\-r\fP flag, jump to the packet matching the filter (display filter syntax). If no exact match is found the first packet after that is selected. .RE .sp \-k .RS 4 .sp Start the capture session immediately. If the \fB\-i\fP flag was specified, the capture uses the specified interface. Otherwise, \fBWireshark\fP searches the list of interfaces, choosing the first non\-loopback interface if there are any non\-loopback interfaces, and choosing the first loopback interface if there are no non\-loopback interfaces; if there are no interfaces, \fBWireshark\fP reports an error and doesn\(cqt start the capture. .RE .sp \-K .RS 4 .sp Load kerberos crypto keys from the specified keytab file. This option can be used multiple times to load keys from several files. .sp Example: \fB\-K krb5.keytab\fP .RE .sp \-l .RS 4 .sp Turn on automatic scrolling if the packet display is being updated automatically as packets arrive during a capture (as specified by the \fB\-S\fP flag). .RE .sp \-L|\-\-list\-data\-link\-types .RS 4 .sp List the data link types supported by the interface and exit. .RE .sp \-\-list\-time\-stamp\-types .RS 4 .sp List time stamp types supported for the interface. If no time stamp type can be set, no time stamp types are listed. .RE .sp \-n .RS 4 .sp Disable network object name resolution (such as hostname, TCP and UDP port names), the \fB\-N\fP flag might override this one. .RE .sp \-N .RS 4 .sp Turn on name resolving only for particular types of addresses and port numbers, with name resolving for other types of addresses and port numbers turned off. This flag overrides \fB\-n\fP if both \fB\-N\fP and \fB\-n\fP are present. If both \fB\-N\fP and \fB\-n\fP flags are not present, all name resolutions are turned on. .sp The argument is a string that may contain the letters: .sp \fBm\fP to enable MAC address resolution .sp \fBn\fP to enable network address resolution .sp \fBN\fP to enable using external resolvers (e.g., DNS) for network address resolution .sp \fBt\fP to enable transport\-layer port number resolution .sp \fBd\fP to enable resolution from captured DNS packets .sp \fBv\fP to enable VLAN IDs to names resolution .RE .sp \-o .RS 4 .sp Set a preference or recent value, overriding the default value and any value read from a preference/recent file. The argument to the flag is a string of the form \fIprefname:value\fP, where \fIprefname\fP is the name of the preference/recent value (which is the same name that would appear in the preference/recent file), and \fIvalue\fP is the value to which it should be set. Since \fBEthereal\fP 0.10.12, the recent settings replaces the formerly used \-B, \-P and \-T flags to manipulate the GUI dimensions. .sp If \fIprefname\fP is "uat", you can override settings in various user access tables using the form "uat:\fIuat filename\fP:\fIuat record\fP". \fIuat filename\fP must be the name of a UAT file, e.g. \fIuser_dlts\fP. \fIuat_record\fP must be in the form of a valid record for that file, including quotes. For instance, to specify a user DLT from the command line, you would use .sp .if n .RS 4 .nf .fam C \-o "uat:user_dlts:\(rs"User 0 (DLT=147)\(rs",\(rs"cops\(rs",\(rs"0\(rs",\(rs"\(rs",\(rs"0\(rs",\(rs"\(rs"" .fam .fi .if n .RE .RE .sp \-p|\-\-no\-promiscuous\-mode .RS 4 .sp \fIDon\(cqt\fP put the interface into promiscuous mode. Note that the interface might be in promiscuous mode for some other reason; hence, \fB\-p\fP cannot be used to ensure that the only traffic that is captured is traffic sent to or from the machine on which \fBWireshark\fP is running, broadcast traffic, and multicast traffic to addresses received by that machine. .sp This option can occur multiple times. If used before the first occurrence of the \fB\-i\fP option, no interface will be put into the promiscuous mode. If used after an \fB\-i\fP option, the interface specified by the last \fB\-i\fP option occurring before this option will not be put into the promiscuous mode. .RE .sp \-P .RS 4 .sp Special path settings usually detected automatically. This is used for special cases, e.g. starting Wireshark from a known location on an USB stick. .sp The criterion is of the form \fIkey:path\fP, where \fIkey\fP is one of: .sp \fBpersconf\fP:\fIpath\fP path of personal configuration files, like the preferences files. .sp \fBpersdata\fP:\fIpath\fP path of personal data files, it\(cqs the folder initially opened. After the very first initialization, the recent file will keep the folder last used. .RE .sp \-r|\-\-read\-file .RS 4 .sp Read packet data from \fIinfile\fP, can be any supported capture file format (including gzipped files). It\(cqs not possible to use named pipes or stdin here! To capture from a pipe or from stdin use \fB\-i \-\fP .RE .sp \-R|\-\-read\-filter .RS 4 .sp When reading a capture file specified with the \fB\-r\fP 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. .RE .sp \-s|\-\-snapshot\-length .RS 4 .sp Set the default snapshot length to use when capturing live data. No more than \fIsnaplen\fP bytes of each network packet will be read into memory, or saved to disk. A value of 0 specifies a snapshot length of 262144, so that the full packet is captured; this is the default. .sp This option can occur multiple times. If used before the first occurrence of the \fB\-i\fP option, it sets the default snapshot length. If used after an \fB\-i\fP option, it sets the snapshot length for the interface specified by the last \fB\-i\fP option occurring before this option. If the snapshot length is not set specifically, the default snapshot length is used if provided. .RE .sp \-S .RS 4 .sp Automatically update the packet display as packets are coming in. .RE .sp \-t a|ad|adoy|d|dd|e|r|u|ud|udoy .RS 4 .sp Set the format of the packet timestamp displayed in the packet list window. The format can be one of: .sp \fBa\fP absolute: The absolute time, as local time in your time zone, is the actual time the packet was captured, with no date displayed .sp \fBad\fP 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 .sp \fBadoy\fP 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 .sp \fBd\fP delta: The delta time is the time since the previous packet was captured .sp \fBdd\fP delta_displayed: The delta_displayed time is the time since the previous displayed packet was captured .sp \fBe\fP epoch: The time in seconds since epoch (Jan 1, 1970 00:00:00) .sp \fBr\fP relative: The relative time is the time elapsed between the first packet and the current packet .sp \fBu\fP UTC: The absolute time, as UTC, is the actual time the packet was captured, with no date displayed .sp \fBud\fP 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 .sp \fBudoy\fP 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 .sp The default format is relative. .RE .sp \-\-temp\-dir .RS 4 .sp Specifies the directory into which temporary files (including capture files) are to be written. The default behaviour is to use your system\(cqs temporary directory (typically \fI/tmp\fP on Linux, and \fIC:\(rs\(rsTemp\fP on Windows). .RE .sp \-\-time\-stamp\-type .RS 4 .sp Change the interface\(cqs timestamp method. See \-\-list\-time\-stamp\-types. .RE .sp \-u .RS 4 .sp Output format of seconds (def: s: seconds) .RE .sp \-v|\-\-version .RS 4 .sp Print the full version information and exit. .RE .sp \-w .RS 4 .sp Set the default capture file name, or \*(Aq\-\*(Aq for standard output. .RE .sp \-X .RS 4 .sp Specify an option to be passed to an \fBWireshark\fP module. The eXtension option is in the form \fIextension_key:value\fP, where \fIextension_key\fP can be: .sp \fBlua_script\fP:\fIlua_script_filename\fP tells \fBWireshark\fP to load the given script in addition to the default Lua scripts. .sp \fBlua_script\fP\fInum\fP:\fIargument\fP tells \fBWireshark\fP to pass the given argument to the lua script identified by \*(Aqnum\*(Aq, which is the number indexed order of the \*(Aqlua_script\*(Aq command. For example, if only one script was loaded with \*(Aq\-X lua_script:my.lua\*(Aq, then \*(Aq\-X lua_script1:foo\*(Aq will pass the string \*(Aqfoo\*(Aq to the \*(Aqmy.lua\*(Aq script. If two scripts were loaded, such as \*(Aq\-X lua_script:my.lua\*(Aq and \*(Aq\-X lua_script:other.lua\*(Aq in that order, then a \*(Aq\-X lua_script2:bar\*(Aq would pass the string \*(Aqbar\*(Aq to the second lua script, namely \*(Aqother.lua\*(Aq. .sp \fBread_format\fP:\fIfile_format\fP tells \fBWireshark\fP to use the given file format to read in the file (the file given in the \fB\-r\fP command option). .sp \fBstdin_descr\fP:\fIdescription\fP tells \fBWireshark\fP to use the given description when capturing from standard input (\fB\-i \-\fP). .RE .sp \-y|\-\-linktype .RS 4 .sp If a capture is started from the command line with \fB\-k\fP, set the data link type to use while capturing packets. The values reported by \fB\-L\fP are the values that can be used. .sp This option can occur multiple times. If used before the first occurrence of the \fB\-i\fP option, it sets the default capture link type. If used after an \fB\-i\fP option, it sets the capture link type for the interface specified by the last \fB\-i\fP option occurring before this option. If the capture link type is not set specifically, the default capture link type is used if provided. .RE .sp \-Y|\-\-display\-filter .RS 4 .sp Start with the given display filter. .RE .sp \-z .RS 4 .sp Get \fBWireshark\fP to collect various types of statistics and display the result in a window that updates in semi\-real time. .sp Some of the currently implemented statistics are: .RE .sp \fB\-z help\fP .RS 4 .sp Display all possible values for \fB\-z\fP. .RE .sp \fB\-z\fP afp,srt[,\fIfilter\fP] .RS 4 .sp Show Apple Filing Protocol service response time statistics. .RE .sp \fB\-z\fP conv,\fItype\fP[,\fIfilter\fP] .RS 4 .sp Create a table that lists all conversations that could be seen in the capture. \fItype\fP specifies the conversation endpoint types for which we want to generate the statistics; currently the supported ones are: .sp .if n .RS 4 .nf .fam C "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 .fam .fi .if n .RE .sp If the optional \fIfilter\fP is specified, only those packets that match the filter will be used in the calculations. .sp 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. .sp These tables can also be generated at runtime by selecting the appropriate conversation type from the menu "Tools/Statistics/Conversation List/". .RE .sp \fB\-z\fP dcerpc,srt,\fIname\-or\-uuid\fP,\fImajor\fP.\fIminor\fP[,\fIfilter\fP] .RS 4 .sp Collect call/reply SRT (Service Response Time) data for DCERPC interface \fIname\fP or \fIuuid\fP, version \fImajor\fP.\fIminor\fP. Data collected is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT. Interface \fIname\fP and \fIuuid\fP are case\-insensitive. .sp Example: \fB\-z dcerpc,srt,12345778\-1234\-abcd\-ef00\-0123456789ac,1.0\fP will collect data for the CIFS SAMR Interface. .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z dcerpc,srt,12345778\-1234\-abcd\-ef00\-0123456789ac,1.0,ip.addr==1.2.3.4\fP will collect SAMR SRT statistics for a specific host. .RE .sp \fB\-z\fP dhcp,stat[,\fIfilter\fP] .RS 4 .sp Show DHCP (BOOTP) statistics. .RE .sp \fB\-z\fP expert .RS 4 .sp Show expert information. .RE .sp \fB\-z\fP fc,srt[,\fIfilter\fP] .RS 4 .sp 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. .sp Example: \fB\-z fc,srt\fP will calculate the Service Response Time as the time delta between the First packet of the exchange and the Last packet of the exchange. .sp 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. .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z "fc,srt,fc.id==01.02.03"\fP will collect stats only for FC packets exchanged by the host at FC address 01.02.03 . .RE .sp \fB\-z\fP h225,counter[\fI,filter\fP] .RS 4 .sp 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. .sp Example: \fB\-z h225,counter\fP .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z "h225,counter,ip.addr==1.2.3.4"\fP will collect stats only for H.225 packets exchanged by the host at IP address 1.2.3.4 . .RE .sp \fB\-z\fP h225,srt[\fI,filter\fP] .RS 4 .sp 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. .sp Example: \fB\-z h225,srt\fP .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z "h225,srt,ip.addr==1.2.3.4"\fP will collect stats only for ITU\-T H.225 RAS packets exchanged by the host at IP address 1.2.3.4 . .RE .sp \fB\-z\fP io,stat .RS 4 .sp 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. .sp This option can be used multiple times on the command line. .sp This graph window can also be opened from the Analyze:Statistics:Traffic:IO\-Stat menu item. .RE .sp \fB\-z\fP ldap,srt[,\fIfilter\fP] .RS 4 .sp Collect call/reply SRT (Service Response Time) data for LDAP. Data collected is the number of calls for each implemented LDAP command, MinSRT, MaxSRT and AvgSRT. .sp Example: \fB\-z ldap,srt\fP will calculate the Service Response Time as the time delta between the Request and the Response. .sp 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. .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: use \fB\-z "ldap,srt,ip.addr==10.1.1.1"\fP will collect stats only for LDAP packets exchanged by the host at IP address 10.1.1.1 . .sp The only LDAP commands that are currently implemented and for which the stats will be available are: BIND SEARCH MODIFY ADD DELETE MODRDN COMPARE EXTENDED .RE .sp \fB\-z\fP megaco,srt[\fI,filter\fP] .RS 4 .sp Collect request/response SRT (Service Response Time) data for MEGACO. (This is similar to \fB\-z smb,srt\fP). Data collected is the number of calls for each known MEGACO Command, Minimum SRT, Maximum SRT and Average SRT. .sp Example: \fB\-z megaco,srt\fP .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z "megaco,srt,ip.addr==1.2.3.4"\fP will collect stats only for MEGACO packets exchanged by the host at IP address 1.2.3.4 . .RE .sp \fB\-z\fP mgcp,srt[\fI,filter\fP] .RS 4 .sp Collect request/response SRT (Service Response Time) data for MGCP. (This is similar to \fB\-z smb,srt\fP). Data collected is the number of calls for each known MGCP Type, Minimum SRT, Maximum SRT and Average SRT. .sp Example: \fB\-z mgcp,srt\fP .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z "mgcp,srt,ip.addr==1.2.3.4"\fP will collect stats only for MGCP packets exchanged by the host at IP address 1.2.3.4 . .RE .sp \fB\-z\fP mtp3,msus[,] .RS 4 .sp Show MTP3 MSU statistics. .RE .sp \fB\-z\fP multicast,stat[,] .RS 4 .sp Show UDP multicast stream statistics. .RE .sp \fB\-z\fP rpc,programs .RS 4 .sp 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. .RE .sp \fB\-z\fP rpc,srt,\fIname\-or\-number\fP,\fIversion\fP[,] .RS 4 .sp Collect call/reply SRT (Service Response Time) data for program \fIname\fP/\fIversion\fP or \fInumber\fP/\fIversion\fP. Data collected is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT. Program \fIname\fP is case\-insensitive. .sp Example: \fB\-z rpc,srt,100003,3\fP will collect data for NFS v3. .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z rpc,srt,nfs,3,nfs.fh.hash==0x12345678\fP will collect NFS v3 SRT statistics for a specific file. .RE .sp \fB\-z\fP scsi,srt,\fIcmdset\fP[,] .RS 4 .sp Collect call/reply SRT (Service Response Time) data for SCSI commandset . .sp Commandsets are 0:SBC 1:SSC 5:MMC .sp Data collected is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT. .sp Example: \fB\-z scsi,srt,0\fP will collect data for SCSI BLOCK COMMANDS (SBC). .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z scsi,srt,0,ip.addr==1.2.3.4\fP will collect SCSI SBC SRT statistics for a specific iscsi/ifcp/fcip host. .RE .sp \fB\-z\fP sip,stat[\fI,filter\fP] .RS 4 .sp 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 also get the number of resent SIP Messages (only for SIP over UDP). .sp Example: \fB\-z sip,stat\fP .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z "sip,stat,ip.addr==1.2.3.4"\fP will collect stats only for SIP packets exchanged by the host at IP address 1.2.3.4 . .RE .sp \fB\-z\fP smb,srt[,\fIfilter\fP] .RS 4 .sp 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. .sp Example: \fB\-z smb,srt\fP .sp 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. .sp This option can be used multiple times on the command line. .sp If the optional \fIfilter\fP is provided, the stats will only be calculated on those calls that match that filter. .sp Example: \fB\-z "smb,srt,ip.addr==1.2.3.4"\fP will collect stats only for SMB packets exchanged by the host at IP address 1.2.3.4 . .RE .sp \fB\-z\fP voip,calls .RS 4 .sp 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. .sp Example: \fB\-z voip,calls\fP .RE .sp \fB\-z\fP wlan,stat[,] .RS 4 .sp Show IEEE 802.11 network and station statistics. .RE .sp \fB\-z\fP wsp,stat[,] .RS 4 .sp Show WSP packet counters. .RE .SH "DIAGNOSTIC OPTIONS" .sp \-\-log\-level .RS 4 Set the active log level. Supported levels in lowest to highest order are "noisy", "debug", "info", "message", "warning", "critical", and "error". Messages at each level and higher will be printed, for example "warning" prints "warning", "critical", and "error" messages and "noisy" prints all messages. Levels are case insensitive. .RE .sp \-\-log\-fatal .RS 4 Abort the program if any messages are logged at the specified level or higher. For example, "warning" aborts on any "warning", "critical", or "error" messages. .RE .sp \-\-log\-domains .RS 4 Only print messages for the specified log domains, e.g. "GUI,Epan,sshdump". List of domains must be comma\-separated. .RE .sp \-\-log\-debug .RS 4 Force the specified domains to log at the "debug" level. List of domains must be comma\-separated. .RE .sp \-\-log\-noisy .RS 4 Force the specified domains to log at the "noisy" level. List of domains must be comma\-separated. .RE .sp \-\-log\-file .RS 4 Write log messages and stderr output to the specified file. .RE .SH "INTERFACE" .SS "MENU ITEMS" .sp \fIFile\0\(fc\0Open\fP, \fIFile\0\(fc\0Open Recent\fP, \fIFile\0\(fc\0Merge\fP .RS 4 .sp Merge another capture file to the currently loaded one. The \fIFile:Merge\fP dialog box allows the merge "Prepended", "Chronologically" or "Appended", relative to the already loaded one. .RE .sp \fIFile\0\(fc\0Close\fP .RS 4 .sp Open or close a capture file. The \fIFile:Open\fP dialog box 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 matching the filter are discarded. The \fIFile:Open Recent\fP is a submenu and will show a list of previously opened files. .RE .sp \fIFile\0\(fc\0Save\fP, \fIFile\0\(fc\0Save As\fP .RS 4 .sp Save the current capture, or the packets currently displayed from that 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 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 which to save it. .RE .sp \fIFile\fP\0\(fc\0\fIFile Set\fP\0\(fc\0\fIList Files\fP .RS 4 .sp Show a dialog box that lists all files of the file set matching the currently loaded file. A file set is a compound of files resulting from a capture using the "multiple files" / "ringbuffer" mode, recognizable by the filename pattern, e.g.: Filename_00001_20230714101530.pcap. .RE .sp \fIFile\fP\0\(fc\0\fIFile Set\fP\0\(fc\0\fINext File\fP, \fIFile\fP\0\(fc\0\fIFile Set\fP\0\(fc\0\fIPrevious File\fP .RS 4 .sp If the currently loaded file is part of a file set (see above), open the next / previous file in that set. .RE .sp \fIFile\0\(fc\0Export\fP .RS 4 .sp Export captured data into an external format. Note: the data cannot be imported back into Wireshark, so be sure to keep the capture file. .RE .sp \fIFile\0\(fc\0Print\fP .RS 4 .sp Print packet data from the current capture. You can select the range of packets to be printed (which packets are printed), and the output format of each packet (how each packet is printed). The output format will be similar to the displayed values, so a summary line, the packet details view, and/or the hex dump of the packet can be printed. .sp Printing options can be set with the \fIEdit:Preferences\fP menu item, or in the dialog box popped up by this menu item. .RE .sp \fIFile\0\(fc\0Quit\fP .RS 4 Exit the application. .RE .sp \fIEdit\fP\0\(fc\0\fICopy\fP\0\(fc\0\fIDescription\fP .RS 4 Copies the description of the selected field in the protocol tree to the clipboard. .RE .sp \fIEdit\fP\0\(fc\0\fICopy\fP\0\(fc\0\fIFieldname\fP .RS 4 Copies the fieldname of the selected field in the protocol tree to the clipboard. .RE .sp \fIEdit\fP\0\(fc\0\fICopy\fP\0\(fc\0\fIValue\fP .RS 4 Copies the value of the selected field in the protocol tree to the clipboard. .RE .sp \fIEdit\fP\0\(fc\0\fICopy\fP\0\(fc\0\fIAs Filter\fP .RS 4 .sp Create a display filter based on the data currently highlighted in the packet details and copy that filter to the clipboard. .sp 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. .RE .sp \fIEdit\0\(fc\0Find Packet\fP .RS 4 .sp Search forward or backward, starting with the currently selected packet (or the most recently selected packet, if no packet is selected). Search criteria can be a display filter expression, a string of hexadecimal digits, or a text string. .sp 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 packet details pane. .sp 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. .RE .sp \fIEdit\0\(fc\0Find Next\fP, \fIEdit\0\(fc\0Find Previous\fP .RS 4 .sp Search forward / backward for a packet matching the filter from the previous search, starting with the currently selected packet (or the most recently selected packet, if no packet is selected). .RE .sp \fIEdit\0\(fc\0Mark Packet (toggle)\fP .RS 4 .sp 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 the /"Edit:Find Packet" dialog can be used to find the next or previous marked packet. .RE .sp \fIEdit\0\(fc\0Find Next Mark\fP, \fIEdit\0\(fc\0Find Previous Mark\fP .RS 4 Find next or previous marked packet. .RE .sp \fIEdit\0\(fc\0Mark All Packets\fP, \fIEdit\0\(fc\0Unmark All Packets\fP .RS 4 Mark or unmark all packets that are currently displayed. .RE .sp \fIEdit\fP\0\(fc\0\fITime Reference\fP\0\(fc\0\fISet Time Reference (toggle)\fP .RS 4 .sp 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 list pane will be replaced with the string "\fBREF\fP". The relative time timestamp in later packets will then be calculated relative to the timestamp of this Time Reference packet and not the first packet in the capture. .sp 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. .sp If there is a column displayed for "Cumulative Bytes" this counter will be reset at every Time Reference packet. .RE .sp \fIEdit\fP\0\(fc\0\fITime Reference\fP\0\(fc\0\fIFind Next\fP, \fIEdit\fP\0\(fc\0\fITime Reference\fP\0\(fc\0\fIFind Previous\fP .RS 4 Search forward or backward for a time referenced packet. .RE .sp \fIEdit\0\(fc\0Configuration Profiles\fP .RS 4 Manage configuration profiles to be able to use more than one set of preferences and configurations. .RE .sp \fIEdit\0\(fc\0Preferences\fP .RS 4 Set the GUI, capture, printing and protocol options (see /Preferences dialog below). .RE .sp \fIView\0\(fc\0Main Toolbar\fP, \fIView\0\(fc\0Filter Toolbar\fP, \fIView\0\(fc\0Statusbar\fP .RS 4 Show or hide the main window controls. .RE .sp \fIView\0\(fc\0Packet List\fP, \fIView\0\(fc\0Packet Details\fP, \fIView\0\(fc\0Packet Bytes\fP .RS 4 Show or hide the main window panes. .RE .sp \fIView\0\(fc\0Time Display Format\fP .RS 4 Set the format of the packet timestamp displayed in the packet list window. .RE .sp \fIView\fP\0\(fc\0\fIName Resolution\fP\0\(fc\0\fIResolve Name\fP .RS 4 Try to resolve a name for the currently selected item. .RE .sp \fIView\fP\0\(fc\0\fIName Resolution\fP\0\(fc\0\fIEnable for ... Layer\fP .RS 4 Enable or disable translation of addresses to names in the display. .RE .sp \fIView\0\(fc\0Colorize Packet List\fP .RS 4 Enable or disable the coloring rules. Disabling will improve performance. .RE .sp \fIView\0\(fc\0Auto Scroll in Live Capture\fP .RS 4 Enable or disable the automatic scrolling of the packet list while a live capture is in progress. .RE .sp \fIView\0\(fc\0Zoom In\fP, \fIView\0\(fc\0Zoom Out\fP .RS 4 Zoom into or out of the main window data (by changing the font size). .RE .sp \fIView\0\(fc\0Normal Size\fP .RS 4 Reset the zoom level back to normal font size. .RE .sp \fIView\0\(fc\0Resize All Columns\fP .RS 4 Resize all columns to best fit the current packet display. .RE .sp \fIView\0\(fc\0Expand / Collapse Subtrees\fP .RS 4 Expand or collapse the currently selected item and its subtrees in the packet details. .RE .sp \fIView\0\(fc\0Expand All\fP, \fIView\0\(fc\0Collapse All\fP .RS 4 Expand or Collapse all branches of the packet details. .RE .sp \fIView\0\(fc\0Colorize Conversation\fP .RS 4 Select a color for a conversation. .RE .sp \fIView\0\(fc\0Reset Coloring 1\-10\fP .RS 4 Reset a color for a conversation. .RE .sp \fIView\0\(fc\0Coloring Rules\fP .RS 4 .sp 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. .RE .sp How Colorization Works .RS 4 .sp 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 expressions use exactly the same syntax as display filter expressions. .sp When Wireshark starts, the color filters are loaded from: .sp .RS 4 .ie n \{\ \h'-04' 1.\h'+01'\c .\} .el \{\ . sp -1 . IP " 1." 4.2 .\} The user\(cqs personal color filters file or, if that does not exist, .RE .sp .RS 4 .ie n \{\ \h'-04' 2.\h'+01'\c .\} .el \{\ . sp -1 . IP " 2." 4.2 .\} The global color filters file. .RE .sp If neither of these exist then the packets will not be colored. .RE .sp \fIView\0\(fc\0Show Packet In New Window\fP .RS 4 .sp Create a new window containing a packet details view and a hex dump window of the currently selected packet; this window will continue to display that packet\(cqs details and data even if another packet is selected. .RE .sp \fIView\0\(fc\0Reload\fP .RS 4 Reload a capture file. Same as \fIFile:Close\fP and \fIFile:Open\fP the same file again. .RE .sp \fIGo\0\(fc\0Back\fP .RS 4 Go back in previously visited packets history. .RE .sp \fIGo\0\(fc\0Forward\fP .RS 4 Go forward in previously visited packets history. .RE .sp \fIGo\0\(fc\0Go To Packet\fP .RS 4 Go to a particular numbered packet. .RE .sp \fIGo\0\(fc\0Go To Corresponding Packet\fP .RS 4 .sp If a field in the packet details pane containing a packet number is selected, go to the packet number specified by that field. (This works 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. .RE .sp \fIGo\0\(fc\0Previous Packet\fP, \fIGo\0\(fc\0Next Packet\fP, \fIGo\0\(fc\0First Packet\fP, \fIGo\0\(fc\0Last Packet\fP .RS 4 Go to the previous, next, first, or last packet in the capture. .RE .sp \fIGo\0\(fc\0Previous Packet In Conversation\fP, \fIGo\0\(fc\0Next Packet In Conversation\fP .RS 4 Go to the previous or next packet of the TCP, UDP or IP conversation. .RE .sp \fICapture\0\(fc\0Interfaces\fP .RS 4 .sp Shows a dialog box with all currently known interfaces and displaying the current network traffic amount. Capture sessions can be started from here. Beware: keeping this box open results in high system load! .RE .sp \fICapture\0\(fc\0Options\fP .RS 4 .sp Initiate a live packet capture (see /"Capture Options Dialog" below). If no filename is specified, a temporary file will be created to hold the capture. The location of the file can be chosen by setting your TMPDIR environment variable before starting \fBWireshark\fP. Otherwise, the default TMPDIR location is system\-dependent, but is likely either \fI/var/tmp\fP or \fI/tmp\fP. .RE .sp \fICapture\0\(fc\0Start\fP .RS 4 .sp Start a live packet capture with the previously selected options. This won\(cqt open the options dialog box, and can be convenient for repeatedly capturing with the same options. .RE .sp \fICapture\0\(fc\0Stop\fP .RS 4 Stop a running live capture. .RE .sp \fICapture\0\(fc\0Restart\fP .RS 4 .sp While a live capture is running, stop it and restart with the same options again. This can be convenient to remove irrelevant packets, if no valuable packets were captured so far. .RE .sp \fICapture\0\(fc\0Capture Filters\fP .RS 4 Edit the saved list of capture filters, allowing filters to be added, changed, or deleted. .RE .sp \fIAnalyze\0\(fc\0Display Filters\fP .RS 4 Edit the saved list of display filters, allowing filters to be added, changed, or deleted. .RE .sp \fIAnalyze\0\(fc\0Display Filter Macros\fP .RS 4 Create shortcuts for complex macros. .RE .sp \fIAnalyze\0\(fc\0Apply as Filter\fP .RS 4 .sp Create a display filter based on the data currently highlighted in the packet details and apply the filter. .sp 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. .sp The \fBSelected\fP option creates a display filter that tests for a match of the data; the \fBNot Selected\fP option creates a display filter that tests for a non\-match of the data. The \fBAnd Selected\fP, \fBOr Selected\fP, \fBAnd Not Selected\fP, and \fBOr Not Selected\fP options add to the end of the display filter in the strip at the top (or bottom) an AND or OR operator followed by the new display filter expression. .RE .sp \fIAnalyze\0\(fc\0Prepare as Filter\fP .RS 4 .sp Create a display filter based on the data currently highlighted in the packet details. The filter strip at the top (or bottom) is updated but it is not yet applied. .RE .sp \fIAnalyze\0\(fc\0Enabled Protocols\fP .RS 4 .sp 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. .sp When a protocol is disabled, dissection in a particular packet stops when that protocol is reached, and Wireshark moves on to the next packet. 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. .sp The list of protocols can be saved, so that Wireshark will start up with the protocols in that list disabled. .RE .sp \fIAnalyze\0\(fc\0Decode As\fP .RS 4 .sp 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 port 12345, using this dialog you can instruct Wireshark to decode all packets to or from that TCP port as HTTP packets. .RE .sp \fIAnalyze\0\(fc\0User Specified Decodes\fP .RS 4 .sp Create a new window showing whether any protocol ID to dissector mappings have been changed by the user. This window also allows the user to reset all decodes to their default values. .RE .sp \fIAnalyze\0\(fc\0Follow TCP Stream\fP .RS 4 .sp 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). .sp The window in which the data stream is displayed lets you select: .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} whether to display the entire conversation, or one or the other side of it; .RE .sp .RS 4 .ie n \{\ \h'-04'\(bu\h'+03'\c .\} .el \{\ . sp -1 . IP \(bu 2.3 .\} whether the data being displayed is to be treated as ASCII or EBCDIC text or as raw hex data; .RE .sp and lets you print what\(cqs currently being displayed, using the same print options that are used for the \fIFile:Print Packet\fP menu item, or save it as text to a file. .RE .sp \fIAnalyze\0\(fc\0Follow UDP Stream\fP, \fIAnalyze\0\(fc\0Follow TLS Stream\fP .RS 4 Similar to Analyze:Follow TCP Stream. .RE .sp \fIAnalyze\0\(fc\0Expert Info\fP, \fIAnalyze\0\(fc\0Expert Info Composite\fP .RS 4 Show anomalies found by Wireshark in a capture file. .RE .sp \fIAnalyze\0\(fc\0Conversation Filter\fP, \fIStatistics\0\(fc\0Summary\fP .RS 4 .sp 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. .RE .sp \fIStatistics\0\(fc\0Protocol Hierarchy\fP .RS 4 .sp 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) \fBended\fP in a particular protocol. In the table, they are listed under "End Packets" and "End Bytes". .RE .sp \fIStatistics\0\(fc\0Conversations\fP .RS 4 Lists of conversations; selectable by protocol. See Statistics:Conversation List below. .RE .sp \fIStatistics\0\(fc\0End Points\fP .RS 4 List of End Point Addresses by protocol with packets, bytes, and other counts. .RE .sp \fIStatistics\0\(fc\0Packet Lengths\fP .RS 4 Grouped counts of packet lengths (0\-19 bytes, 20\-39 bytes, ...) .RE .sp \fIStatistics\0\(fc\0I/O Graphs\fP .RS 4 .sp Open a window where up to 5 graphs in different colors can be displayed to indicate number of packets or number of bytes per second for all packets matching the specified filter. By default only one graph will be displayed showing number of packets per second. .sp 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. .sp 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 individual graph such as "Display: