From 20ff95f1234b14a5b693ff096a2aeb9e156f4ec7 Mon Sep 17 00:00:00 2001 From: Ulf Lamping Date: Thu, 16 Jun 2005 21:51:17 +0000 Subject: [PATCH] updated to latest Ethereal GUI svn path=/trunk/; revision=14671 --- docbook/eug_src/EUG_chapter_advanced.xml | 44 ++++++++++++++++-------- 1 file changed, 30 insertions(+), 14 deletions(-) diff --git a/docbook/eug_src/EUG_chapter_advanced.xml b/docbook/eug_src/EUG_chapter_advanced.xml index af7a935171..291597e7a0 100644 --- a/docbook/eug_src/EUG_chapter_advanced.xml +++ b/docbook/eug_src/EUG_chapter_advanced.xml @@ -67,7 +67,7 @@ - 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: @@ -94,6 +94,12 @@ into your own C program. + + + Raw. This allows you to load the unaltered stream + data into a different program for further examination. + + @@ -154,7 +160,7 @@ -
Reassembling is disabled! +
Reassembling is disabled by default! Reassembling is usually disabled in the preferences by default, as it slows down packet processing a bit. @@ -187,23 +193,24 @@
Name Resolution - 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 . + 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 . 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. Note! - 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). @@ -211,9 +218,18 @@ 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. + Tip! + + 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. + + The name resolution feature can be en-/disabled separately for the following protocol layers (in brackets):