forked from osmocom/wireshark
fix various minor things noted by Brian Drab
svn path=/trunk/; revision=19230
This commit is contained in:
parent
1d5165c8e0
commit
93bf2c9841
Binary file not shown.
Before Width: | Height: | Size: 51 KiB After Width: | Height: | Size: 49 KiB |
|
@ -573,7 +573,7 @@
|
||||||
</orderedlist>
|
</orderedlist>
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
The tooltip of the higher level protocol setting will note you if and
|
The tooltip of the higher level protocol setting will notify you if and
|
||||||
which lower level protocol setting has to be considered too.
|
which lower level protocol setting has to be considered too.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
@ -582,7 +582,7 @@
|
||||||
<section id="ChAdvNameResolutionSection"><title>Name Resolution</title>
|
<section id="ChAdvNameResolutionSection"><title>Name Resolution</title>
|
||||||
<para>
|
<para>
|
||||||
Name resolution tries to resolve some of the numerical address values into
|
Name resolution tries to resolve some of the numerical address values into
|
||||||
a human readable format. There are two possible ways to do this
|
a human readable format. There are two possible ways to do these
|
||||||
conversations, depending on the resolution to be done: calling
|
conversations, depending on the resolution to be done: calling
|
||||||
system/network services (like the gethostname function) and/or evaluate
|
system/network services (like the gethostname function) and/or evaluate
|
||||||
from Wireshark specific configuration files.
|
from Wireshark specific configuration files.
|
||||||
|
@ -597,7 +597,7 @@
|
||||||
<section><title>Name Resolution drawbacks</title>
|
<section><title>Name Resolution drawbacks</title>
|
||||||
<para>
|
<para>
|
||||||
Name resolution can be invaluable while working with Wireshark and may
|
Name resolution can be invaluable while working with Wireshark and may
|
||||||
save you even hours of work. Unfortunately, it also has it's drawbacks.
|
even save you hours of work. Unfortunately, it also has it's drawbacks.
|
||||||
</para>
|
</para>
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
|
@ -615,7 +615,7 @@
|
||||||
So the resolved names might not be available if you open the capture file
|
So the resolved names might not be available if you open the capture file
|
||||||
later or on a different machine.
|
later or on a different machine.
|
||||||
Each time you open a capture file it may look "slightly different",
|
Each time you open a capture file it may look "slightly different",
|
||||||
maybe simply because you can't connect a name server (which you could
|
maybe simply because you can't connect to a name server (which you could
|
||||||
connect before).
|
connect before).
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
|
|
|
@ -726,7 +726,7 @@ wireshark -i eth0 -k
|
||||||
<para>
|
<para>
|
||||||
In the usual case, you won't have to choose this link-layer header type.
|
In the usual case, you won't have to choose this link-layer header type.
|
||||||
The following paragraphs describe the exceptional cases, where
|
The following paragraphs describe the exceptional cases, where
|
||||||
selecting this type is possible, so you will have a guide what to do:
|
selecting this type is possible, so you will have a guide of what to do:
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
If you are capturing on an 802.11 device on some versions of BSD, this
|
If you are capturing on an 802.11 device on some versions of BSD, this
|
||||||
|
@ -1017,7 +1017,7 @@ tcp port 23 and not host 10.0.0.5
|
||||||
<graphic entityref="WiresharkCaptureInfoDialog" format="JPG"/>
|
<graphic entityref="WiresharkCaptureInfoDialog" format="JPG"/>
|
||||||
</figure>
|
</figure>
|
||||||
This dialog box will inform you about the number of captured packets and
|
This dialog box will inform you about the number of captured packets and
|
||||||
the time since the capture was started. The selection which protocols
|
the time since the capture was started. The selection of which protocols
|
||||||
are counted cannot be changed.
|
are counted cannot be changed.
|
||||||
</para>
|
</para>
|
||||||
<tip><title>Tip!</title>
|
<tip><title>Tip!</title>
|
||||||
|
|
|
@ -114,10 +114,11 @@
|
||||||
<section>
|
<section>
|
||||||
<title>Live capture from many different network media</title>
|
<title>Live capture from many different network media</title>
|
||||||
<para>
|
<para>
|
||||||
Despite its name, Wireshark can capture traffic from
|
Wireshark can capture traffic from many different network media types
|
||||||
network media other than Ethernet. Which media types are
|
- and despite it's name including wireless LAN as well.
|
||||||
supported, depends on many things like the operating system you are
|
Which media types are supported, depends on many things like the
|
||||||
using. An overview of the supported media types can be found at:
|
operating system you are using.
|
||||||
|
An overview of the supported media types can be found at:
|
||||||
<ulink url="&WiresharkMediaPage;"/>.
|
<ulink url="&WiresharkMediaPage;"/>.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
@ -225,7 +226,7 @@
|
||||||
<listitem><para>Red Hat Linux</para></listitem>
|
<listitem><para>Red Hat Linux</para></listitem>
|
||||||
<listitem><para>Rock Linux</para></listitem>
|
<listitem><para>Rock Linux</para></listitem>
|
||||||
<listitem><para>Slackware Linux</para></listitem>
|
<listitem><para>Slackware Linux</para></listitem>
|
||||||
<listitem><para>Suse Linux</para></listitem>
|
<listitem><para>SUSE Linux</para></listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
|
@ -427,7 +427,7 @@
|
||||||
<para>
|
<para>
|
||||||
When using the "Multiple Files" option while doing a capture
|
When using the "Multiple Files" option while doing a capture
|
||||||
(see: <xref linkend="ChCapCaptureFiles"/>),
|
(see: <xref linkend="ChCapCaptureFiles"/>),
|
||||||
the capture data is spreaded over several capture files, called a file
|
the capture data is spread over several capture files, called a file
|
||||||
set.
|
set.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
|
@ -449,7 +449,7 @@
|
||||||
<para>
|
<para>
|
||||||
This simple mechanism usually works well, but has it's drawbacks. If several
|
This simple mechanism usually works well, but has it's drawbacks. If several
|
||||||
file sets were captured with the same prefix and suffix, Wireshark will detect
|
file sets were captured with the same prefix and suffix, Wireshark will detect
|
||||||
them as a single file set. If files were renamed or spreaded over several
|
them as a single file set. If files were renamed or spread over several
|
||||||
directories the mechanism will fail to find all files of a set.
|
directories the mechanism will fail to find all files of a set.
|
||||||
</para>
|
</para>
|
||||||
</sidebar>
|
</sidebar>
|
||||||
|
|
|
@ -60,7 +60,7 @@
|
||||||
</figure>
|
</figure>
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
The following table gives an overview which functions are available
|
The following table gives an overview of which functions are available
|
||||||
in this pane, where to find the corresponding function in the main menu,
|
in this pane, where to find the corresponding function in the main menu,
|
||||||
and a short description of each item.
|
and a short description of each item.
|
||||||
</para>
|
</para>
|
||||||
|
@ -207,7 +207,7 @@
|
||||||
</figure>
|
</figure>
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
The following table gives an overview which functions are available
|
The following table gives an overview of which functions are available
|
||||||
in this pane, where to find the corresponding function in the main menu,
|
in this pane, where to find the corresponding function in the main menu,
|
||||||
and a short description of each item.
|
and a short description of each item.
|
||||||
</para>
|
</para>
|
||||||
|
@ -401,7 +401,7 @@
|
||||||
</figure>
|
</figure>
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
The following table gives an overview which functions are available
|
The following table gives an overview of which functions are available
|
||||||
in this pane, where to find the corresponding function in the main menu,
|
in this pane, where to find the corresponding function in the main menu,
|
||||||
and a short description of each item.
|
and a short description of each item.
|
||||||
</para>
|
</para>
|
||||||
|
@ -510,7 +510,7 @@
|
||||||
You can filter on any protocol that Wireshark understands.
|
You can filter on any protocol that Wireshark understands.
|
||||||
You can also filter on any field that a dissector adds to the tree
|
You can also filter on any field that a dissector adds to the tree
|
||||||
view, but only if the dissector has added an abbreviation for the
|
view, but only if the dissector has added an abbreviation for the
|
||||||
field. A list of such fields is available in the Wireshark in the
|
field. A list of such fields is available in Wireshark in the
|
||||||
<command>Add Expression...</command> dialog box. You can find more
|
<command>Add Expression...</command> dialog box. You can find more
|
||||||
information on the <command>Add Expression...</command> dialog box
|
information on the <command>Add Expression...</command> dialog box
|
||||||
in <xref linkend="ChWorkFilterAddExpressionSection"/>.
|
in <xref linkend="ChWorkFilterAddExpressionSection"/>.
|
||||||
|
@ -953,6 +953,7 @@ eth.src[1-2] == 00:83
|
||||||
<para>
|
<para>
|
||||||
You can leave the <command>Add Expression...</command> dialog
|
You can leave the <command>Add Expression...</command> dialog
|
||||||
box without any effect by clicking the <command>Cancel</command>
|
box without any effect by clicking the <command>Cancel</command>
|
||||||
|
button.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
Loading…
Reference in New Issue