extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-06-19 17:28:35 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add CLASSIFY change to upgrade issues

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4366 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-08-16 16:51:32 +00:00
parent 27cec53079
commit b2af6c9a6e
1 changed files with 34 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
docs/upgrade_issues.xml
View File

@ -240,6 +240,40 @@
<para><command>cp -f /usr/share/shorewall/xmodules <para><command>cp -f /usr/share/shorewall/xmodules
/etc/shorewall/modules</command></para> /etc/shorewall/modules</command></para>
</listitem> </listitem>
<listitem>
<para>(<emphasis role="bold">Versions &gt;= 3.2.3</emphasis>)
Previously, CLASSIFY tcrules were always processed out of the
POSTROUTING chain. Beginning with this release, they are processed out
of the POSTROUTING chain *except* when the SOURCE is
$FW[:&lt;address&gt;] in which case the rule is processed out of the
OUTPUT chain.</para>
<para>With correctly-coded rulesets, this change should have no
effect. Users having incorrectly-coded tcrules may need to change
them.</para>
<para>Example:</para>
<blockquote>
<programlisting>#MARK/ SOURCE DEST PROTO DEST SOURCE
#CLASSIFY PORTS(S) PORT(S)
1:110 $FW eth3 tcp - 22</programlisting>
</blockquote>
<para>While the user may have expected this rule to only affect
traffic from the firewall itself, the rule was really equivalent to
this one:</para>
<blockquote>
<programlisting>#MARK/ SOURCE DEST PROTO DEST SOURCE
#CLASSIFY PORTS(S) PORT(S)
1:110 0.0.0.0/0 eth3 tcp - 22</programlisting>
</blockquote>
<para>So after this change, the second rule will be required rather
than the first if that is what was really wanted.</para>
</listitem>
</orderedlist> </orderedlist>
</section> </section>