osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

updated to latest Ethereal GUI 

svn path=/trunk/; revision=14671
This commit is contained in:
Ulf Lamping 2005-06-16 21:51:17 +00:00
parent b6d028442c
commit 20ff95f123
1 changed files with 30 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
docbook/eug_src/EUG_chapter_advanced.xml
View File

@ -67,7 +67,7 @@
</orderedlist>
</para>
<para>
You can then choose to view the data in one of four formats:
You can then choose to view the data in one of the following formats:
<orderedlist>
<listitem>
<para>
@ -94,6 +94,12 @@
into your own C program.
</para>
</listitem>
<listitem>
<para>
<command>Raw</command>. This allows you to load the unaltered stream
data into a different program for further examination.
</para>
</listitem>
</orderedlist>
</para>
<note>
@ -154,7 +160,7 @@
</para>
</section>
<section><title>Reassembling is disabled!</title>
<section><title>Reassembling is disabled by default!</title>
<para>
Reassembling is usually disabled in the preferences by default, as it
slows down packet processing a bit.
@ -187,23 +193,24 @@
<section id="ChAdvNameResolutionSection"><title>Name Resolution</title>
<para>
Name resolution tries to resolve some of the numerical address values to human
readable names. There are two possible ways to do this conversations, depending on
the resolution to be done: calling system/network services (like the gethostname
function) and/or evaluate from Ethereal specific configuration files. If there
are both features available, Ethereal will first try the system services
and then fall back to it's own configuration files. XXX - is this really true?
For details about the configuration files Ethereal uses for name
resolution and alike, see <xref linkend="AppFiles"/>.
Name resolution tries to resolve some of the numerical address values to
human readable names. There are two possible ways to do this
conversations, depending on the resolution to be done: calling
system/network services (like the gethostname function) and/or evaluate
from Ethereal specific configuration files. If there are both features
available, Ethereal will first try the system services and then fall back
to it's own configuration files. XXX - is this really true? For details
about the configuration files Ethereal uses for name resolution and alike,
see <xref linkend="AppFiles"/>.
</para>
<para>
However, be prepared that this conversion often will fail, e.g. the name
to be resolved might simply be unknown by the servers asked and the
configuration files.
to be resolved might simply be unknown by the servers asked and not found
in the configuration files.
</para>
<note><title>Note!</title>
<para>
You might see packets to/from your machine in your capture file, which are
You may see packets to/from your machine in your capture file, which are
caused by name resolution network services (e.g. DNS packets).
</para>
</note>
@ -211,9 +218,18 @@
<para>
The resolved names are not stored in the capture file or somewhere else,
so the resolved names might not be available if you open the capture file
later or on another machine.
later or on a different machine.
</para>
</note>
<tip><title>Tip!</title>
<para>
The name resolution in the packet list is done while the list is filled.
If a name could be resolved after a packet was added to the list, that
entry won't be changed. As the name resolution results are cached, you
can use "View/Reload" to rebuild the packet list, this time with the
correctly resolved names.
</para>
</tip>
<para>
The name resolution feature can be en-/disabled separately for the
following protocol layers (in brackets):