Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or any later
version published by the Free Software Foundation.
All logos and trademarks in this document are property of their respective owner.
Preface ............................................................................................................................ ix
1. Foreword .............................................................................................................. ix
2. Who should read this document? .............................................................................. ix
3. Acknowledgements ................................................................................................ ix
4. About this document ............................................................................................... x
5. Where to get the latest copy of this document? ............................................................. x
6. Providing feedback about this document ..................................................................... x
E. This Document's License (GPL) .................................................................................... 240
viii
Preface
1. Foreword
Wireshark is one of those programs that many network managers would love to be able to use, but they are
often prevented from getting what they would like from Wireshark because of the lack of documentation.
This document is part of an effort by the Wireshark team to improve the usability of Wireshark.
We hope that you find it useful, and look forward to your comments.
2. Who should read this document?
The intended audience of this book is anyone using Wireshark.
This book will explain all the basics and also some of the advanced features that Wireshark provides. As
Wireshark has become a very complex program since the early days, not every feature of Wireshark may
be explained in this book.
This book is not intended to explain network sniffing in general and it will not provide details about specific
network protocols. A lot of useful information regarding these topics can be found at the Wireshark Wiki
at http://wiki.wireshark.org
By reading this book, you will learn how to install Wireshark, how to use the basic elements of the graphical
user interface (such as the menu) and what's behind some of the advanced features that are not always
obvious at first sight. It will hopefully guide you around some common problems that frequently appear
for new (and sometimes even advanced) users of Wireshark.
3. Acknowledgements
The authors would like to thank the whole Wireshark team for their assistance. In particular, the authors
would like to thank:
• Gerald Combs, for initiating the Wireshark project and funding to do this documentation.
• Guy Harris, for many helpful hints and a great deal of patience in reviewing this document.
• Gilbert Ramirez, for general encouragement and helpful hints along the way.
The authors would also like to thank the following people for their helpful feedback on this document:
• Pat Eyler, for his suggestions on improving the example on generating a backtrace.
• Martin Regner, for his various suggestions and corrections.
• Graeme Hewson, for a lot of grammatical corrections.
The authors would like to acknowledge those man page and README authors for the Wireshark project
from who sections of this document borrow heavily:
• Scott Renfro from whose mergecap man page Section D.8, “mergecap: Merging multiple capture files
into one ” is derived.
ix
Preface
• Ashok Narayanan from whose text2pcap man page Section D.9, “text2pcap: Converting ASCII
hexdumps to network captures ” is derived.
• Frank Singleton from whose README.idl2wrsSection D.10, “idl2wrs: Creating dissectors from
CORBA IDL files ” is derived.
4. About this document
This book was originally developed by Richard Sharpe with funds provided from the Wireshark Fund. It
was updated by Ed Warnicke and more recently redesigned and updated by Ulf Lamping.
It is written in DocBook/XML.
You will find some specially marked parts in this book:
This is a warning!
You should pay attention to a warning, as otherwise data loss might occur.
This is a note!
A note will point you to common mistakes and things that might not be obvious.
This is a tip!
Tips will be helpful for your everyday work using Wireshark.
5. Where to get the latest copy of this
document?
The latest copy of this documentation can always be found at: http://www.wireshark.org/docs/.
6. Providing feedback about this document
Should you have any feedback about this document, please send it to the authors through wireshark-
dev[AT]wireshark.org.
x
Chapter 1. Introduction
1.1. What is Wireshark?
Wireshark is a network packet analyzer. A network packet analyzer will try to capture network packets
and tries to display that packet data as detailed as possible.
You could think of a network packet analyzer as a measuring device used to examine what's going on
inside a network cable, just like a voltmeter is used by an electrician to examine what's going on inside
an electric cable (but at a higher level, of course).
In the past, such tools were either very expensive, proprietary, or both. However, with the advent of
Wireshark, all that has changed.
Wireshark is perhaps one of the best open source packet analyzers available today.
1.1.1. Some intended purposes
Here are some examples people use Wireshark for:
• network administrators use it to troubleshoot network problems
• network security engineers use it to examine security problems
• developers use it to debug protocol implementations
• people use it to learn network protocol internals
Beside these examples, Wireshark can be helpful in many other situations too.
1.1.2. Features
The following are some of the many features Wireshark provides:
• Available for UNIX and Windows.
• Capture live packet data from a network interface.
• Display packets with very detailed protocol information.
• Open and Save packet data captured.
• Import and Export packet data from and to a lot of other capture programs.
• Filter packets on many criteria.
• Search for packets on many criteria.
• Colorize packet display based on filters.
• Create various statistics.
• ... and a lot more!
However, to really appreciate its power, you have to start using it.
1
Introduction
Figure 1.1, “ Wireshark captures packets and allows you to examine their content. ” shows Wireshark
having captured some packets and waiting for you to examine them.
Figure 1.1. Wireshark captures packets and allows you to examine their content.
1.1.3. Live capture from many different network media
Wireshark can capture traffic from many different network media types - and despite its name - including
wireless LAN as well. Which media types are supported, depends on many things like the operating
system you are using. An overview of the supported media types can be found at: http://wiki.wireshark.org/
CaptureSetup/NetworkMedia.
1.1.4. Import files from many other capture programs
Wireshark can open packets captured from a large number of other capture programs. For a list of input
formats see Section 5.2.2, “Input File Formats”.
1.1.5. Export files for many other capture programs
Wireshark can save packets captured in a large number of formats of other capture programs. For a list of
output formats see Section 5.3.2, “Output File Formats”.
1.1.6. Many protocol decoders
There are protocol decoders (or dissectors, as they are known in Wireshark) for a great many protocols:
see Appendix B, Protocols and Protocol Fields.
2
Introduction
1.1.7. Open Source Software
Wireshark is an open source software project, and is released under the GNU General Public License
(GPL). You can freely use Wireshark on any number of computers you like, without worrying about license
keys or fees or such. In addition, all source code is freely available under the GPL. Because of that, it is
very easy for people to add new protocols to Wireshark, either as plugins, or built into the source, and
they often do!
1.1.8. What Wireshark is not
Here are some things Wireshark does not provide:
• Wireshark isn't an intrusion detection system. It will not warn you when someone does strange things
on your network that he/she isn't allowed to do. However, if strange things happen, Wireshark might
help you figure out what is really going on.
• Wireshark will not manipulate things on the network, it will only "measure" things from it. Wireshark
doesn't send packets on the network or do other active things (except for name resolutions, but even
that can be disabled).
1.2. System Requirements
What you'll need to get Wireshark up and running ...
1.2.1. General Remarks
• The values below are the minimum requirements and only "rules of thumb" for use on a moderately
used network
• Working with a busy network can easily produce huge memory and disk space usage! For example:
Capturing on a fully saturated 100MBit/s Ethernet will produce ~ 750MBytes/min! Having a fast
processor, lots of memory and disk space is a good idea in that case.
• If Wireshark is running out of memory it crashes, see: http://wiki.wireshark.org/KnownBugs/
OutOfMemory for details and workarounds
• Wireshark won't benefit much from Multiprocessor/Hyperthread systems as time consuming tasks like
filtering packets are single threaded. No rule is without exception: during an "Update list of packets in
real time" capture, capturing traffic runs in one process and dissecting and displaying packets runs in
another process - which should benefit from two processors.
1.2.2. Microsoft Windows
• Windows XP Home, XP Pro, XP Tablet PC, XP Media Center, Server 2003, Vista, 2008, 7, or 2008 R2
• Any modern 32-bit x86 or 64-bit AMD64/x86-64 processor.
• 128MB available RAM. Larger capture files require more RAM.
• 75MB available disk space. Capture files require additional disk space.
• 800*600 (1280*1024 or higher recommended) resolution with at least 65536 (16bit) colors (256 colors
should work if Wireshark is installed with the "legacy GTK1" selection of the Wireshark 1.0.x releases)
3
Introduction
• A supported network card for capturing:
• Ethernet: Any card supported by Windows should work. See the wiki pages on Ethernet capture and
offloading for issues that may affect your environment.
• 802.11: See the Wireshark wiki page. Capturing raw 802.11 information may be difficult without
special equipment.
• Other media: See http://wiki.wireshark.org/CaptureSetup/NetworkMedia
Remarks:
• Many older Windows versions are no longer supported for three reasons: None of the developers use
those systems which makes support difficult. The libraries Wireshark depends on (GTK, WinPcap, …)
have dropped support for older releases. Microsoft has also dropped support for these systems.
• Windows 95, 98 and ME are no longer supported. The "old technology" releases of Windows lack
memory protection (specifically VirtualProtect) which we use to improve program safety and security.
The last known version to work was Ethereal 0.10.14 (which includes WinPcap 3.1). You can get it
from http://ethereal.com/download.html. According to this bug report, you may need to install Ethereal
0.10.0 on some systems.
Microsoft retired support for Windows 98 and ME in 2006.
• Windows NT 4.0 no longer works with Wireshark. The last known version to work was Wireshark
0.99.4 (which includes WinPcap 3.1). You still can get it from http://www.wireshark.org/download/
win32/all-versions/wireshark-setup-0.99.4.exe.
Microsoft retired support for Windows NT 4.0 in 2004.
• Windows 2000 no longer works with Wireshark. The last known version to work was Wireshark 1.2.x
(which includes WinPcap 4.1.2). You still can get it from http://www.wireshark.org/download/win32/
all-versions/.
Microsoft retired support for Windows 2000 in 2010.
• Windows CE and the embedded versions of Windows are not currently supported.
• Multiple monitor setups are supported but may behave a bit strangely.
1.2.3. Unix / Linux
Wireshark currently runs on most UNIX platforms. The system requirements should be comparable to the
Windows values listed above.
Binary packages are available for at least the following platforms:
• Apple Mac OS X
• Debian GNU/Linux
• FreeBSD
• Gentoo Linux
• HP-UX
• Mandriva Linux
4
Introduction
• NetBSD
• OpenPKG
• Red Hat Enterprise/Fedora Linux
• rPath Linux
• Sun Solaris/i386
• Sun Solaris/Sparc
• Canonical Ubuntu
If a binary package is not available for your platform, you should download the source and try to build it.
Please report your experiences to wireshark-dev[AT]wireshark.org .
1.3. Where to get Wireshark?
You can get the latest copy of the program from the Wireshark website: http://www.wireshark.org/
download.html. The website allows you to choose from among several mirrors for downloading.
A new Wireshark version will typically become available every 4-8 months.
If you want to be notified about new Wireshark releases, you should subscribe to the wireshark-announce
mailing list. You will find more details in Section 1.6.5, “Mailing Lists”.
1.4. A brief history of Wireshark
In late 1997, Gerald Combs needed a tool for tracking down networking problems and wanted to learn
more about networking, so he started writing Ethereal (the former name of the Wireshark project) as a
way to solve both problems.
Ethereal was initially released, after several pauses in development, in July 1998 as version 0.2.0. Within
days, patches, bug reports, and words of encouragement started arriving, so Ethereal was on its way to
success.
Not long after that, Gilbert Ramirez saw its potential and contributed a low-level dissector to it.
In October, 1998, Guy Harris of Network Appliance was looking for something better than tcpview, so he
started applying patches and contributing dissectors to Ethereal.
In late 1998, Richard Sharpe, who was giving TCP/IP courses, saw its potential on such courses, and started
looking at it to see if it supported the protocols he needed. While it didn't at that point, new protocols could
be easily added. So he started contributing dissectors and contributing patches.
The list of people who have contributed to the project has become very long since then, and almost all of
them started with a protocol that they needed that Wireshark or Ethereal did not already handle. So they
copied an existing dissector and contributed the code back to the team.
In 2006 the project moved house and re-emerged under a new name: Wireshark.
In 2008, after ten years of development, Wireshark finally arrived at version 1.0. This release was the first
deemed complete, with the minimum features implemented. Its release coincided with the first Wireshark
Developer and User Conference, called SharkFest.
5
Introduction
1.5. Development and maintenance of
Wireshark
Wireshark was initially developed by Gerald Combs. Ongoing development and maintenance of Wireshark
is handled by the Wireshark team, a loose group of individuals who fix bugs and provide new functionality.
There have also been a large number of people who have contributed protocol dissectors to Wireshark,
and it is expected that this will continue. You can find a list of the people who have contributed code to
Wireshark by checking the about dialog box of Wireshark, or at the authors page on the Wireshark web site.
Wireshark is an open source software project, and is released under the GNU General Public License
(GPL). All source code is freely available under the GPL. You are welcome to modify Wireshark to suit
your own needs, and it would be appreciated if you contribute your improvements back to the Wireshark
team.
You gain three benefits by contributing your improvements back to the community:
• Other people who find your contributions useful will appreciate them, and you will know that you have
helped people in the same way that the developers of Wireshark have helped people.
• The developers of Wireshark might improve your changes even more, as there's always room for
improvement. Or they may implement some advanced things on top of your code, which can be useful
for yourself too.
• The maintainers and developers of Wireshark will maintain your code as well, fixing it when API
changes or other changes are made, and generally keeping it in tune with what is happening with
Wireshark. So if Wireshark is updated (which is done often), you can get a new Wireshark version from
the website and your changes will already be included without any effort for you.
The Wireshark source code and binary kits for some platforms are all available on the download page of
the Wireshark website: http://www.wireshark.org/download.html.
1.6. Reporting problems and getting help
If you have problems, or need help with Wireshark, there are several places that may be of interest to you
(well, besides this guide of course).
1.6.1. Website
You will find lots of useful information on the Wireshark homepage at http://www.wireshark.org.
1.6.2. Wiki
The Wireshark Wiki at http://wiki.wireshark.org provides a wide range of information related to Wireshark
and packet capturing in general. You will find a lot of information not part of this user's guide. For example,
there is an explanation how to capture on a switched network, an ongoing effort to build a protocol
reference and a lot more.
And best of all, if you would like to contribute your knowledge on a specific topic (maybe a network
protocol you know well), you can edit the wiki pages by simply using your web browser.
6
1.6.3. Q&A Forum
The Wireshark Q and A forum at http://ask.wireshark.org offers a resource where questions and answers
come together. You have the option to search what questions were asked before and what answers were
given by people who knew about the issue. Answers are graded, so you can pick out the best ones easily.
If your issue isn't discussed before you can post one yourself.
1.6.4. FAQ
The "Frequently Asked Questions" will list often asked questions and the corresponding answers.
Read the FAQ!
Before sending any mail to the mailing lists below, be sure to read the FAQ, as it will often
answer the question(s) you might have. This will save yourself and others a lot of time (keep
in mind that a lot of people are subscribed to the mailing lists).
You will find the FAQ inside Wireshark by clicking the menu item Help/Contents and selecting the FAQ
page in the dialog shown.
An online version is available at the Wireshark website: http://www.wireshark.org/faq.html. You might
prefer this online version, as it's typically more up to date and the HTML format is easier to use.
Introduction
1.6.5. Mailing Lists
There are several mailing lists of specific Wireshark topics available:
wireshark-announceThis mailing list will inform you about new program releases, which usually
appear about every 4-8 weeks.
wireshark-usersThis list is for users of Wireshark. People post questions about building and
using Wireshark, others (hopefully) provide answers.
wireshark-devThis list is for Wireshark developers. If you want to start developing a
protocol dissector, join this list.
You can subscribe to each of these lists from the Wireshark web site: http://www.wireshark.org. Simply
select the mailing lists link on the left hand side of the site. The lists are archived at the Wireshark web
site as well.
Tip!
You can search in the list archives to see if someone asked the same question some time
before and maybe already got an answer. That way you don't have to wait until someone
answers your question.
1.6.6. Reporting Problems
Note!
Before reporting any problems, please make sure you have installed the latest version of
Wireshark.
When reporting problems with Wireshark, it is helpful if you supply the following information:
7
Introduction
1. The version number of Wireshark and the dependent libraries linked with it, e.g. GTK+, etc. You can
obtain this from the about dialog box of Wireshark, or with the command wireshark -v.
2. Information about the platform you run Wireshark on.
3. A detailed description of your problem.
4. If you get an error/warning message, copy the text of that message (and also a few lines before and after
it, if there are some), so others may find the place where things go wrong. Please don't give something
like: "I get a warning while doing x" as this won't give a good idea where to look at.
Don't send large files!
Do not send large files (>100KB) to the mailing lists, just place a note that further data
is available on request. Large files will only annoy a lot of people on the list who are not
interested in your specific problem. If required, you will be asked for further data by the
persons who really can help you.
Don't send confidential information!
If you send captured data to the mailing lists, be sure they don't contain any sensitive or
confidential information like passwords or such.
1.6.7. Reporting Crashes on UNIX/Linux platforms
When reporting crashes with Wireshark, it is helpful if you supply the traceback information (besides the
information mentioned in "Reporting Problems").
You can obtain this traceback information with the following commands:
Type the characters in the first line verbatim! Those are back-tics there!
Note
backtrace is a gdb command. You should enter it verbatim after the first line shown above,
but it will not be echoed. The ^D (Control-D, that is, press the Control key and the D key
together) will cause gdb to exit. This will leave you with a file called bt.txt in the current
directory. Include the file with your bug report.
Note
If you do not have gdb available, you will have to check out your operating system's
debugger.
You should mail the traceback to the wireshark-dev[AT]wireshark.org mailing list.
8
Introduction
1.6.8. Reporting Crashes on Windows platforms
The Windows distributions don't contain the symbol files (.pdb), because they are very large. For this
reason it's not possible to create a meaningful backtrace file from it. You should report your crash just like
other problems, using the mechanism described above.
9
Chapter 2. Building and Installing
Wireshark
2.1. Introduction
As with all things, there must be a beginning, and so it is with Wireshark. To use Wireshark, you must:
• Obtain a binary package for your operating system, or
• Obtain the source and build Wireshark for your operating system.
Currently, several Linux distributions ship Wireshark, but they are commonly shipping an out-of-date
version. No other versions of UNIX ship Wireshark so far, and Microsoft does not ship it with any version
of Windows. For that reason, you will need to know where to get the latest version of Wireshark and how
to install it.
This chapter shows you how to obtain source and binary packages, and how to build Wireshark from
source, should you choose to do so.
The following are the general steps you would use:
1. Download the relevant package for your needs, e.g. source or binary distribution.
2. Build the source into a binary, if you have downloaded the source.
This may involve building and/or installing other necessary packages.
3. Install the binaries into their final destinations.
2.2. Obtaining the source and binary
distributions
You can obtain both source and binary distributions from the Wireshark web site: http://
www.wireshark.org. Simply select the download link, and then select either the source package or binary
package of your choice from the mirror site closest to you.
Download all required files!
In general, unless you have already downloaded Wireshark before, you will most likely need
to download several source packages if you are building Wireshark from source. This is
covered in more detail below.
Once you have downloaded the relevant files, you can go on to the next step.
Note!
While you will find a number of binary packages available on the Wireshark web site, you
might not find one for your platform, and they often tend to be several versions behind the
10
Building and Installing Wireshark
current released version, as they are contributed by people who have the platforms they are
built for.
For this reason, you might want to pull down the source distribution and build it, as the
process is relatively simple.
2.3. Before you build Wireshark under UNIX
Before you build Wireshark from sources, or install a binary package, you must ensure that you have the
following other packages installed:
• GTK+, The GIMP Tool Kit.
You will also need Glib. Both can be obtained from www.gtk.org
• libpcap, the packet capture software that Wireshark uses.
You can obtain libpcap from www.tcpdump.org
Depending on your system, you may be able to install these from binaries, e.g. RPMs, or you may need
to obtain them in source code form and build them.
If you have downloaded the source for GTK+, the instructions shown in Example 2.1, “Building GTK+
from source” may provide some help in building it:
Example 2.1. Building GTK+ from source
gzip -dc gtk+-2.21.1.tar.gz | tar xvf <much output removed>
cd gtk+-2.21.1
./configure
<much output removed>
make
<much output removed>
make install
<much output removed>
Note!
You may need to change the version number of GTK+ in Example 2.1, “Building GTK+
from source” to match the version of GTK+ you have downloaded. The directory you change
to will change if the version of GTK+ changes, and in all cases, tar xvf - will show you the
name of the directory you should change to.
Note!
If you use Linux, or have GNU tar installed, you can use tar zxvf gtk+-2.21.1.tar.gz. It is
also possible to use gunzip -c or gzcat rather than gzip -dc on many UNIX systems.
Note!
If you downloaded GTK+ or any other tar file using Windows, you may find your file called
gtk+-2_21_1_tar.gz.
11
Building and Installing Wireshark
You should consult the GTK+ web site if any errors occur in carrying out the instructions in Example 2.1,
“Building GTK+ from source”.
If you have downloaded the source to libpcap, the general instructions shown in Example 2.2, “Building
and installing libpcap” will assist in building it. Also, if your operating system does not support tcpdump,
you might also want to download it from the tcpdump web site and install it.
Example 2.2. Building and installing libpcap
gzip -dc libpcap-1.0.0.tar.Z | tar xvf <much output removed>
cd libpcap-1.0.0
./configure
<much output removed>
make
<much output removed>
make install
<much output removed>
Note!
The directory you should change to will depend on the version of libpcap you have
downloaded. In all cases, tar xvf - will show you the name of the directory that has been
unpacked.
Under Red Hat 6.x and beyond (and distributions based on it, like Mandrake) you can simply install each of
the packages you need from RPMs. Most Linux systems will install GTK+ and GLib in any case, however
you will probably need to install the devel versions of each of these packages. The commands shown in
Example 2.3, “ Installing required RPMs under Red Hat Linux 6.2 and beyond ” will install all the needed
RPMs if they are not already installed.
Example 2.3. Installing required RPMs under Red Hat Linux 6.2 and beyond
If you are using a version of Red Hat later than 6.2, the required RPMs have most likely
changed. Simply use the correct RPMs from your distribution.
Under Debian you can install Wireshark using aptitude. aptitude will handle any dependency issues for
you. Example 2.4, “Installing debs under Debian, Ubuntu and other Debian derivatives” shows how to
do this.
Example 2.4. Installing debs under Debian, Ubuntu and other Debian derivatives
aptitude install wireshark-dev
12
Building and Installing Wireshark
2.4. Building Wireshark from source under
UNIX
Use the following general steps if you are building Wireshark from source under a UNIX operating system:
1. Unpack the source from its gzip'd tar file. If you are using Linux, or your version of UNIX uses GNU
tar, you can use the following command:
tar zxvf wireshark-1.9-tar.gz
For other versions of UNIX, you will want to use the following commands:
gzip -d wireshark-1.9-tar.gz
tar xvf wireshark-1.9-tar
Note!
The pipeline gzip -dc wireshark-1.9-tar.gz | tar xvf - will work here as well.
Note!
If you have downloaded the Wireshark tarball under Windows, you may find that your
browser has created a file with underscores rather than periods in its file name.
2. Change directory to the Wireshark source directory.
3. Configure your source so it will build correctly for your version of UNIX. You can do this with the
following command:
./configure
If this step fails, you will have to rectify the problems and rerun configure. Troubleshooting hints are
provided in Section 2.6, “Troubleshooting during the install on Unix”.
4. Build the sources into a binary, with the make command. For example:
make
5. Install the software in its final destination, using the command:
make install
Once you have installed Wireshark with make install above, you should be able to run it by entering
wireshark.
13
Building and Installing Wireshark
2.5. Installing the binaries under UNIX
In general, installing the binary under your version of UNIX will be specific to the installation methods
used with your version of UNIX. For example, under AIX, you would use smit to install the Wireshark
binary package, while under Tru64 UNIX (formerly Digital UNIX) you would use setld.
2.5.1. Installing from rpm's under Red Hat and alike
Use the following command to install the Wireshark RPM that you have downloaded from the Wireshark
web site:
rpm -ivh wireshark-1.9.i386.rpm
If the above step fails because of missing dependencies, install the dependencies first, and then retry the
step above. See Example 2.3, “ Installing required RPMs under Red Hat Linux 6.2 and beyond ” for
information on what RPMs you will need to have installed.
2.5.2. Installing from deb's under Debian, Ubuntu and
other Debian derivatives
If you can just install from the repository then use:
aptitude install wireshark
aptitude should take care of all of the dependency issues for you.
Use the following command to install downloaded Wireshark deb's under Debian:
dpkg doesn't take care of all dependencies, but reports what's missing.
Note!
By installing Wireshark packages non-root users won't gain rights automatically to capture
packets. To allow non-root users to capture packets follow the procedure described in /usr/
share/doc/wireshark-common/README.Debian
2.5.3. Installing from portage under Gentoo Linux
Use the following command to install Wireshark under Gentoo Linux with all of the extra features:
Use the following command to install Wireshark under FreeBSD:
14
Building and Installing Wireshark
pkg_add -r wireshark
pkg_add should take care of all of the dependency issues for you.
2.6. Troubleshooting during the install on Unix
A number of errors can occur during the installation process. Some hints on solving these are provided here.
If the configure stage fails, you will need to find out why. You can check the file config.log in the
source directory to find out what failed. The last few lines of this file should help in determining the
problem.
The standard problems are that you do not have GTK+ on your system, or you do not have a recent enough
version of GTK+. The configure will also fail if you do not have libpcap (at least the required include
files) on your system.
Another common problem is for the final compile and link stage to terminate with a complaint of: Output
too long. This is likely to be caused by an antiquated sed (such as the one shipped with Solaris). Since sed
is used by the libtool script to construct the final link command, this leads to mysterious problems. This
can be resolved by downloading a recent version of sed from http://directory.fsf.org/project/sed/.
If you cannot determine what the problems are, send an email to the wireshark-dev mailing list explaining
your problem, and including the output from config.log and anything else you think is relevant, like
a trace of the make stage.
2.7. Building from source under Windows
It is recommended to use the binary installer for Windows, until you want to start developing Wireshark
on the Windows platform.
For further information how to build Wireshark for Windows from the sources, have a look at the
Developer's Guide on the Documentation Page.
You may also want to have a look at the Development Wiki: http://wiki.wireshark.org/Development for
the latest available development documentation.
2.8. Installing Wireshark under Windows
In this section we explore installing Wireshark under Windows from the binary packages.
2.8.1. Install Wireshark
You may acquire a binary installer of Wireshark named something like: wiresharkwinxx-1.9.x.exe. The Wireshark installer includes WinPcap, so you don't need to download and
install two separate packages.
Simply download the Wireshark installer from: http://www.wireshark.org/download.html and execute it.
Beside the usual installer options like where to install the program, there are several optional components.
Tip: Just keep the defaults!
If you are unsure which settings to select, just keep the defaults.
15
Building and Installing Wireshark
2.8.1.1. "Choose Components" page
Wireshark
• Wireshark GTK - Wireshark is a GUI network protocol analyzer.
TShark - TShark is a command-line based network protocol analyzer.
Plugins / Extensions (for the Wireshark and TShark dissection engines):
• Dissector Plugins - Plugins with some extended dissections.
• Tree Statistics Plugins - Plugins with some extended statistics.
• Mate - Meta Analysis and Tracing Engine (experimental) - user configurable extension(s) of the
display filter engine, see http://wiki.wireshark.org/Mate for details.
• SNMP MIBs - SNMP MIBs for a more detailed SNMP dissection.
Tools (additional command line tools to work with capture files):
• Editcap - Editcap is a program that reads a capture file and writes some or all of the packets into another
capture file.
• Text2Pcap - Text2pcap is a program that reads in an ASCII hex dump and writes the data into a libpcapstyle capture file.
• Mergecap - Mergecap is a program that combines multiple saved capture files into a single output file.
• Capinfos - Capinfos is a program that provides information on capture files.
• Rawshark - Rawshark is a raw packet filter.
User's Guide - Local installation of the User's Guide. The Help buttons on most dialogs will require an
internet connection to show help pages if the User's Guide is not installed locally.
2.8.1.2. "Additional Tasks" page
• Start Menu Shortcuts - add some start menu shortcuts.
• Desktop Icon - add a Wireshark icon to the desktop.
• Quick Launch Icon - add a Wireshark icon to the Explorer quick launch toolbar.
• Associate file extensions to Wireshark - Associate standard network trace files to Wireshark.
2.8.1.3. "Install WinPcap?" page
The Wireshark installer contains the latest released WinPcap installer.
If you don't have WinPcap installed, you won't be able to capture live network traffic, but you will still
be able to open saved capture files.
• Currently installed WinPcap version - the Wireshark installer detects the currently installed WinPcap
version.
• Install WinPcap x.x - if the currently installed version is older than the one which comes with the
Wireshark installer (or WinPcap is not installed at all), this will be selected by default.
16
Building and Installing Wireshark
• Start WinPcap service "NPF" at startup - so users without administrative privileges can capture.
You can simply start the Wireshark installer without any command line parameters, it will show you the
usual interactive installer.
For special cases, there are some command line parameters available:
• /NCRC disables the CRC check
• /S runs the installer or uninstaller silently with default values. Please note: The silent installer won't
install WinPCap!
• /desktopicon installation of the desktop icon, =yes - force installation, =no - don't install, otherwise use
defaults / user settings. This option can be useful for a silent installer.
• /quicklaunchicon installation of the quick launch icon, =yes - force installation, =no - don't install,
otherwise use defaults / user settings.
• /D sets the default installation directory ($INSTDIR), overriding InstallDir and InstallDirRegKey. It
must be the last parameter used in the command line and must not contain any quotes, even if the path
contains spaces.
As mentioned above, the Wireshark installer takes care of the installation of WinPcap,
so usually you don't have to worry about WinPcap at all!
The following is only necessary if you want to try a different version than the one included in the Wireshark
installer, e.g. because a new WinPcap (beta) version was released.
Additional WinPcap versions (including newer alpha or beta releases) can be downloaded from the
following locations:
• The main WinPcap site: http://www.winpcap.org
• The Wiretapped.net mirror: http://www.mirrors.wiretapped.net/security/packet-capture/winpcap
At the download page you will find a single installer exe called something like "auto-installer", which can
be installed under various Windows systems, including NT4.0/2000/XP/2003/Vista/7/2008.
17
Building and Installing Wireshark
2.8.3. Update Wireshark
From time to time you may want to update your installed Wireshark to a more recent version. If you join
Wireshark's announce mailing list, you will be informed about new Wireshark versions, see Section 1.6.5,
“Mailing Lists” for details how to subscribe to this list.
New versions of Wireshark usually become available every 4 to 8 months. Updating Wireshark is done the
same way as installing it, you simply download and start the installer exe. A reboot is usually not required
and all your personal settings remain unchanged.
2.8.4. Update WinPcap
New versions of WinPcap are less frequently available, maybe only once in a year. You will find WinPcap
update instructions where you can download new WinPcap versions. Usually you have to reboot the
machine after installing a new WinPcap version.
Warning!
If you have an older version of WinPcap installed, you must uninstall it before installing the
current version. Recent versions of the WinPcap installer will take care of this.
2.8.5. Uninstall Wireshark
You can uninstall Wireshark the usual way, using the "Add or Remove Programs" option inside the Control
Panel. Select the "Wireshark" entry to start the uninstallation procedure.
The Wireshark uninstaller will provide several options as to which things are to be uninstalled; the default
is to remove the core components but keep the personal settings, WinPcap and alike.
WinPcap won't be uninstalled by default, as other programs than Wireshark may use it as well.
2.8.6. Uninstall WinPcap
You can uninstall WinPcap independently of Wireshark, using the "WinPcap" entry in the "Add or Remove
Programs" of the Control Panel.
Note!
After uninstallation of WinPcap you can't capture anything with Wireshark.
It might be a good idea to reboot Windows afterwards.
18
Chapter 3. User Interface
3.1. Introduction
By now you have installed Wireshark and are most likely keen to get started capturing your first packets.
In the next chapters we will explore:
• How the Wireshark user interface works
• How to capture packets in Wireshark
• How to view packets in Wireshark
• How to filter packets in Wireshark
• ... and many other things!
3.2. Start Wireshark
You can start Wireshark from your shell or window manager.
Tip!
When starting Wireshark it's possible to specify optional settings using the command line.
See Section 10.2, “Start Wireshark from the command line” for details.
Note!
In the following chapters, a lot of screenshots from Wireshark will be shown. As Wireshark
runs on many different platforms with many different window managers, different styles
applied and there are different versions of the underlying GUI toolkit used, your screen
might look different from the provided screenshots. But as there are no real differences in
functionality, these screenshots should still be well understandable.
3.3. The Main window
Let's look at Wireshark's user interface. Figure 3.1, “The Main window” shows Wireshark as you would
usually see it after some packets are captured or loaded (how to do this will be described later).
19
Figure 3.1. The Main window
User Interface
Wireshark's main window consists of parts that are commonly known from many other GUI programs.
1. The menu (see Section 3.4, “The Menu”) is used to start actions.
2. The main toolbar (see Section 3.16, “The "Main" toolbar”) provides quick access to frequently used
items from the menu.
3. The filter toolbar (see Section 3.17, “The "Filter" toolbar”) provides a way to directly manipulate the
currently used display filter (see Section 6.3, “Filtering packets while viewing”).
4. The packet list pane (see Section 3.18, “The "Packet List" pane”) displays a summary of each packet
captured. By clicking on packets in this pane you control what is displayed in the other two panes.
5. The packet details pane (see Section 3.19, “The "Packet Details" pane”) displays the packet selected
in the packet list pane in more detail.
6. The packet bytes pane (see Section 3.20, “The "Packet Bytes" pane”) displays the data from the packet
selected in the packet list pane, and highlights the field selected in the packet details pane.
7. The statusbar (see Section 3.21, “The Statusbar”) shows some detailed information about the current
program state and the captured data.
Tip!
The layout of the main window can be customized by changing preference settings. See
Section 10.5, “Preferences” for details!
20
Loading...
+ 225 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.