aboutsummaryrefslogtreecommitdiffstats
path: root/docbook/eug_src
diff options
context:
space:
mode:
authorUlf Lamping <ulf.lamping@web.de>2005-12-18 03:42:01 +0000
committerUlf Lamping <ulf.lamping@web.de>2005-12-18 03:42:01 +0000
commit0f388d682ff115e52deff69f72abe117d435b80d (patch)
tree067c60167ae46476dae19f6631248649265a58e5 /docbook/eug_src
parent0f4cc578a17ffece635fc87e6b8425ab287de9b4 (diff)
reassembling as enabled by default (the default was changed from disabled to enabled some time ago)
svn path=/trunk/; revision=16836
Diffstat (limited to 'docbook/eug_src')
-rw-r--r--docbook/eug_src/EUG_chapter_advanced.xml17
1 files changed, 9 insertions, 8 deletions
diff --git a/docbook/eug_src/EUG_chapter_advanced.xml b/docbook/eug_src/EUG_chapter_advanced.xml
index 291597e7a0..6966390c8b 100644
--- a/docbook/eug_src/EUG_chapter_advanced.xml
+++ b/docbook/eug_src/EUG_chapter_advanced.xml
@@ -136,14 +136,14 @@
<section><title>How Ethereal handles it</title>
<para>
For some of the network protocols Ethereal knows of, a mechanism is
- implemented to find, decode and display this chunks of data.
+ implemented to find, decode and display these chunks of data.
Ethereal will try to find the corresponding packets of this chunk,
and will show the combined data as additional pages in the
"Packet Bytes" pane, see <xref linkend="ChUsePacketBytesPaneSection"/>.
</para>
<note><title>Note!</title>
<para>
- Reassembling might take place in several protocol layers, so it's possible
+ Reassembling might take place at several protocol layers, so it's possible
that multiple tabs in the "Packet Bytes" pane appear.
</para>
</note>
@@ -158,15 +158,16 @@
HTML page) is returned. Ethereal will show the hex dump of the data in
a new tab "Uncompressed entity body" in the "Packet Bytes" pane.
</para>
- </section>
-
- <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.
+ Reassembling is enabled in the preferences by default. The defaults
+ were changed from disabled to enabled in September 2005. If you created
+ your preference settings before this date, you might look if reassembling
+ is actually enabled, as it can be extremely helpful while analyzing
+ network packets.
</para>
<para>
- Enabling reassembling of a protocol typically requires two things:
+ The enabling or disabling of the reassemble settings of a protocol typically
+ requires two things:
<orderedlist>
<listitem>
<para>