From a348da66362d69f7aef1ba6706d5bd62bede60d8 Mon Sep 17 00:00:00 2001
From: teastep <teastep@fbd18981-670d-0410-9b5c-8dc0c1a9a2bb>
Date: Sun, 10 Feb 2008 06:00:33 +0000
Subject: [PATCH] Update man pages for .1

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8175 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
---
 manpages/shorewall-tcclasses.xml | 4 ++--
 manpages/shorewall-tcrules.xml   | 9 ++++++++-
 manpages/shorewall.xml           | 8 ++++++++
 3 files changed, 18 insertions(+), 3 deletions(-)

diff --git a/manpages/shorewall-tcclasses.xml b/manpages/shorewall-tcclasses.xml
index b43e47deb..75961d01e 100644
--- a/manpages/shorewall-tcclasses.xml
+++ b/manpages/shorewall-tcclasses.xml
@@ -196,8 +196,8 @@
         role="bold">,</emphasis><emphasis>option</emphasis>]...]</term>
 
         <listitem>
-          <para>A comma-separated list of options including the
-          following:</para>
+          <para>Added in Shorewall-perl 4.1. A comma-separated list of options
+          including the following:</para>
 
           <variablelist>
             <varlistentry>
diff --git a/manpages/shorewall-tcrules.xml b/manpages/shorewall-tcrules.xml
index 01a2414cb..649058014 100644
--- a/manpages/shorewall-tcrules.xml
+++ b/manpages/shorewall-tcrules.xml
@@ -87,7 +87,14 @@
               <para>- If the SOURCE is <emphasis
               role="bold">$FW</emphasis>[<emphasis
               role="bold">:</emphasis><emphasis>address-or-range</emphasis>[,<emphasis>address-or-range</emphasis>]...],
-              then the rule is inserted into the OUTPUT chain.</para>
+              then the rule is inserted into the OUTPUT chain. The behavior
+              changed in Shorewall-perl 4.1. Previously, when
+              HIGH_ROUTE_MARKS=Yes, Shorewall allowed non-zero mark values
+              &lt; 256 to be assigned in the OUTPUT chain. This has been
+              changed so that only high mark values may be assigned there.
+              Packet marking rules for traffic shaping of packets originating
+              on the firewall must be coded in the POSTROUTING chain (see
+              below).</para>
 
               <para>- Otherwise, the chain is determined by the setting of
               MARK_IN_FORWARD_CHAIN in <ulink
diff --git a/manpages/shorewall.xml b/manpages/shorewall.xml
index a3d92539d..936a08873 100644
--- a/manpages/shorewall.xml
+++ b/manpages/shorewall.xml
@@ -944,6 +944,14 @@
           chains such as FORWARD may not be refreshed.</para>
 
           <para>Example:<programlisting><command>shorewall refresh net2fw nat:net_dnat</command> #Refresh the 'net2loc' chain in the filter table and the 'net_dnat' chain in the nat table</programlisting></para>
+
+          <para>Beginning with Shorewall 4.1, the <emphasis
+          role="bold">refresh</emphasis> command has slightly different
+          behavior. When no chain name is given to the <emphasis
+          role="bold">refresh</emphasis> command, the mangle table is
+          refreshed along with the blacklist chain (if any). This allows you
+          to modify <filename>/etc/shorewall/tcrules </filename>and install
+          the changes using <emphasis role="bold">refresh</emphasis>. </para>
         </listitem>
       </varlistentry>