</tip>
<para>
The content format of the configuration files is the same on all platforms.
- However, to match the different policies for unix and windows platforms,
+ However, to match the different policies for Unix and windows platforms,
different folders for these files are used.
</para>
<table id="AppFilesTabFolders" frame="none">
to translate IPv4 and IPv6 addresses into names.
</para>
<para>
- This file has the same format as the usual /etc/hosts file in unix systems.
+ This file has the same format as the usual /etc/hosts file in Unix systems.
</para>
<para>
An example is:
<!-- WSUG Appendix Tools -->
-
<!-- $Id$ -->
<appendix id="AppTools">
<para><command>Ethernet manufacturer codes (manuf file)</command>
If both ARP and ethers didn't returned a result, Wireshark tries to convert
the first 3 bytes of an ethernet address to an abbreviated manufacturer name,
- which has been assigned by the IEC
+ which has been assigned by the IEEE
(e.g. 00:09:5b:01:02:03 -> Netgear_01:02:03).
</para>
</section>
The receiver will calculate the checksum of the received data with the same
algorithm as the transmitter.
If the received and calculated checksums don't match a transmission error
- has occured.
+ has occurred.
</para>
<para>
Some checksum algorithms are able to recover (simple) errors by
way to success.
</para>
<para>
- Not long after that Gilbert Ramirez saw its potential and contributed
+ Not long after that, Gilbert Ramirez saw its potential and contributed
a low-level dissector to it.
</para>
<para>
<listitem>
<para>
The developers of Wireshark might improve your changes even more,
- as there's always room for improvements. Or they may implement some
+ 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.
</para>
<title>Reporting problems and getting help</title>
<para>
If you have problems, or need help with Wireshark, there are several
- places that may be of interest to you (well, beside this guide of
+ places that may be of interest to you (well, besides this guide of
course).
</para>
and in the file formats of some other protocol analyzers, so other tools
can read the capture data.
</para>
- <warning><title>File formats have different time stamp accuracys!</title>
+ <warning><title>File formats have different time stamp accuracies!</title>
<para>
Saving from the currently used to a different file format may reduce the
time stamp accuracy, see the <xref linkend="ChAdvTimestamps"/> for details.
<para>
Wireshark is a very useful tool for network troubleshooting, since it
contains a number of features that allow you to quickly focus on
- problems in your networkfor several reasons:
+ problems in your network for several reasons:
<itemizedlist>
<listitem>
<para>
</para>
<para>
Because Wireshark can read many capture file formats, you can
- capture using any conventient tool. One useful approach is
+ capture using any convenient tool. One useful approach is
to use <command>tcpdump</command> to capture on remote
systems and then copy the capture file to your system for
later analysis. For more details on capturing with
<section id="Ch04ROUSWI">
<title>Capturing in the presence of switches and routers</title>
<para>
- In the old days of Ethernet, all network traffic was spreaded over one
+ In the old days of Ethernet, all network traffic was spread over one
"yellow" cable through the whole network. Capturing data was easy,
as all packets from the network could be captured using the
"promiscuous mode" at any place in the network. The only devices blocking
</para>
<para>
Then Ethernet wiring using hubs become the state of the art. As the hubs
- still spreaded the packets all over the network, things regarding
+ still spaded the packets all over the network, things regarding
capturing didn't changed.
</para>
<para>
At the next stage, Ethernet switches became widely available. This
complicated things a lot. When capturing traffic on a computer connected
to a switch, usually the switch will only forward packets to the computer,
- which are directed to it, or to all computers (broadcast's). It's much the
+ which are directed to it, or to all computers (broadcasts). It's much the
same like deactivating the promiscuous mode of the capturing network card.
</para>
<para>
<entry>Ethernet address (6 bytes)</entry>
<entry><para>Separators can be a colon
(:), dot (.) or dash (-) and can have one or
- two bytes between sep
erators:<programlisting>
+ two bytes between sep
arators:<programlisting>
eth.addr == ff:ff:ff:ff:ff:ff
eth.addr == ff-ff-ff-ff-ff-ff
eth.addr == ffff.ffff.ffff</programlisting></para></entry>
</row>
<row>
<entry>IPv6 address</entry>
- <entry> </entry>
+ <entry>ipv6.addr == ::1</entry>
</row>
<row>
- <entry>IPX network number</entry>
- <entry> </entry>
+ <entry>IPX address</entry>
+ <entry>ipx.addr == 00000000.ffffffffffff</entry>
</row>
<row>
<entry>String (text)</entry>
- <entry> </entry>
- </row>
- <row>
- <entry>
- Double-precision floating point number
- </entry>
- <entry> </entry>
+ <entry>http.request.uri == "http://www.wireshark.org/"</entry>
</row>
</tbody>
</tgroup>
<para>
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 might be explained in this
+ the early days, not every feature of Wireshark may be explained in this
book.
</para>
<para>
</para>
<para>
By reading this book, you will learn how to install Wireshark, how to use the
- basic elements of the graphical user interface (like the menu) and what's
- behind some of the advanced features that are maybe not that obvious at first
- sight. It will
- hopefully guide you around some common problems that frequently appears for
- new (and sometimes even advanced) users of Wireshark.
+ 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.
</para>
</section>
git.samba.org / obnox / wireshark / wip.git / commitdiff