4 wireshark - Interactively dump and analyze network traffic
9 S<[ B<-a> E<lt>capture autostop conditionE<gt> ] ...>
10 S<[ B<-b> E<lt>capture ring buffer optionE<gt> ] ...>
11 S<[ B<-B> E<lt>capture buffer size (Win32 only)E<gt> ] >
12 S<[ B<-c> E<lt>capture packet countE<gt> ]>
13 S<[ B<-C> E<lt>configuration profileE<gt> ]>
15 S<[ B<--display=>E<lt>X display to useE<gt> ] >
16 S<[ B<-f> E<lt>capture filterE<gt> ]>
17 S<[ B<-g> E<lt>packet numberE<gt> ]>
20 S<[ B<-i> E<lt>capture interfaceE<gt>|- ]>
21 S<[ B<-J> E<lt>jump filterE<gt> ]>
24 S<[ B<-K> E<lt>keytabE<gt> ]>
27 S<[ B<-m> E<lt>fontE<gt> ]>
29 S<[ B<-N> E<lt>name resolving flagsE<gt> ] >
30 S<[ B<-o> E<lt>preference/recent settingE<gt> ] ...>
32 S<[ B<-P> E<lt>path settingE<gt>]>
34 S<[ B<-r> E<lt>infileE<gt> ]>
35 S<[ B<-R> E<lt>read (display) filterE<gt> ]>
37 S<[ B<-s> E<lt>capture snaplenE<gt> ]>
38 S<[ B<-t> ad|a|r|d|dd|e ]>
40 S<[ B<-w> E<lt>outfileE<gt> ]>
41 S<[ B<-y> E<lt>capture link typeE<gt> ]>
42 S<[ B<-X> E<lt>eXtension optionE<gt> ]>
43 S<[ B<-z> E<lt>statisticsE<gt> ]>
44 S<[ E<lt>infileE<gt> ]>
48 B<Wireshark> is a GUI network protocol analyzer. It lets you
49 interactively browse packet data from a live network or from a
50 previously saved capture file. B<Wireshark>'s native capture file format
51 is B<libpcap> format, which is also the format used by B<tcpdump> and
54 B<Wireshark> can read / import the following file formats:
59 libpcap, tcpdump and various other tools using tcpdump's capture format
62 B<snoop> and B<atmsnoop>
65 Shomiti/Finisar B<Surveyor> captures
68 Novell B<LANalyzer> captures
71 Microsoft B<Network Monitor> captures
74 AIX's B<iptrace> captures
77 Cinco Networks B<NetXRay> captures
80 Network Associates Windows-based B<Sniffer> captures
83 Network General/Network Associates DOS-based B<Sniffer> (compressed or uncompressed) captures
86 AG Group/WildPackets B<EtherPeek>/B<TokenPeek>/B<AiroPeek>/B<EtherHelp>/B<PacketGrabber> captures
89 B<RADCOM>'s WAN/LAN analyzer captures
92 Network Instruments B<Observer> version 9 captures
95 B<Lucent/Ascend> router debug output
98 files from HP-UX's B<nettl>
101 B<Toshiba's> ISDN routers dump output
104 the output from B<i4btrace> from the ISDN4BSD project
107 traces from the B<EyeSDN> USB S0.
110 the output in B<IPLog> format from the Cisco Secure Intrusion Detection System
113 B<pppd logs> (pppdump format)
116 the output from VMS's B<TCPIPtrace>/B<TCPtrace>/B<UCX$TRACE> utilities
119 the text output from the B<DBS Etherwatch> VMS utility
122 Visual Networks' B<Visual UpTime> traffic capture
125 the output from B<CoSine> L2 debug
128 the output from Accellent's B<5Views> LAN agents
131 Endace Measurement Systems' ERF format captures
134 Linux Bluez Bluetooth stack B<hcidump -w> traces
137 Catapult DCT2000 .out files
140 TamoSoft CommView files
143 Apple PacketLogger files
147 There is no need to tell B<Wireshark> what type of
148 file you are reading; it will determine the file type by itself.
149 B<Wireshark> is also capable of reading any of these file formats if they
150 are compressed using gzip. B<Wireshark> recognizes this directly from
151 the file; the '.gz' extension is not required for this purpose.
153 Like other protocol analyzers, B<Wireshark>'s main window shows 3 views
154 of a packet. It shows a summary line, briefly describing what the
155 packet is. A packet details display is shown, allowing you to drill
156 down to exact protocol or field that you interested in. Finally, a hex
157 dump shows you exactly what the packet looks like when it goes over the
160 In addition, B<Wireshark> has some features that make it unique. It can
161 assemble all the packets in a TCP conversation and show you the ASCII
162 (or EBCDIC, or hex) data in that conversation. Display filters in
163 B<Wireshark> are very powerful; more fields are filterable in B<Wireshark>
164 than in other protocol analyzers, and the syntax you can use to create
165 your filters is richer. As B<Wireshark> progresses, expect more and more
166 protocol fields to be allowed in display filters.
168 Packet capturing is performed with the pcap library. The capture filter
169 syntax follows the rules of the pcap library. This syntax is different
170 from the display filter syntax.
172 Compressed file support uses (and therefore requires) the zlib library.
173 If the zlib library is not present, B<Wireshark> will compile, but will
174 be unable to read compressed files.
176 The pathname of a capture file to be read can be specified with the
177 B<-r> option or can be specified as a command-line argument.
181 Most users will want to start B<Wireshark> without options and configure
182 it from the menus instead. Those users may just skip this section.
186 =item -a E<lt>capture autostop conditionE<gt>
188 Specify a criterion that specifies when B<Wireshark> is to stop writing
189 to a capture file. The criterion is of the form I<test>B<:>I<value>,
190 where I<test> is one of:
192 B<duration>:I<value> Stop writing to a capture file after I<value> seconds have
195 B<filesize>:I<value> Stop writing to a capture file after it reaches a size of
196 I<value> kilobytes (where a kilobyte is 1024 bytes). If this option is used
197 together with the -b option, Wireshark will stop writing to the current
198 capture file and switch to the next one if filesize is reached.
200 B<files>:I<value> Stop writing to capture files after I<value> number of files
203 =item -b E<lt>capture ring buffer optionE<gt>
205 Cause B<Wireshark> to run in "multiple files" mode. In "multiple files" mode,
206 B<Wireshark> will write to several capture files. When the first capture file
207 fills up, B<Wireshark> will switch writing to the next file and so on.
209 The created filenames are based on the filename given with the B<-w> flag,
210 the number of the file and on the creation date and time,
211 e.g. outfile_00001_20050604120117.pcap, outfile_00002_20050604120523.pcap, ...
213 With the I<files> option it's also possible to form a "ring buffer".
214 This will fill up new files until the number of files specified,
215 at which point B<Wireshark> will discard the data in the first file and start
216 writing to that file and so on. If the I<files> option is not set,
217 new files filled up until one of the capture stop conditions match (or
218 until the disk is full).
220 The criterion is of the form I<key>B<:>I<value>,
221 where I<key> is one of:
223 B<duration>:I<value> switch to the next file after I<value> seconds have
224 elapsed, even if the current file is not completely filled up.
226 B<filesize>:I<value> switch to the next file after it reaches a size of
227 I<value> kilobytes (where a kilobyte is 1024 bytes).
229 B<files>:I<value> begin again with the first file after I<value> number of
230 files were written (form a ring buffer). This value must be less than 100000.
231 Caution should be used when using large numbers of files: some filesystems do
232 not handle many files in a single directory well. The B<files> criterion
233 requires either B<duration> or B<filesize> to be specified to control when to
234 go to the next file. It should be noted that each B<-b> parameter takes exactly
235 one criterion; to specify two criterion, each must be preceded by the B<-b>
238 Example: B<-b filesize:1024 -b files:5> results in a ring buffer of five files
239 of size one megabyte.
241 =item -B E<lt>capture buffer sizeE<gt>
243 Set capture buffer size (in MB, default is 1MB). This is used by the
244 the capture driver to buffer packet data until that data can be written
245 to disk. If you encounter packet drops while capturing, try to increase
246 this size. Note that, while B<Tshark> attempts to set the buffer size
247 to 1MB by default, and can be told to set it to a larger value, the
248 system or interface on which you're capturing might silently limit the
249 capture buffer size to a lower value or raise it to a higher value.
251 This is available on UNIX systems with libpcap 1.0.0 or later and on
252 Windows. It is not available on UNIX systems with earlier versions of
255 =item -c E<lt>capture packet countE<gt>
257 Set the maximum number of packets to read when capturing live
260 =item -C E<lt>configuration profileE<gt>
262 Start with the given configuration profile.
266 Print a list of the interfaces on which B<Wireshark> can capture, and
267 exit. For each network interface, a number and an
268 interface name, possibly followed by a text description of the
269 interface, is printed. The interface name or the number can be supplied
270 to the B<-i> flag to specify an interface on which to capture.
272 This can be useful on systems that don't have a command to list them
273 (e.g., Windows systems, or UNIX systems lacking B<ifconfig -a>);
274 the number can be useful on Windows 2000 and later systems, where the
275 interface name is a somewhat complex string.
277 Note that "can capture" means that B<Wireshark> was able to open
278 that device to do a live capture; if, on your system, a program doing a
279 network capture must be run from an account with special privileges (for
280 example, as root), then, if B<Wireshark> is run with the B<-D> flag and
281 is not run from such an account, it will not list any interfaces.
283 =item --display=E<lt>X display to useE<gt>
285 Specifies the X display to use. A hostname and screen (otherhost:0.0)
286 or just a screen (:0.0) can be specified. This option is not available
289 =item -f E<lt>capture filterE<gt>
291 Set the capture filter expression.
293 =item -g E<lt>packet numberE<gt>
295 After reading in a capture file using the B<-r> flag, go to the given I<packet number>.
299 Print the version and options and exit.
303 Hide the capture info dialog during live packet capture.
305 =item -i E<lt>capture interfaceE<gt>|-
307 Set the name of the network interface or pipe to use for live packet
310 Network interface names should match one of the names listed in
311 "B<wireshark -D>" (described above); a number, as reported by
312 "B<wireshark -D>", can also be used. If you're using UNIX, "B<netstat
313 -i>" or "B<ifconfig -a>" might also work to list interface names,
314 although not all versions of UNIX support the B<-a> flag to B<ifconfig>.
316 If no interface is specified, B<Wireshark> searches the list of
317 interfaces, choosing the first non-loopback interface if there are any
318 non-loopback interfaces, and choosing the first loopback interface if
319 there are no non-loopback interfaces. If there are no interfaces at all,
320 B<Wireshark> reports an error and doesn't start the capture.
322 Pipe names should be either the name of a FIFO (named pipe) or ``-'' to
323 read data from the standard input. On Windows systems, pipe names must be
324 of the form ``\\pipe\.\B<pipename>''. Data read from pipes must be in
325 standard libpcap format.
327 =item -J E<lt>jump filterE<gt>
329 After reading in a capture file using the B<-r> flag, jump to the packet
330 matching the filter (display filter syntax). If no exact match is found
331 the first packet after that is selected.
335 Use after B<-J> to change the behavior when no exact match is found for
336 the filter. With this option select the first packet before.
340 Start the capture session immediately. If the B<-i> flag was
341 specified, the capture uses the specified interface. Otherwise,
342 B<Wireshark> searches the list of interfaces, choosing the first
343 non-loopback interface if there are any non-loopback interfaces, and
344 choosing the first loopback interface if there are no non-loopback
345 interfaces; if there are no interfaces, B<Wireshark> reports an error and
346 doesn't start the capture.
348 =item -K E<lt>keytabE<gt>
350 Load kerberos crypto keys from the specified keytab file.
351 This option can be used multiple times to load keys from several files.
353 Example: B<-K krb5.keytab>
357 Turn on automatic scrolling if the packet display is being updated
358 automatically as packets arrive during a capture (as specified by the
363 List the data link types supported by the interface and exit.
365 =item -m E<lt>fontE<gt>
367 Set the name of the font used by B<Wireshark> for most text. B<Wireshark>
368 will construct the name of the bold font used for the data in the byte
369 view pane that corresponds to the field selected in the packet details
370 pane from the name of the main text font.
374 Disable network object name resolution (such as hostname, TCP and UDP port
375 names), the B<-N> flag might override this one.
377 =item -N E<lt>name resolving flagsE<gt>
379 Turn on name resolving only for particular types of addresses and port
380 numbers, with name resolving for other types of addresses and port
381 numbers turned off. This flag overrides B<-n> if both B<-N> and B<-n> are
382 present. If both B<-N> and B<-n> flags are not present, all name resolutions are
385 The argument is a string that may contain the letters:
387 B<m> to enable MAC address resolution
389 B<n> to enable network address resolution
391 B<t> to enable transport-layer port number resolution
393 B<C> to enable concurrent (asynchronous) DNS lookups
395 =item -o E<lt>preference/recent settingE<gt>
397 Set a preference or recent value, overriding the default value and any value
398 read from a preference/recent file. The argument to the flag is a string of
399 the form I<prefname>B<:>I<value>, where I<prefname> is the name of the
400 preference/recent value (which is the same name that would appear in the
401 preference/recent file), and I<value> is the value to which it should be set.
402 Since B<Ethereal> 0.10.12, the recent settings replaces the formerly used
403 -B, -P and -T flags to manipulate the GUI dimensions.
405 If I<prefname> is "uat", you can override settings in various user access
406 tables using the form uatB<:>I<uat filename>:I<uat record>. I<uat filename>
407 must be the name of a UAT file, e.g. I<user_dlts>. I<uat_record> must be in
408 the form of a valid record for that file, including quotes. For instance, to
409 specify a user DLT from the command line, you would use
413 -o "uat:user_dlts:\"User 0 (DLT=147)\",\"cops\",\"0\",\"\",\"0\",\"\""
419 I<Don't> put the interface into promiscuous mode. Note that the
420 interface might be in promiscuous mode for some other reason; hence,
421 B<-p> cannot be used to ensure that the only traffic that is captured is
422 traffic sent to or from the machine on which B<Wireshark> is running,
423 broadcast traffic, and multicast traffic to addresses received by that
426 =item -P E<lt>path settingE<gt>
428 Special path settings usually detected automatically. This is used for
429 special cases, e.g. starting Wireshark from a known location on an USB stick.
431 The criterion is of the form I<key>B<:>I<path>, where I<key> is one of:
433 B<persconf>:I<path> path of personal configuration files, like the
436 B<persdata>:I<path> path of personal data files, it's the folder initially
437 opened. After the very first initialization, the recent file will keep the
442 Cause B<Wireshark> to exit after the end of capture session (useful in
443 batch mode with B<-c> option for instance); this option requires the
444 B<-i> and B<-w> parameters.
446 =item -r E<lt>infileE<gt>
448 Read packet data from I<infile>, can be any supported capture file format
449 (including gzipped files). It's not possible to use named pipes or stdin
452 =item -R E<lt>read (display) filterE<gt>
454 When reading a capture file specified with the B<-r> flag, causes the
455 specified filter (which uses the syntax of display filters, rather than
456 that of capture filters) to be applied to all packets read from the
457 capture file; packets not matching the filter are discarded.
461 Automatically update the packet display as packets are coming in.
463 =item -s E<lt>capture snaplenE<gt>
465 Set the default snapshot length to use when capturing live data.
466 No more than I<snaplen> bytes of each network packet will be read into
467 memory, or saved to disk. A value of 0 specifies a snapshot length of
468 65535, so that the full packet is captured; this is the default.
470 =item -t ad|a|r|d|dd|e
472 Set the format of the packet timestamp displayed in the packet list
473 window. The format can be one of:
475 B<ad> absolute with date: The absolute date and time is the actual time and
476 date the packet was captured
478 B<a> absolute: The absolute time is the actual time the packet was captured,
479 with no date displayed
481 B<r> relative: The relative time is the time elapsed between the first packet
482 and the current packet
484 B<d> delta: The delta time is the time since the previous packet was
487 B<dd> delta_displayed: The delta_displayed time is the time since the
488 previous displayed packet was captured
490 B<e> epoch: The time in seconds since epoch (Jan 1, 1970 00:00:00)
492 The default format is relative.
496 Print the version and exit.
498 =item -w E<lt>outfileE<gt>
500 Set the default capture file name.
502 =item -y E<lt>capture link typeE<gt>
504 If a capture is started from the command line with B<-k>, set the data
505 link type to use while capturing packets. The values reported by B<-L>
506 are the values that can be used.
508 =item -X E<lt>eXtension optionsE<gt>
510 Specify an option to be passed to an B<Wireshark> module. The eXtension option
511 is in the form I<extension_key>B<:>I<value>, where I<extension_key> can be:
513 B<lua_script>:I<lua_script_filename> tells B<Wireshark> to load the given script in addition to the
516 B<stdin_descr>:I<description> tells B<Wireshark> to use the given description when
517 capturing from standard input (B<-i ->).
519 =item -z E<lt>statisticsE<gt>
521 Get B<Wireshark> to collect various types of statistics and display the result
522 in a window that updates in semi-real time.
524 Currently implemented statistics are:
528 =item B<-z> dcerpc,srt,I<uuid>,I<major>.I<minor>[,I<filter>]
530 Collect call/reply SRT (Service Response Time) data for DCERPC interface I<uuid>,
531 version I<major>.I<minor>.
532 Data collected is the number of calls for each procedure, MinSRT, MaxSRT
535 Example: S<B<-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0>> will collect data for the CIFS SAMR Interface.
537 This option can be used multiple times on the command line.
539 If the optional I<filter> is provided, the stats will only be calculated
540 on those calls that match that filter.
542 Example: S<B<-z dcerpc,srt,12345778-1234-abcd-ef00-0123456789ac,1.0,ip.addr==1.2.3.4>> will collect SAMR
543 SRT statistics for a specific host.
547 Collect packet/bytes statistics for the capture in intervals of 1 second.
548 This option will open a window with up to 5 color-coded graphs where
549 number-of-packets-per-second or number-of-bytes-per-second statistics
550 can be calculated and displayed.
552 This option can be used multiple times on the command line.
554 This graph window can also be opened from the Analyze:Statistics:Traffic:IO-Stat
557 =item B<-z> rpc,srt,I<program>,I<version>[,<filter>]
559 Collect call/reply SRT (Service Response Time) data for I<program>/I<version>. Data collected
560 is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.
562 Example: B<-z rpc,srt,100003,3> will collect data for NFS v3.
564 This option can be used multiple times on the command line.
566 If the optional I<filter> is provided, the stats will only be calculated
567 on those calls that match that filter.
569 Example: S<B<-z rpc,srt,100003,3,nfs.fh.hash==0x12345678>> will collect NFS v3
570 SRT statistics for a specific file.
572 =item B<-z> rpc,programs
574 Collect call/reply RTT data for all known ONC-RPC programs/versions.
575 Data collected is the number of calls for each protocol/version, MinRTT,
578 =item B<-z> scsi,srt,I<cmdset>[,<filter>]
580 Collect call/reply SRT (Service Response Time) data for SCSI commandset <cmdset>.
582 Commandsets are 0:SBC 1:SSC 5:MMC
585 is the number of calls for each procedure, MinSRT, MaxSRT and AvgSRT.
587 Example: B<-z scsi,srt,0> will collect data for SCSI BLOCK COMMANDS (SBC).
589 This option can be used multiple times on the command line.
591 If the optional I<filter> is provided, the stats will only be calculated
592 on those calls that match that filter.
594 Example: B<-z scsi,srt,0,ip.addr==1.2.3.4> will collect SCSI SBC
595 SRT statistics for a specific iscsi/ifcp/fcip host.
597 =item B<-z> smb,srt[,I<filter>]
599 Collect call/reply SRT (Service Response Time) data for SMB. Data collected
600 is the number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.
602 Example: B<-z smb,srt>
604 The data will be presented as separate tables for all normal SMB commands,
605 all Transaction2 commands and all NT Transaction commands.
606 Only those commands that are seen in the capture will have their stats
608 Only the first command in a xAndX command chain will be used in the
609 calculation. So for common SessionSetupAndX + TreeConnectAndX chains,
610 only the SessionSetupAndX call will be used in the statistics.
611 This is a flaw that might be fixed in the future.
613 This option can be used multiple times on the command line.
615 If the optional I<filter> is provided, the stats will only be calculated
616 on those calls that match that filter.
618 Example: B<-z "smb,srt,ip.addr==1.2.3.4"> will collect stats only for
619 SMB packets exchanged by the host at IP address 1.2.3.4 .
621 =item B<-z> fc,srt[,I<filter>]
623 Collect call/reply SRT (Service Response Time) data for FC. Data collected
624 is the number of calls for each Fibre Channel command, MinSRT, MaxSRT and AvgSRT.
626 Example: B<-z fc,srt>
627 will calculate the Service Response Time as the time delta between the
628 First packet of the exchange and the Last packet of the exchange.
630 The data will be presented as separate tables for all normal FC commands,
631 Only those commands that are seen in the capture will have its stats
634 This option can be used multiple times on the command line.
636 If the optional I<filter> is provided, the stats will only be calculated
637 on those calls that match that filter.
639 Example: B<-z "fc,srt,fc.id==01.02.03"> will collect stats only for
640 FC packets exchanged by the host at FC address 01.02.03 .
642 =item B<-z> ldap,srt[,I<filter>]
644 Collect call/reply SRT (Service Response Time) data for LDAP. Data collected
645 is the number of calls for each implemented LDAP command, MinSRT, MaxSRT and AvgSRT.
647 Example: B<-z ldap,srt>
648 will calculate the Service Response Time as the time delta between the
649 Request and the Response.
651 The data will be presented as separate tables for all implemented LDAP commands,
652 Only those commands that are seen in the capture will have its stats
655 This option can be used multiple times on the command line.
657 If the optional I<filter> is provided, the stats will only be calculated
658 on those calls that match that filter.
660 Example: use B<-z "ldap,srt,ip.addr==10.1.1.1"> will collect stats only for
661 LDAP packets exchanged by the host at IP address 10.1.1.1 .
663 The only LDAP commands that are currently implemented and for which the stats will be available are:
673 =item B<-z> mgcp,srt[I<,filter>]
675 Collect request/response SRT (Service Response Time) data for MGCP.
676 (This is similar to B<-z smb,srt>). Data collected is the number of calls
677 for each known MGCP Type, Minimum SRT, Maximum SRT and Average SRT.
679 Example: B<-z mgcp,srt>
681 This option can be used multiple times on the command line.
683 If the optional I<filter> is provided, the stats will only be calculated
684 on those calls that match that filter.
686 Example: B<-z "mgcp,srt,ip.addr==1.2.3.4"> will collect stats only for
687 MGCP packets exchanged by the host at IP address 1.2.3.4 .
689 =item B<-z> megaco,srt[I<,filter>]
691 Collect request/response SRT (Service Response Time) data for MEGACO.
692 (This is similar to B<-z smb,srt>). Data collected is the number of calls
693 for each known MEGACO Command, Minimum SRT, Maximum SRT and Average SRT.
695 Example: B<-z megaco,srt>
697 This option can be used multiple times on the command line.
699 If the optional I<filter> is provided, the stats will only be calculated
700 on those calls that match that filter.
702 Example: B<-z "megaco,srt,ip.addr==1.2.3.4"> will collect stats only for
703 MEGACO packets exchanged by the host at IP address 1.2.3.4 .
705 =item B<-z> conv,I<type>[,I<filter>]
707 Create a table that lists all conversations that could be seen in the
708 capture. I<type> specifies the conversation endpoint types for which we
709 want to generate the statistics; currently the supported ones are:
711 "eth" Ethernet addresses
712 "fc" Fibre Channel addresses
713 "fddi" FDDI addresses
715 "ipv6" IPv6 addresses
717 "tcp" TCP/IP socket pairs Both IPv4 and IPv6 are supported
718 "tr" Token Ring addresses
719 "udp" UDP/IP socket pairs Both IPv4 and IPv6 are supported
721 If the optional I<filter> is specified, only those packets that match the
722 filter will be used in the calculations.
724 The table is presented with one line for each conversation and displays
725 the number of packets/bytes in each direction as well as the total
726 number of packets/bytes. By default, the table is sorted according to
727 the total number of packets.
729 These tables can also be generated at runtime by selecting the appropriate
730 conversation type from the menu "Tools/Statistics/Conversation List/".
732 =item B<-z> h225,counter[I<,filter>]
734 Count ITU-T H.225 messages and their reasons. In the first column you get a
735 list of H.225 messages and H.225 message reasons which occur in the current
736 capture file. The number of occurrences of each message or reason is displayed
737 in the second column.
739 Example: B<-z h225,counter>
741 This option can be used multiple times on the command line.
743 If the optional I<filter> is provided, the stats will only be calculated
744 on those calls that match that filter.
746 Example: B<-z "h225,counter,ip.addr==1.2.3.4"> will collect stats only for
747 H.225 packets exchanged by the host at IP address 1.2.3.4 .
749 =item B<-z> h225,srt[I<,filter>]
751 Collect request/response SRT (Service Response Time) data for ITU-T H.225 RAS.
752 Data collected is the number of calls of each ITU-T H.225 RAS Message Type,
753 Minimum SRT, Maximum SRT, Average SRT, Minimum in Packet, and Maximum in Packet.
754 You will also get the number of Open Requests (Unresponded Requests),
755 Discarded Responses (Responses without matching request) and Duplicate Messages.
757 Example: B<-z h225,srt>
759 This option can be used multiple times on the command line.
761 If the optional I<filter> is provided, the stats will only be calculated
762 on those calls that match that filter.
764 Example: B<-z "h225,srt,ip.addr==1.2.3.4"> will collect stats only for
765 ITU-T H.225 RAS packets exchanged by the host at IP address 1.2.3.4 .
767 =item B<-z> sip,stat[I<,filter>]
769 This option will activate a counter for SIP messages. You will get the number
770 of occurrences of each SIP Method and of each SIP Status-Code. Additionally you
771 also get the number of resent SIP Messages (only for SIP over UDP).
773 Example: B<-z sip,stat>
775 This option can be used multiple times on the command line.
777 If the optional I<filter> is provided, the stats will only be calculated
778 on those calls that match that filter.
780 Example: B<-z "sip,stat,ip.addr==1.2.3.4"> will collect stats only for
781 SIP packets exchanged by the host at IP address 1.2.3.4 .
783 =item B<-z> voip,calls
785 This option will show a window that shows VoIP calls found in the capture file.
786 This is the same window shown as when you go to the Statistics Menu and choose
789 Example: B<-z voip,calls>
803 =item File:Open Recent
807 Merge another capture file to the currently loaded one. The I<File:Merge>
808 dialog box allows the merge "Prepended", "Chronologically" or "Appended",
809 relative to the already loaded one.
813 Open or close a capture file. The I<File:Open> dialog box
814 allows a filter to be specified; when the capture file is read, the
815 filter is applied to all packets read from the file, and packets not
816 matching the filter are discarded. The I<File:Open Recent> is a submenu
817 and will show a list of previously opened files.
823 Save the current capture, or the packets currently displayed from that
824 capture, to a file. Check boxes let you select whether to save all
825 packets, or just those that have passed the current display filter and/or
826 those that are currently marked, and an option menu lets you select (from
827 a list of file formats in which at particular capture, or the packets
828 currently displayed from that capture, can be saved), a file format in
831 =item File:File Set:List Files
833 Show a dialog box that lists all files of the file set matching the currently
834 loaded file. A file set is a compound of files resulting from a capture using
835 the "multiple files" / "ringbuffer" mode, recognizable by the filename pattern,
836 e.g.: Filename_00001_20050604101530.pcap.
838 =item File:File Set:Next File
840 =item File:File Set:Previous File
842 If the currently loaded file is part of a file set (see above), open the
843 next / previous file in that set.
847 Export captured data into an external format. Note: the data cannot be
848 imported back into Wireshark, so be sure to keep the capture file.
852 Print packet data from the current capture. You can select the range of
853 packets to be printed (which packets are printed), and the output format of
854 each packet (how each packet is printed). The output format will be similar
855 to the displayed values, so a summary line, the packet details view, and/or
856 the hex dump of the packet can be printed.
858 Printing options can be set with the I<Edit:Preferences> menu item, or in the
859 dialog box popped up by this menu item.
863 Exit the application.
865 =item Edit:Copy:Description
867 Copies the description of the selected field in the protocol tree to
870 =item Edit:Copy:Fieldname
872 Copies the fieldname of the selected field in the protocol tree to
875 =item Edit:Copy:Value
877 Copies the value of the selected field in the protocol tree to
880 =item Edit:Copy:As Filter
882 Create a display filter based on the data currently highlighted in the
883 packet details and copy that filter to the clipboard.
885 If that data is a field that can be tested in a display filter
886 expression, the display filter will test that field; otherwise, the
887 display filter will be based on the absolute offset within the packet.
888 Therefore it could be unreliable if the packet contains protocols with
889 variable-length headers, such as a source-routed token-ring packet.
891 =item Edit:Find Packet
893 Search forward or backward, starting with the currently selected packet
894 (or the most recently selected packet, if no packet is selected). Search
895 criteria can be a display filter expression, a string of hexadecimal
896 digits, or a text string.
898 When searching for a text string, you can search the packet data, or you
899 can search the text in the Info column in the packet list pane or in the
902 Hexadecimal digits can be separated by colons, periods, or dashes.
903 Text string searches can be ASCII or Unicode (or both), and may be
908 =item Edit:Find Previous
910 Search forward / backward for a packet matching the filter from the previous
911 search, starting with the currently selected packet (or the most recently
912 selected packet, if no packet is selected).
914 =item Edit:Mark Packet (toggle)
916 Mark (or unmark if currently marked) the selected packet. The field
917 "frame.marked" is set for packets that are marked, so that, for example,
918 a display filters can be used to display only marked packets, and so that
919 the L<Edit:Find Packet|/item_edit_3afind_packet> dialog can be used to find the next or previous
922 =item Edit:Find Next Mark
924 =item Edit:Find Previous Mark
926 Find next/previous marked packet.
928 =item Edit:Mark All Packets
930 =item Edit:Unmark All Packets
932 Mark / Unmark all packets that are currently displayed.
934 =item Edit:Time Reference:Set Time Reference (toggle)
936 Set (or unset if currently set) the selected packet as a Time Reference packet.
937 When a packet is set as a Time Reference packet, the timestamps in the packet
938 list pane will be replaced with the string "*REF*".
939 The relative time timestamp in later packets will then be calculated relative
940 to the timestamp of this Time Reference packet and not the first packet in
943 Packets that have been selected as Time Reference packets will always be
944 displayed in the packet list pane. Display filters will not affect or
947 If there is a column displayed for "Cumulative Bytes" this counter will
948 be reset at every Time Reference packet.
950 =item Edit:Time Reference:Find Next
952 =item Edit:Time Reference:Find Previous
954 Search forward / backward for a time referenced packet.
956 =item Edit:Configuration Profiles
958 Manage configuration profiles to be able to use more than one set of
959 preferences and configurations.
961 =item Edit:Preferences
963 Set the GUI, capture, printing and protocol options
964 (see L<Preferences|/item_preferences> dialog below).
966 =item View:Main Toolbar
968 =item View:Filter Toolbar
972 Show or hide the main window controls.
974 =item View:Packet List
976 =item View:Packet Details
978 =item View:Packet Bytes
980 Show or hide the main window panes.
982 =item View:Time Display Format
984 Set the format of the packet timestamp displayed in the packet list window.
986 =item View:Name Resolution:Resolve Name
988 Try to resolve a name for the currently selected item.
990 =item View:Name Resolution:Enable for ... Layer
992 Enable or disable translation of addresses to names in the display.
994 =item View:Colorize Packet List
996 Enable or disable the coloring rules. Disabling will improve performance.
998 =item View:Auto Scroll in Live Capture
1000 Enable or disable the automatic scrolling of the
1001 packet list while a live capture is in progress.
1007 Zoom into / out of the main window data (by changing the font size).
1009 =item View:Normal Size
1011 Reset the zoom factor of zoom in / zoom out back to normal font size.
1013 =item View:Resize All Columns
1015 Resize all columns to best fit the current packet display.
1017 =item View:Expand Subtrees
1019 Expands the currently selected item and it's subtrees in the packet details.
1021 =item View:Expand All
1023 =item View:Collapse All
1025 Expand / Collapse all branches of the packet details.
1027 =item View:Colorize Conversation
1029 Select color for a conversation.
1031 =item View:Reset Coloring 1-10
1033 Reset Color for a conversation.
1035 =item View:Coloring Rules
1037 Change the foreground and background colors of the packet information in
1038 the list of packets, based upon display filters. The list of display
1039 filters is applied to each packet sequentially. After the first display
1040 filter matches a packet, any additional display filters in the list are
1041 ignored. Therefore, if you are filtering on the existence of protocols,
1042 you should list the higher-level protocols first, and the lower-level
1047 =item How Colorization Works
1049 Packets are colored according to a list of color filters. Each filter
1050 consists of a name, a filter expression and a coloration. A packet is
1051 colored according to the first filter that it matches. Color filter
1052 expressions use exactly the same syntax as display filter expressions.
1054 When Wireshark starts, the color filters are loaded from:
1058 1. The user's personal color filters file or, if that does not exist,
1060 2. The global color filters file.
1064 If neither of these exist then the packets will not be colored.
1068 =item View:Show Packet In New Window
1070 Create a new window containing a packet details view and a hex dump
1071 window of the currently selected packet; this window will continue to
1072 display that packet's details and data even if another packet is
1077 Reload a capture file. Same as I<File:Close> and I<File:Open> the same
1082 Go back in previously visited packets history.
1086 Go forward in previously visited packets history.
1088 =item Go:Go To Packet
1090 Go to a particular numbered packet.
1092 =item Go:Go To Corresponding Packet
1094 If a field in the packet details pane containing a packet number is
1095 selected, go to the packet number specified by that field. (This works
1096 only if the dissector that put that entry into the packet details put it
1097 into the details as a filterable field rather than just as text.) This
1098 can be used, for example, to go to the packet for the request
1099 corresponding to a reply, or the reply corresponding to a request, if
1100 that packet number has been put into the packet details.
1102 =item Go:Previous Packet
1104 =item Go:Next Packet
1106 =item Go:First Packet
1108 =item Go:Last Packet
1110 Go to the previous / next / first / last packet in the capture.
1112 =item Go:Previous Packet In Conversation
1114 =item Go:Next Packet In Conversation
1116 Go to the previous / next packet of the converation (TCP, UDP or IP)
1118 =item Capture:Interfaces
1120 Shows a dialog box with all currently known interfaces and displaying the
1121 current network traffic amount. Capture sessions can be started from here.
1122 Beware: keeping this box open results in high system load!
1124 =item Capture:Options
1126 Initiate a live packet capture (see L<Capture Options|/item_capture_options>
1127 dialog below). If no filename is specified, a temporary file will be created
1128 to hold the capture. The location of the file can be chosen by setting your
1129 TMPDIR environment variable before starting B<Wireshark>. Otherwise, the
1130 default TMPDIR location is system-dependent, but is likely either F</var/tmp>
1135 Start a live packet capture with the previously selected options. This won't
1136 open the options dialog box, and can be convenient for repeatedly capturing
1137 with the same options.
1141 Stop a running live capture.
1143 =item Capture:Restart
1145 While a live capture is running, stop it and restart with the same options
1146 again. This can be convenient to remove irrelevant packets, if no valuable
1147 packets were captured so far.
1149 =item Capture:Capture Filters
1151 Edit the saved list of capture filters, allowing filters to be added,
1152 changed, or deleted.
1154 =item Analyze:Display Filters
1156 Edit the saved list of display filters, allowing filters to be added,
1157 changed, or deleted.
1159 =item Analyze:Display Filter Macros
1161 Create shortcuts for complex macros
1163 =item Analyze:Apply as Filter
1165 Create a display filter based on the data currently highlighted in the
1166 packet details and apply the filter.
1168 If that data is a field that can be tested in a display filter
1169 expression, the display filter will test that field; otherwise, the
1170 display filter will be based on the absolute offset within the packet.
1171 Therefore it could be unreliable if the packet contains protocols with
1172 variable-length headers, such as a source-routed token-ring packet.
1174 The B<Selected> option creates a display filter that tests for a match
1175 of the data; the B<Not Selected> option creates a display filter that
1176 tests for a non-match of the data. The B<And Selected>, B<Or Selected>,
1177 B<And Not Selected>, and B<Or Not Selected> options add to the end of
1178 the display filter in the strip at the top (or bottom) an AND or OR
1179 operator followed by the new display filter expression.
1181 =item Analyze:Prepare a Filter
1183 Create a display filter based on the data currently highlighted in the
1184 packet details. The filter strip at the top (or bottom) is updated but
1185 it is not yet applied.
1187 =item Analyze:Enabled Protocols
1189 Allow protocol dissection to be enabled or disabled for a specific
1190 protocol. Individual protocols can be enabled or disabled by clicking
1191 on them in the list or by highlighting them and pressing the space bar.
1192 The entire list can be enabled, disabled, or inverted using the buttons
1195 When a protocol is disabled, dissection in a particular packet stops
1196 when that protocol is reached, and Wireshark moves on to the next packet.
1197 Any higher-layer protocols that would otherwise have been processed will
1198 not be displayed. For example, disabling TCP will prevent the dissection
1199 and display of TCP, HTTP, SMTP, Telnet, and any other protocol exclusively
1202 The list of protocols can be saved, so that Wireshark will start up with
1203 the protocols in that list disabled.
1205 =item Analyze:Decode As
1207 If you have a packet selected, present a dialog allowing you to change
1208 which dissectors are used to decode this packet. The dialog has one
1209 panel each for the link layer, network layer and transport layer
1210 protocol/port numbers, and will allow each of these to be changed
1211 independently. For example, if the selected packet is a TCP packet to
1212 port 12345, using this dialog you can instruct Wireshark to decode all
1213 packets to or from that TCP port as HTTP packets.
1215 =item Analyze:User Specified Decodes
1217 Create a new window showing whether any protocol ID to dissector
1218 mappings have been changed by the user. This window also allows the
1219 user to reset all decodes to their default values.
1221 =item Analyze:Follow TCP Stream
1223 If you have a TCP packet selected, display the contents of the data
1224 stream for the TCP connection to which that packet belongs, as text, in
1225 a separate window, and leave the list of packets in a filtered state,
1226 with only those packets that are part of that TCP connection being
1227 displayed. You can revert to your old view by pressing ENTER in the
1228 display filter text box, thereby invoking your old display filter (or
1229 resetting it back to no display filter).
1231 The window in which the data stream is displayed lets you select:
1237 whether to display the entire conversation, or one or the other side of
1242 whether the data being displayed is to be treated as ASCII or EBCDIC
1243 text or as raw hex data;
1247 and lets you print what's currently being displayed, using the same
1248 print options that are used for the I<File:Print Packet> menu item, or
1249 save it as text to a file.
1251 =item Analyze:Follow UDP Stream
1253 =item Analyze:Follow SSL Stream
1255 (Similar to Analyze:Follow TCP Stream)
1257 =item Analyze:Expert Info
1259 =item Analyze:Expert Info Composite
1261 (Kind of) a log of anomalies found by Wireshark in a capture file.
1263 =item Analyze:Conversation Filter
1265 =item Statistics:Summary
1267 Show summary information about the capture, including elapsed time,
1268 packet counts, byte counts, and the like. If a display filter is in
1269 effect, summary information will be shown about the capture and about
1270 the packets currently being displayed.
1272 =item Statistics:Protocol Hierarchy
1274 Show the number of packets, and the number of bytes in those packets,
1275 for each protocol in the trace. It organizes the protocols in the same
1276 hierarchy in which they were found in the trace. Besides counting the
1277 packets in which the protocol exists, a count is also made for packets
1278 in which the protocol is the last protocol in the stack. These
1279 last-protocol counts show you how many packets (and the byte count
1280 associated with those packets) B<ended> in a particular protocol. In
1281 the table, they are listed under "End Packets" and "End Bytes".
1283 =item Statistics:Conversations
1285 Lists of conversations; selectable by protocol. See Statistics:Conversation List below.
1287 =item Statistics:End Points
1289 List of End Point Addresses by protocol with packets/bytes/.... counts.
1291 =item Statistics:Packet Lengths
1293 Grouped counts of packet lengths (0-19 bytes, 20-39 bytes, ...)
1295 =item Statistics:IO Graphs
1297 Open a window where up to 5 graphs in different colors can be displayed
1298 to indicate number of packets or number of bytes per second for all packets
1299 matching the specified filter.
1300 By default only one graph will be displayed showing number of packets per second.
1302 The top part of the window contains the graphs and scales for the X and
1303 Y axis. If the graph is too long to fit inside the window there is a
1304 horizontal scrollbar below the drawing area that can scroll the graphs
1305 to the left or the right. The horizontal axis displays the time into
1306 the capture and the vertical axis will display the measured quantity at
1309 Below the drawing area and the scrollbar are the controls. On the
1310 bottom left there will be five similar sets of controls to control each
1311 individual graph such as "Display:<button>" which button will toggle
1312 that individual graph on/off. If <button> is ticked, the graph will be
1313 displayed. "Color:<color>" which is just a button to show which color
1314 will be used to draw that graph (color is only available in Gtk2
1315 version) and finally "Filter:<filter-text>" which can be used to specify
1316 a display filter for that particular graph.
1318 If filter-text is empty then all packets will be used to calculate the
1319 quantity for that graph. If filter-text is specified only those packets
1320 that match that display filter will be considered in the calculation of
1323 To the right of the 5 graph controls there are four menus to control
1324 global aspects of the draw area and graphs. The "Unit:" menu is used to
1325 control what to measure; "packets/tick", "bytes/tick" or "advanced..."
1327 packets/tick will measure the number of packets matching the (if
1328 specified) display filter for the graph in each measurement interval.
1330 bytes/tick will measure the total number of bytes in all packets matching
1331 the (if specified) display filter for the graph in each measurement
1334 advanced... see below
1336 "Tick interval:" specifies what measurement intervals to use. The
1337 default is 1 second and means that the data will be counted over 1
1340 "Pixels per tick:" specifies how many pixels wide each measurement
1341 interval will be in the drawing area. The default is 5 pixels per tick.
1343 "Y-scale:" controls the max value for the y-axis. Default value is
1344 "auto" which means that B<Wireshark> will try to adjust the maxvalue
1347 "advanced..." If Unit:advanced... is selected the window will display
1348 two more controls for each of the five graphs. One control will be a
1349 menu where the type of calculation can be selected from
1350 SUM,COUNT,MAX,MIN,AVG and LOAD, and one control, textbox, where the name of a
1351 single display filter field can be specified.
1353 The following restrictions apply to type and field combinations:
1355 SUM: available for all types of integers and will calculate the SUM of
1356 all occurrences of this field in the measurement interval. Note that
1357 some field can occur multiple times in the same packet and then all
1358 instances will be summed up. Example: 'tcp.len' which will count the
1359 amount of payload data transferred across TCP in each interval.
1361 COUNT: available for all field types. This will COUNT the number of times
1362 certain field occurs in each interval. Note that some fields
1363 may occur multiple times in each packet and if that is the case
1364 then each instance will be counted independently and COUNT
1365 will be greater than the number of packets.
1367 MAX: available for all integer and relative time fields. This will calculate
1368 the max seen integer/time value seen for the field during the interval.
1369 Example: 'smb.time' which will plot the maximum SMB response time.
1371 MIN: available for all integer and relative time fields. This will calculate
1372 the min seen integer/time value seen for the field during the interval.
1373 Example: 'smb.time' which will plot the minimum SMB response time.
1375 AVG: available for all integer and relative time fields.This will
1376 calculate the average seen integer/time value seen for the field during
1377 the interval. Example: 'smb.time' which will plot the average SMB
1380 LOAD: available only for relative time fields (response times).
1382 Example of advanced:
1383 Display how NFS response time MAX/MIN/AVG changes over time:
1387 filter:nfs&&rpc.time
1392 filter:nfs&&rpc.time
1397 filter:nfs&&rpc.time
1400 Example of advanced:
1401 Display how the average packet size from host a.b.c.d changes over time.
1405 filter:ip.addr==a.b.c.d&&frame.pkt_len
1406 Calc:AVG frame.pkt_len
1409 The LOAD io-stat type is very different from anything you have ever seen
1410 before! While the response times themselves as plotted by MIN,MAX,AVG are
1411 indications on the Server load (which affects the Server response time),
1412 the LOAD measurement measures the Client LOAD.
1413 What this measures is how much workload the client generates,
1414 i.e. how fast will the client issue new commands when the previous ones
1416 i.e. the level of concurrency the client can maintain.
1417 The higher the number, the more and faster is the client issuing new
1418 commands. When the LOAD goes down, it may be due to client load making
1419 the client slower in issuing new commands (there may be other reasons as
1420 well, maybe the client just doesn't have any commands it wants to issue
1423 Load is measured in concurrency/number of overlapping i/o and the value
1424 1000 means there is a constant load of one i/o.
1426 In each tick interval the amount of overlap is measured.
1427 See the graph below containing three commands:
1428 Below the graph are the LOAD values for each interval that would be calculated.
1432 | | o=====* | | | | | |
1434 | o========* | o============* | | |
1436 --------------------------------------------------> Time
1437 500 1500 500 750 1000 500 0 0
1439 =item Statistics:Conversation List
1441 This option will open a new window that displays a list of all
1442 conversations between two endpoints. The list has one row for each
1443 unique conversation and displays total number of packets/bytes seen as
1444 well as number of packets/bytes in each direction.
1446 By default the list is sorted according to the number of packets but by
1447 clicking on the column header; it is possible to re-sort the list in
1448 ascending or descending order by any column.
1450 By first selecting a conversation by clicking on it and then using the
1451 right mouse button (on those platforms that have a right
1452 mouse button) wireshark will display a popup menu offering several different
1453 filter operations to apply to the capture.
1455 These statistics windows can also be invoked from the Wireshark command
1456 line using the B<-z conv> argument.
1458 =item Statistics:Service Response Time
1474 Open a window to display Service Response Time statistics for an
1475 arbitrary DCE-RPC program
1476 interface and display B<Procedure>, B<Number of Calls>, B<Minimum SRT>,
1477 B<Maximum SRT> and B<Average SRT> for all procedures for that
1478 program/version. These windows opened will update in semi-real time to
1479 reflect changes when doing live captures or when reading new capture
1480 files into B<Wireshark>.
1482 This dialog will also allow an optional filter string to be used.
1483 If an optional filter string is used only such DCE-RPC request/response pairs
1484 that match that filter will be used to calculate the statistics. If no filter
1485 string is specified all request/response pairs will be used.
1495 Open a window to display Service Response Time statistics for Fibre Channel
1496 and display B<FC Type>, B<Number of Calls>, B<Minimum SRT>,
1497 B<Maximum SRT> and B<Average SRT> for all FC types.
1498 These windows opened will update in semi-real time to
1499 reflect changes when doing live captures or when reading new capture
1500 files into B<Wireshark>.
1501 The Service Response Time is calculated as the time delta between the
1502 First packet of the exchange and the Last packet of the exchange.
1504 This dialog will also allow an optional filter string to be used.
1505 If an optional filter string is used only such FC first/last exchange pairs
1506 that match that filter will be used to calculate the statistics. If no filter
1507 string is specified all request/response pairs will be used.
1517 Collect requests/response SRT (Service Response Time) data for ITU-T H.225 RAS.
1518 Data collected is B<number of calls> for each known ITU-T H.225 RAS Message Type,
1519 B<Minimum SRT>, B<Maximum SRT>, B<Average SRT>, B<Minimum in Packet>, and B<Maximum in Packet>.
1520 You will also get the number of B<Open Requests> (Unresponded Requests),
1521 B<Discarded Responses> (Responses without matching request) and Duplicate Messages.
1522 These windows opened will update in semi-real time to reflect changes when
1523 doing live captures or when reading new capture files into B<Wireshark>.
1525 You can apply an optional filter string in a dialog box, before starting
1526 the calculation. The statistics will only be calculated
1527 on those calls matching that filter.
1541 Collect requests/response SRT (Service Response Time) data for MGCP.
1542 Data collected is B<number of calls> for each known MGCP Type,
1543 B<Minimum SRT>, B<Maximum SRT>, B<Average SRT>, B<Minimum in Packet>, and B<Maximum in Packet>.
1544 These windows opened will update in semi-real time to reflect changes when
1545 doing live captures or when reading new capture files into B<Wireshark>.
1547 You can apply an optional filter string in a dialog box, before starting
1548 the calculation. The statistics will only be calculated
1549 on those calls matching that filter.
1559 Open a window to display statistics for an arbitrary ONC-RPC program interface
1560 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.
1561 These windows opened will update in semi-real time to reflect changes when
1562 doing live captures or when reading new capture files into B<Wireshark>.
1564 This dialog will also allow an optional filter string to be used.
1565 If an optional filter string is used only such ONC-RPC request/response pairs
1566 that match that filter will be used to calculate the statistics. If no filter
1567 string is specified all request/response pairs will be used.
1569 By first selecting a conversation by clicking on it and then using the
1570 right mouse button (on those platforms that have a right
1571 mouse button) wireshark will display a popup menu offering several different
1572 filter operations to apply to the capture.
1586 Collect call/reply SRT (Service Response Time) data for SMB. Data collected
1587 is the number of calls for each SMB command, MinSRT, MaxSRT and AvgSRT.
1589 The data will be presented as separate tables for all normal SMB commands,
1590 all Transaction2 commands and all NT Transaction commands.
1591 Only those commands that are seen in the capture will have its stats
1593 Only the first command in a xAndX command chain will be used in the
1594 calculation. So for common SessionSetupAndX + TreeConnectAndX chains,
1595 only the SessionSetupAndX call will be used in the statistics.
1596 This is a flaw that might be fixed in the future.
1598 You can apply an optional filter string in a dialog box, before starting
1599 the calculation. The stats will only be calculated
1600 on those calls matching that filter.
1602 By first selecting a conversation by clicking on it and then using the
1603 right mouse button (on those platforms that have a right
1604 mouse button) wireshark will display a popup menu offering several different
1605 filter operations to apply to the capture.
1613 =item Statistics:BOOTP-DHCP
1617 =item Statistics:Compare
1619 Compare two Capture Files
1621 =item Statistics:Flow Graph
1623 Flow Graph: General/TCP
1625 =item Statistics:HTTP
1627 HTTP Load Distribution, Packet Counter & Requests
1629 =item Statistics:IP Addresses
1631 Count/Rate/Percent by IP Address
1633 =item Statistics:IP Destinations
1635 Count/Rate/Percent by IP Address/protocol/port
1637 =item Statistics:IP Protocol Types
1639 Count/Rate/Percent by IP Protocol Types
1641 =item Statistics:ONC-RPC Programs
1643 This dialog will open a window showing aggregated RTT statistics for all
1644 ONC-RPC Programs/versions that exist in the capture file.
1646 =item Statistics:TCP Stream Graph
1648 Graphs: Round Trip; Throughput; Time-Sequence (Stevens); Time-Sequence (tcptrace)
1650 =item Statistics:UDP Multicast streams
1652 Multicast Streams Counts/Rates/... by Source/Destination Address/Port pairs
1654 =item Statistics:WLAN Traffic
1656 WLAN Traffic Statistics
1658 =item Telephony:ITU-T H.225
1660 Count ITU-T H.225 messages and their reasons. In the first column you get a
1661 list of H.225 messages and H.225 message reasons, which occur in the current
1662 capture file. The number of occurrences of each message or reason will be displayed
1663 in the second column.
1664 This window opened will update in semi-real time to reflect changes when
1665 doing live captures or when reading new capture files into B<Wireshark>.
1667 You can apply an optional filter string in a dialog box, before starting
1668 the counter. The statistics will only be calculated
1669 on those calls matching that filter.
1673 Activate a counter for SIP messages. You will get the number of occurrences of each
1674 SIP Method and of each SIP Status-Code. Additionally you also get the number of
1675 resent SIP Messages (only for SIP over UDP).
1677 This window opened will update in semi-real time to reflect changes when
1678 doing live captures or when reading new capture files into B<Wireshark>.
1680 You can apply an optional filter string in a dialog box, before starting
1681 the counter. The statistics will only be calculated
1682 on those calls matching that filter.
1684 =item Tools:Firewall ACL Rules
1692 =item Help:Supported Protocols
1694 List of supported protocols and display filter protocol fields.
1696 =item Help:Manual Pages
1698 Display locally installed HTML versions of these manual pages in a web browser.
1700 =item Help:Wireshark Online
1702 Various links to online resources to be open in a web browser, like
1703 L<http://www.wireshark.org>.
1705 =item Help:About Wireshark
1707 See various information about Wireshark (see L<About|/item_about> dialog below), like the
1708 version, the folders used, the available plugins, ...
1718 The main window contains the usual things like the menu, some toolbars, the
1719 main area and a statusbar. The main area is split into three panes, you can
1720 resize each pane using a "thumb" at the right end of each divider line.
1722 The main window is much more flexible than before. The layout of the main
1723 window can be customized by the I<Layout> page in the dialog box popped
1724 up by I<Edit:Preferences>, the following will describe the layout with the
1731 Some menu items are available for quick access here. There is no way to
1732 customize the items in the toolbar, however the toolbar can be hidden by
1733 I<View:Main Toolbar>.
1735 =item Filter Toolbar
1737 A display filter can be entered into the filter toolbar.
1738 A filter for HTTP, HTTPS, and DNS traffic might look like this:
1740 tcp.port == 80 || tcp.port == 443 || tcp.port == 53
1742 Selecting the I<Filter:> button lets you choose from a list of named
1743 filters that you can optionally save. Pressing the Return or Enter
1744 keys, or selecting the I<Apply> button, will cause the filter to be
1745 applied to the current list of packets. Selecting the I<Reset> button
1746 clears the display filter so that all packets are displayed (again).
1748 There is no way to customize the items in the toolbar, however the toolbar
1749 can be hidden by I<View:Filter Toolbar>.
1751 =item Packet List Pane
1753 The top pane contains the list of network packets that you can scroll
1754 through and select. By default, the packet number, packet timestamp,
1755 source and destination addresses, protocol, and description are
1756 displayed for each packet; the I<Columns> page in the dialog box popped
1757 up by I<Edit:Preferences> lets you change this (although, unfortunately,
1758 you currently have to save the preferences, and exit and restart
1759 Wireshark, for those changes to take effect).
1761 If you click on the heading for a column, the display will be sorted by
1762 that column; clicking on the heading again will reverse the sort order
1765 An effort is made to display information as high up the protocol stack
1766 as possible, e.g. IP addresses are displayed for IP packets, but the
1767 MAC layer address is displayed for unknown packet types.
1769 The right mouse button can be used to pop up a menu of operations.
1771 The middle mouse button can be used to mark a packet.
1773 =item Packet Details Pane
1775 The middle pane contains a display of the details of the
1776 currently-selected packet. The display shows each field and its value
1777 in each protocol header in the stack. The right mouse button can be
1778 used to pop up a menu of operations.
1780 =item Packet Bytes Pane
1782 The lowest pane contains a hex and ASCII dump of the actual packet data.
1783 Selecting a field in the packet details highlights the corresponding
1784 bytes in this section.
1786 The right mouse button can be used to pop up a menu of operations.
1790 The statusbar is divided into three parts, on the left some context dependent
1791 things are shown, like information about the loaded file, in the center the
1792 number of packets are displayed, and on the right the current configuration
1795 The statusbar can be hidden by I<View:Statusbar>.
1801 The I<Preferences> dialog lets you control various personal preferences
1802 for the behavior of B<Wireshark>.
1806 =item User Interface Preferences
1808 The I<User Interface> page is used to modify small aspects of the GUI to
1809 your own personal taste:
1813 =item Selection Bars
1815 The selection bar in the packet list and packet details can have either
1816 a "browse" or "select" behavior. If the selection bar has a "browse"
1817 behavior, the arrow keys will move an outline of the selection bar,
1818 allowing you to browse the rest of the list or details without changing
1819 the selection until you press the space bar. If the selection bar has a
1820 "select" behavior, the arrow keys will move the selection bar and change
1821 the selection to the new item in the packet list or packet details.
1823 =item Save Window Position
1825 If this item is selected, the position of the main Wireshark window will
1826 be saved when Wireshark exits, and used when Wireshark is started again.
1828 =item Save Window Size
1830 If this item is selected, the size of the main Wireshark window will
1831 be saved when Wireshark exits, and used when Wireshark is started again.
1833 =item Save Window Maximized state
1835 If this item is selected the maximize state of the main Wireshark window
1836 will be saved when Wireshark exists, and used when Wireshark is started again.
1838 =item File Open Dialog Behavior
1840 This item allows the user to select how Wireshark handles the listing
1841 of the "File Open" Dialog when opening trace files. "Remember Last
1842 Directory" causes Wireshark to automatically position the dialog in the
1843 directory of the most recently opened file, even between launches of Wireshark.
1844 "Always Open in Directory" allows the user to define a persistent directory
1845 that the dialog will always default to.
1849 Allows the user to specify a persistent File Open directory. Trailing
1850 slashes or backslashes will automatically be added.
1852 =item File Open Preview timeout
1854 This items allows the user to define how much time is spend reading the
1855 capture file to present preview data in the File Open dialog.
1857 =item Open Recent maximum list entries
1859 The File menu supports a recent file list. This items allows the user to
1860 specify how many files are kept track of in this list.
1862 =item Ask for unsaved capture files
1864 When closing a capture file or Wireshark itself if the file isn't saved yet
1865 the user is presented the option to save the file when this item is set.
1867 =item Wrap during find
1869 This items determines the behavior when reaching the beginning or the end
1870 of a capture file. When set the search wraps around and continues, otherwise
1873 =item Settings dialogs show a save button
1875 This item determines if the various dialogs sport an explicit Save button
1876 or that save is implicit in OK / Apply.
1878 =item Web browser command
1880 This entry specifies the command line to launch a web browser. It is used
1881 to access online content, like the Wiki and user guide. Use '%s' to place
1882 the request URL in the command line.
1886 =item Layout Preferences
1888 The I<Layout> page lets you specify the general layout of the main window.
1889 You can choose from six different layouts and fill the three panes with the
1896 The vertical scrollbars in the three panes can be set to be either on
1897 the left or the right.
1899 =item Alternating row colors
1903 The highlight method in the hex dump display for the selected protocol
1904 item can be set to use either inverse video, or bold characters.
1908 =item Filter toolbar placement
1910 =item Custom window title
1914 =item Column Preferences
1916 The I<Columns> page lets you specify the number, title, and format
1917 of each column in the packet list.
1919 The I<Column title> entry is used to specify the title of the column
1920 displayed at the top of the packet list. The type of data that the column
1921 displays can be specified using the I<Column format> option menu.
1922 The row of buttons on the left perform the following actions:
1928 Adds a new column to the list.
1932 Deletes the currently selected list item.
1936 Moves the selected list item up or down one position.
1940 =item Font Preferences
1942 The I<Font> page lets you select the font to be used for most text.
1944 =item Color Preferences
1946 The I<Colors> page can be used to change the color of the text
1947 displayed in the TCP stream window and for marked packets. To change a color,
1948 simply select an attribute from the "Set:" menu and use the color selector to
1949 get the desired color. The new text colors are displayed as a sample text.
1951 =item Capture Preferences
1953 The I<Capture> page lets you specify various parameters for capturing
1954 live packet data; these are used the first time a capture is started.
1956 The I<Interface:> combo box lets you specify the interface from which to
1957 capture packet data, or the name of a FIFO from which to get the packet
1960 The I<Data link type:> option menu lets you, for some interfaces, select
1961 the data link header you want to see on the packets you capture. For
1962 example, in some OSes and with some versions of libpcap, you can choose,
1963 on an 802.11 interface, whether the packets should appear as Ethernet
1964 packets (with a fake Ethernet header) or as 802.11 packets.
1966 The I<Limit each packet to ... bytes> check box lets you set the
1967 snapshot length to use when capturing live data; turn on the check box,
1968 and then set the number of bytes to use as the snapshot length.
1970 The I<Filter:> text entry lets you set a capture filter expression to be
1971 used when capturing.
1973 If any of the environment variables SSH_CONNECTION, SSH_CLIENT,
1974 REMOTEHOST, DISPLAY, or SESSIONNAME are set, Wireshark will create a
1975 default capture filter that excludes traffic from the hosts and ports
1976 defined in those variables.
1978 The I<Capture packets in promiscuous mode> check box lets you specify
1979 whether to put the interface in promiscuous mode when capturing.
1981 The I<Update list of packets in real time> check box lets you specify
1982 that the display should be updated as packets are seen.
1984 The I<Automatic scrolling in live capture> check box lets you specify
1985 whether, in an "Update list of packets in real time" capture, the packet
1986 list pane should automatically scroll to show the most recently captured
1989 =item Printing Preferences
1991 The radio buttons at the top of the I<Printing> page allow you choose
1992 between printing packets with the I<File:Print Packet> menu item as text
1993 or PostScript, and sending the output directly to a command or saving it
1994 to a file. The I<Command:> text entry box, on UNIX-compatible systems,
1995 is the command to send files to (usually B<lpr>), and the I<File:> entry
1996 box lets you enter the name of the file you wish to save to.
1997 Additionally, you can select the I<File:> button to browse the file
1998 system for a particular save file.
2000 =item Name Resolution Preferences
2002 The I<Enable MAC name resolution>, I<Enable network name resolution> and
2003 I<Enable transport name resolution> check boxes let you specify whether
2004 MAC addresses, network addresses, and transport-layer port numbers
2005 should be translated to names.
2007 The I<Enable concurrent DNS name resolution> allows Wireshark to send out
2008 multiple name resolution requests and not wait for the result before
2009 continuing dissection. This speeds up dissection with network name
2010 resolution but initially may miss resolutions. The number of concurrent
2011 requests can be set here as well.
2017 =item RTP Player Preferences
2019 This page allows you to select the number of channels visible in the
2020 RTP player window. It determines the height of the window, more channels
2021 are possible and visible by means of a scroll bar.
2023 =item Protocol Preferences
2025 There are also pages for various protocols that Wireshark dissects,
2026 controlling the way Wireshark handles those protocols.
2030 =item Edit Capture Filter List
2032 =item Edit Display Filter List
2034 =item Capture Filter
2036 =item Display Filter
2042 The I<Edit Capture Filter List> dialog lets you create, modify, and
2043 delete capture filters, and the I<Edit Display Filter List> dialog lets
2044 you create, modify, and delete display filters.
2046 The I<Capture Filter> dialog lets you do all of the editing operations
2047 listed, and also lets you choose or construct a filter to be used when
2050 The I<Display Filter> dialog lets you do all of the editing operations
2051 listed, and also lets you choose or construct a filter to be used to
2052 filter the current capture being viewed.
2054 The I<Read Filter> dialog lets you do all of the editing operations
2055 listed, and also lets you choose or construct a filter to be used to
2056 as a read filter for a capture file you open.
2058 The I<Search Filter> dialog lets you do all of the editing operations
2059 listed, and also lets you choose or construct a filter expression to be
2060 used in a find operation.
2062 In all of those dialogs, the I<Filter name> entry specifies a
2063 descriptive name for a filter, e.g. B<Web and DNS traffic>. The
2064 I<Filter string> entry is the text that actually describes the filtering
2065 action to take, as described above.The dialog buttons perform the
2072 If there is text in the two entry boxes, creates a new associated list
2077 Modifies the currently selected list item to match what's in the entry
2082 Deletes the currently selected list item.
2084 =item Add Expression...
2086 For display filter expressions, pops up a dialog box to allow you to
2087 construct a filter expression to test a particular field; it offers
2088 lists of field names, and, when appropriate, lists from which to select
2089 tests to perform on the field and values with which to compare it. In
2090 that dialog box, the OK button will cause the filter expression you
2091 constructed to be entered into the I<Filter string> entry at the current
2096 In the I<Capture Filter> dialog, closes the dialog box and makes the
2097 filter in the I<Filter string> entry the filter in the I<Capture
2098 Preferences> dialog. In the I<Display Filter> dialog, closes the dialog
2099 box and makes the filter in the I<Filter string> entry the current
2100 display filter, and applies it to the current capture. In the I<Read
2101 Filter> dialog, closes the dialog box and makes the filter in the
2102 I<Filter string> entry the filter in the I<Open Capture File> dialog.
2103 In the I<Search Filter> dialog, closes the dialog box and makes the
2104 filter in the I<Filter string> entry the filter in the I<Find Packet>
2109 Makes the filter in the I<Filter string> entry the current display
2110 filter, and applies it to the current capture.
2114 If the list of filters being edited is the list of
2115 capture filters, saves the current filter list to the personal capture
2116 filters file, and if the list of filters being edited is the list of
2117 display filters, saves the current filter list to the personal display
2122 Closes the dialog without doing anything with the filter in the I<Filter
2127 =item The Color Filters Dialog
2129 This dialog displays a list of color filters and allows it to be
2134 =item THE FILTER LIST
2136 Single rows may be selected by clicking. Multiple rows may be selected
2137 by using the ctrl and shift keys in combination with the mouse button.
2141 Adds a new filter at the bottom of the list and opens the Edit Color
2142 Filter dialog box. You will have to alter the filter expression at
2143 least before the filter will be accepted. The format of color filter
2144 expressions is identical to that of display filters. The new filter is
2145 selected, so it may immediately be moved up and down, deleted or edited.
2146 To avoid confusion all filters are unselected before the new filter is
2151 Opens the Edit Color Filter dialog box for the selected filter. (If this
2152 button is disabled you may have more than one filter selected, making it
2153 ambiguous which is to be edited.)
2157 Enables the selected color filter(s).
2161 Disables the selected color filter(s).
2165 Deletes the selected color filter(s).
2169 Allows you to choose a file in which to save the current list of color
2170 filters. You may also choose to save only the selected filters. A
2171 button is provided to save the filters in the global color filters file
2172 (you must have sufficient permissions to write this file, of course).
2176 Allows you to choose a file containing color filters which are then
2177 added to the bottom of the current list. All the added filters are
2178 selected, so they may be moved to the correct position in the list as a
2179 group. To avoid confusion, all filters are unselected before the new
2180 filters are imported. A button is provided to load the filters from the
2181 global color filters file.
2185 Deletes your personal color filters file, reloads the global
2186 color filters file, if any, and closes the dialog.
2190 Moves the selected filter(s) up the list, making it more likely that
2191 they will be used to color packets.
2195 Moves the selected filter(s) down the list, making it less likely that
2196 they will be used to color packets.
2200 Closes the dialog and uses the color filters as they stand.
2204 Colors the packets according to the current list of color filters, but
2205 does not close the dialog.
2209 Saves the current list of color filters in your personal color filters
2210 file. Unless you do this they will not be used the next time you start
2215 Closes the dialog without changing the coloration of the packets. Note
2216 that changes you have made to the current list of color filters are not
2221 =item Capture Options
2223 The I<Capture Options> dialog lets you specify various parameters for
2224 capturing live packet data.
2226 The I<Interface:> field lets you specify the interface from which to
2227 capture packet data or a command from which to get the packet data via a
2230 The I<Link layer header type:> field lets you specify the interfaces link
2231 layer header type. This field is usually disabled, as most interface have
2232 only one header type.
2234 The I<Capture packets in promiscuous mode> check box lets you specify
2235 whether the interface should be put into promiscuous mode when
2238 The I<Limit each packet to ... bytes> check box and field lets you
2239 specify a maximum number of bytes per packet to capture and save; if the
2240 check box is not checked, the limit will be 65535 bytes.
2242 The I<Capture Filter:> entry lets you specify the capture filter using a
2243 tcpdump-style filter string as described above.
2245 The I<File:> entry lets you specify the file into which captured packets
2246 should be saved, as in the I<Printer Options> dialog above. If not
2247 specified, the captured packets will be saved in a temporary file; you
2248 can save those packets to a file with the I<File:Save As> menu item.
2250 The I<Use multiple files> check box lets you specify that the capture
2251 should be done in "multiple files" mode. This option is disabled, if the
2252 I<Update list of packets in real time> option is checked.
2254 The I<Next file every ... megabyte(s)> check box and fields lets
2255 you specify that a switch to a next file should be done
2256 if the specified filesize is reached. You can also select the appropriate
2257 unit, but beware that the filesize has a maximum of 2 GB.
2258 The check box is forced to be checked, as "multiple files" mode requires a
2259 file size to be specified.
2261 The I<Next file every ... minute(s)> check box and fields lets
2262 you specify that the switch to a next file should be done after the specified
2263 time has elapsed, even if the specified capture size is not reached.
2265 The I<Ring buffer with ... files> field lets you specify the number
2266 of files of a ring buffer. This feature will capture into to the first file
2267 again, after the specified amount of files were used.
2269 The I<Stop capture after ... files> field lets you specify the number
2270 of capture files used, until the capture is stopped.
2272 The I<Stop capture after ... packet(s)> check box and field let
2273 you specify that Wireshark should stop capturing after having captured
2274 some number of packets; if the check box is not checked, Wireshark will
2275 not stop capturing at some fixed number of captured packets.
2277 The I<Stop capture after ... megabyte(s)> check box and field lets
2278 you specify that Wireshark should stop capturing after the file to which
2279 captured packets are being saved grows as large as or larger than some
2280 specified number of megabytes. If the check box is not checked, Wireshark
2281 will not stop capturing at some capture file size (although the operating
2282 system on which Wireshark is running, or the available disk space, may still
2283 limit the maximum size of a capture file). This option is disabled, if
2284 "multiple files" mode is used,
2286 The I<Stop capture after ... second(s)> check box and field let you
2287 specify that Wireshark should stop capturing after it has been capturing
2288 for some number of seconds; if the check box is not checked, Wireshark
2289 will not stop capturing after some fixed time has elapsed.
2291 The I<Update list of packets in real time> check box lets you specify
2292 whether the display should be updated as packets are captured and, if
2293 you specify that, the I<Automatic scrolling in live capture> check box
2294 lets you specify the packet list pane should automatically scroll to
2295 show the most recently captured packets as new packets arrive.
2297 The I<Enable MAC name resolution>, I<Enable network name resolution> and
2298 I<Enable transport name resolution> check boxes let you specify whether
2299 MAC addresses, network addresses, and transport-layer port numbers
2300 should be translated to names.
2304 The I<About> dialog lets you view various information about Wireshark.
2306 =item About:Wireshark
2308 The I<Wireshark> page lets you view general information about Wireshark,
2309 like the installed version, licensing information and such.
2313 The I<Authors> page shows the author and all contributors.
2317 The I<Folders> page lets you view the directory names where Wireshark is
2318 searching it's various configuration and other files.
2322 The I<Plugins> page lets you view the dissector plugin modules
2323 available on your system.
2325 The I<Plugins List> shows the name and version of each dissector plugin
2326 module found on your system.
2328 On Unix-compatible systems, the plugins are looked for in the following
2329 directories: the F<lib/wireshark/plugins/$VERSION> directory under the
2330 main installation directory (for example,
2331 F</usr/local/lib/wireshark/plugins/$VERSION>), and then
2332 F<$HOME/.wireshark/plugins>.
2334 On Windows systems, the plugins are looked for in the following
2335 directories: F<plugins\$VERSION> directory under the main installation
2336 directory (for example, F<C:\Program Files\Wireshark\plugins\$VERSION>),
2337 and then F<%APPDATA%\Wireshark\plugins\$VERSION> (or, if %APPDATA% isn't
2338 defined, F<%USERPROFILE%\Application Data\Wireshark\plugins\$VERSION>).
2340 $VERSION is the version number of the plugin interface, which
2341 is typically the version number of Wireshark. Note that a dissector
2342 plugin module may support more than one protocol; there is not
2343 necessarily a one-to-one correspondence between dissector plugin modules
2344 and protocols. Protocols supported by a dissector plugin module are
2345 enabled and disabled using the I<Edit:Protocols> dialog box, just as
2346 protocols built into Wireshark are.
2350 =head1 CAPTURE FILTER SYNTAX
2352 See the manual page of pcap-filter(4) or, if that doesn't exist, tcpdump(8),
2353 or, if that doesn't exist, L<http://wiki.wireshark.org/CaptureFilters>.
2355 =head1 DISPLAY FILTER SYNTAX
2357 For a complete table of protocol and protocol fields that are filterable
2358 in B<Wireshark> see the wireshark-filter(4) manual page.
2362 These files contains various B<Wireshark> configuration settings.
2368 The F<preferences> files contain global (system-wide) and personal
2369 preference settings. If the system-wide preference file exists, it is
2370 read first, overriding the default settings. If the personal preferences
2371 file exists, it is read next, overriding any previous values. Note: If
2372 the command line flag B<-o> is used (possibly more than once), it will
2373 in turn override values from the preferences files.
2375 The preferences settings are in the form I<prefname>B<:>I<value>,
2377 where I<prefname> is the name of the preference
2378 and I<value> is the value to
2379 which it should be set; white space is allowed between B<:> and
2380 I<value>. A preference setting can be continued on subsequent lines by
2381 indenting the continuation lines with white space. A B<#> character
2382 starts a comment that runs to the end of the line:
2384 # Vertical scrollbars should be on right side?
2385 # TRUE or FALSE (case-insensitive).
2386 gui.scrollbar_on_right: TRUE
2388 The global preferences file is looked for in the F<wireshark> directory
2389 under the F<share> subdirectory of the main installation directory (for
2390 example, F</usr/local/share/wireshark/preferences>) on UNIX-compatible
2391 systems, and in the main installation directory (for example,
2392 F<C:\Program Files\Wireshark\preferences>) on Windows systems.
2394 The personal preferences file is looked for in F<$HOME/.wireshark/preferences> on
2395 UNIX-compatible systems and F<%APPDATA%\Wireshark\preferences> (or, if
2396 %APPDATA% isn't defined, F<%USERPROFILE%\Application
2397 Data\Wireshark\preferences>) on Windows systems.
2399 Note: Whenever the preferences are saved by using the I<Save> button
2400 in the I<Edit:Preferences> dialog box, your personal preferences file
2401 will be overwritten with the new settings, destroying any comments and
2402 unknown/obsolete settings that were in the file.
2406 The F<recent> file contains personal settings (mostly GUI related) such
2407 as the current B<Wireshark> window size. The file is saved at program exit and
2408 read in at program start automatically. Note: The command line flag B<-o>
2409 may be used to override settings from this file.
2411 The settings in this file have the same format as in the F<preferences>
2412 files, and the same directory as for the personal preferences file is
2415 Note: Whenever Wireshark is closed, your recent file
2416 will be overwritten with the new settings, destroying any comments and
2417 unknown/obsolete settings that were in the file.
2419 =item Disabled (Enabled) Protocols
2421 The F<disabled_protos> files contain system-wide and personal lists of
2422 protocols that have been disabled, so that their dissectors are never
2423 called. The files contain protocol names, one per line, where the
2424 protocol name is the same name that would be used in a display filter
2430 If a protocol is listed in the global F<disabled_protos> file, it is not
2431 displayed in the I<Analyze:Enabled Protocols> dialog box, and so cannot
2432 be enabled by the user.
2434 The global F<disabled_protos> file uses the same directory as the global
2437 The personal F<disabled_protos> file uses the same directory as the
2438 personal preferences file.
2440 Note: Whenever the disabled protocols list is saved by using the I<Save>
2441 button in the I<Analyze:Enabled Protocols> dialog box, your personal
2442 disabled protocols file will be overwritten with the new settings,
2443 destroying any comments that were in the file.
2445 =item Name Resolution (hosts)
2447 If the personal F<hosts> file exists, it is
2448 used to resolve IPv4 and IPv6 addresses before any other
2449 attempts are made to resolve them. The file has the standard F<hosts>
2450 file syntax; each line contains one IP address and name, separated by
2451 whitespace. The same directory as for the personal preferences file is used.
2453 Capture filter name resolution is handled by libpcap on UNIX-compatible
2454 systems and WinPCAP on Windows. As such the Wireshark personal F<hosts> file
2455 will not be consulted for capture filter name resolution.
2457 =item Name Resolution (ethers)
2459 The F<ethers> files are consulted to correlate 6-byte hardware addresses to
2460 names. First the personal F<ethers> file is tried and if an address is not
2461 found there the global F<ethers> file is tried next.
2463 Each line contains one hardware address and name, separated by
2464 whitespace. The digits of the hardware address are separated by colons
2465 (:), dashes (-) or periods (.). The same separator character must be
2466 used consistently in an address. The following three lines are valid
2467 lines of an F<ethers> file:
2469 ff:ff:ff:ff:ff:ff Broadcast
2470 c0-00-ff-ff-ff-ff TR_broadcast
2471 00.00.00.00.00.00 Zero_broadcast
2473 The global F<ethers> file is looked for in the F</etc> directory on
2474 UNIX-compatible systems, and in the main installation directory (for
2475 example, F<C:\Program Files\Wireshark>) on Windows systems.
2477 The personal F<ethers> file is looked for in the same directory as the personal
2480 Capture filter name resolution is handled by libpcap on UNIX-compatible
2481 systems and WinPCAP on Windows. As such the Wireshark personal F<ethers> file
2482 will not be consulted for capture filter name resolution.
2484 =item Name Resolution (manuf)
2486 The F<manuf> file is used to match the 3-byte vendor portion of a 6-byte
2487 hardware address with the manufacturer's name; it can also contain well-known
2488 MAC addresses and address ranges specified with a netmask. The format of the
2489 file is the same as the F<ethers> files, except that entries such as:
2493 can be provided, with the 3-byte OUI and the name for a vendor, and
2496 00-00-0C-07-AC/40 All-HSRP-routers
2498 can be specified, with a MAC address and a mask indicating how many bits
2499 of the address must match. The above entry, for example, has 40
2500 significant bits, or 5 bytes, and would match addresses from
2501 00-00-0C-07-AC-00 through 00-00-0C-07-AC-FF. The mask need not be a
2504 The F<manuf> file is looked for in the same directory as the global
2507 =item Name Resolution (ipxnets)
2509 The F<ipxnets> files are used to correlate 4-byte IPX network numbers to
2510 names. First the global F<ipxnets> file is tried and if that address is not
2511 found there the personal one is tried next.
2513 The format is the same as the F<ethers>
2514 file, except that each address is four bytes instead of six.
2515 Additionally, the address can be represented as a single hexadecimal
2516 number, as is more common in the IPX world, rather than four hex octets.
2517 For example, these four lines are valid lines of an F<ipxnets> file:
2521 00:00:BE:EF IT_Server1
2524 The global F<ipxnets> file is looked for in the F</etc> directory on
2525 UNIX-compatible systems, and in the main installation directory (for
2526 example, F<C:\Program Files\Wireshark>) on Windows systems.
2528 The personal F<ipxnets> file is looked for in the same directory as the
2529 personal preferences file.
2531 =item Capture Filters
2533 The F<cfilters> files contain system-wide and personal capture filters.
2534 Each line contains one filter, starting with the string displayed in the
2535 dialog box in quotation marks, followed by the filter string itself:
2540 The global F<cfilters> file uses the same directory as the
2541 global preferences file.
2543 The personal F<cfilters> file uses the same directory as the personal
2544 preferences file. It is written through the Capture:Capture Filters
2547 If the global F<cfilters> file exists, it is used only if the personal
2548 F<cfilters> file does not exist; global and personal capture filters are
2551 =item Display Filters
2553 The F<dfilters> files contain system-wide and personal display filters.
2554 Each line contains one filter, starting with the string displayed in the
2555 dialog box in quotation marks, followed by the filter string itself:
2560 The global F<dfilters> file uses the same directory as the
2561 global preferences file.
2563 The personal F<dfilters> file uses the same directory as the
2564 personal preferences file. It is written through the Analyze:Display
2567 If the global F<dfilters> file exists, it is used only if the personal
2568 F<dfilters> file does not exist; global and personal display filters are
2571 =item Color Filters (Coloring Rules)
2573 The F<colorfilters> files contain system-wide and personal color filters.
2574 Each line contains one filter, starting with the string displayed in the
2575 dialog box, followed by the corresponding display filter. Then the
2576 background and foreground colors are appended:
2579 @tcp@tcp@[59345,58980,65534][0,0,0]
2580 @udp@udp@[28834,57427,65533][0,0,0]
2582 The global F<colorfilters> file uses the same directory as the
2583 global preferences file.
2585 The personal F<colorfilters> file uses the same directory as the
2586 personal preferences file. It is written through the View:Coloring Rules
2589 If the global F<colorfilters> file exists, it is used only if the personal
2590 F<colorfilters> file does not exist; global and personal color filters are
2595 The F<gtkrc> files contain system-wide and personal GTK theme settings.
2597 The global F<gtkrc> file uses the same directory as the
2598 global preferences file.
2600 The personal F<gtkrc> file uses the same directory as the personal
2605 See above in the description of the About:Plugins page.
2609 =head1 ENVIRONMENT VARIABLES
2613 =item WIRESHARK_DEBUG_EP_NO_CHUNKS
2615 Normally per-packet memory is allocated in large "chunks." This behavior
2616 doesn't work well with debugging tools such as Valgrind or ElectricFence.
2617 Export this environment variable to force individual allocations.
2618 Note: disabling chunks also disables canaries (see below).
2620 =item WIRESHARK_DEBUG_SE_NO_CHUNKS
2622 Normally per-file memory is allocated in large "chunks." This behavior
2623 doesn't work well with debugging tools such as Valgrind or ElectricFence.
2624 Export this environment variable to force individual allocations.
2625 Note: disabling chunks also disables canaries (see below).
2627 =item WIRESHARK_DEBUG_EP_NO_CANARY
2629 Normally per-packet memory allocations are separated by "canaries" which
2630 allow detection of memory overruns. This comes at the expense of some extra
2631 memory usage. Exporting this environment variable disables these canaries.
2633 =item WIRESHARK_DEBUG_SE_USE_CANARY
2635 Exporting this environment variable causes per-file memory allocations to be
2636 protected with "canaries" which allow for detection of memory overruns.
2637 This comes at the expense of significant extra memory usage.
2639 =item WIRESHARK_DEBUG_SCRUB_MEMORY
2641 If this environment variable is exported, the contents of per-packet and
2642 per-file memory is initialized to 0xBADDCAFE when the memory is allocated
2643 and is reset to 0xDEADBEEF when the memory is freed. This functionality is
2644 useful mainly to developers looking for bugs in the way memory is handled.
2646 =item WIRESHARK_RUN_FROM_BUILD_DIRECTORY
2648 This environment variable causes the plugins and other data files to be loaded
2649 from the build directory (where the program was compiled) rather than from the
2650 standard locations. It has no effect when the program in question is running
2651 with root (or setuid) permissions on *NIX.
2653 =item WIRESHARK_DATA_DIR
2655 This environment variable causes the various data files to be loaded from
2656 a directory other than the standard locations. It has no effect when the
2657 program in question is running with root (or setuid) permissions on *NIX.
2659 =item WIRESHARK_PYTHON_DIR
2661 This environment variable points to an alternate location for Python.
2662 It has no effect when the program in question is running with root (or setuid)
2663 permissions on *NIX.
2665 =item ERF_RECORDS_TO_CHECK
2667 This environment variable controls the number of ERF records checked when
2668 deciding if a file really is in the ERF format. Setting this environment
2669 variable a number higher than the default (20) would make false positives
2672 =item IPFIX_RECORDS_TO_CHECK
2674 This environment variable controls the number of IPFIX records checked when
2675 deciding if a file really is in the IPFIX format. Setting this environment
2676 variable a number higher than the default (20) would make false positives
2679 =item WIRESHARK_ABORT_ON_DISSECTOR_BUG
2681 If this environment variable is set, B<Wireshark> will call abort(3)
2682 when a dissector bug is encountered. abort(3) will cause the program to
2683 exit abnormally; if you are running B<Wireshark> in a debugger, it
2684 should halt in the debugger and allow inspection of the process, and, if
2685 you are not running it in a debugger, it will, on some OSes, assuming
2686 your environment is configured correctly, generate a core dump file.
2687 This can be useful to developers attempting to troubleshoot a problem
2688 with a protocol dissector.
2690 =item WIRESHARK_EP_VERIFY_POINTERS
2692 This environment variable, if exported, causes certain uses of pointers to be
2693 audited to ensure they do not point to memory that is deallocated after each
2694 packet has been fully dissected. This can be useful to developers writing or
2697 =item WIRESHARK_SE_VERIFY_POINTERS
2699 This environment variable, if exported, causes certain uses of pointers to be
2700 audited to ensure they do not point to memory that is deallocated after when
2701 a capture file is closed. This can be useful to developers writing or
2708 wireshark-filter(4), tshark(1), editcap(1), pcap-filter(4), tcpdump(8),
2709 pcap(3), dumpcap(1), mergecap(1), text2pcap(1)
2713 The latest version of B<Wireshark> can be found at
2714 L<http://www.wireshark.org>.
2716 HTML versions of the Wireshark project man pages are available at:
2717 L<http://www.wireshark.org/docs/man-pages>.