From e718ffabcf8152fbe30e3374b05897bfcb2f26c1 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Mon, 27 Feb 2006 15:54:05 +0000
Subject: [PATCH] Add IN-BANDWIDTH setting advice to Traffic Shaping Doc

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3598 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 Shorewall/releasenotes.txt |  4 +++-
 docs/traffic_shaping.xml   | 10 +++++++++-
 2 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/Shorewall/releasenotes.txt b/Shorewall/releasenotes.txt
index 84f6b2853..7633e1665 100755
--- a/Shorewall/releasenotes.txt
+++ b/Shorewall/releasenotes.txt
@@ -42,7 +42,9 @@ None.
 Migration Considerations:
 
 1)  A number of macros have been split into two.  The macros affected are:
+
 	IMAP LDAP NNTP POP3 SMTP
+
     Each of these macros now handles only traffic on the native (plaintext)
     port.  There is a corresponding macro with S added to the end of the
     name for the SSL version of the same protocol.  Thus each macro results
@@ -64,7 +66,7 @@ Migration Considerations:
 
 	DNAT     Z1!Z2        loc:192.168.1.4        ...
 
-    That syntax has never worked correctly when Z2 is a dynamic zone.
+    That feature has never worked correctly when Z2 is a dynamic zone.
     Furthermore, now that Shorewall supports exclusion lists, the capability
     is redundant since the above rule can now be written in the form:
 
diff --git a/docs/traffic_shaping.xml b/docs/traffic_shaping.xml
index 3f63bf0dc..8164511c1 100644
--- a/docs/traffic_shaping.xml
+++ b/docs/traffic_shaping.xml
@@ -21,7 +21,7 @@
       </author>
     </authorgroup>
 
-    <pubdate>2006-01-04</pubdate>
+    <pubdate>2006-02-27</pubdate>
 
     <copyright>
       <year>2001-2006</year>
@@ -266,6 +266,14 @@
           to avoid queuing at your providers side. If you don't want any
           traffic to be dropped set this to a value faster than your interface
           maximum rate.</para>
+
+          <para>To determine the optimum value for this setting, we recommend
+          that you start by setting it significantly below your measured
+          download bandwidth (20% or so). While downloading, measure the
+          <emphasis>ping</emphasis> response time from the firewall to the
+          upstream router as you gradually increase the setting.The optimal
+          setting is at the point beyond which the <emphasis>ping</emphasis>
+          time increases sharply as you increase the setting.</para>
         </listitem>
 
         <listitem>