Fix man page typo (CLEAR_FORWARD_MARK -> FORWARD_CLEAR_MARK)

This commit is contained in:
Tom Eastep 2011-04-06 10:46:47 -07:00
parent 6626ef06fb
commit e653a34865
4 changed files with 9 additions and 3 deletions

View File

@ -6,6 +6,8 @@ Changes in Shorewall 4.4.19 RC 1
3) Allow simple TC to work on both IPv4 and IPv6
4) Fix an optimizer bug in Shorewall::Chains::replace_references().
Changes in Shorewall 4.4.19 Beta 5
1) Fix logical naming and bridge.

View File

@ -16,7 +16,11 @@ VI. PROBLEMS CORRECTED AND NEW FEATURES IN PRIOR RELEASES
RC 1
None.
1) Corrected a problem in optimize level 4 that resulted in the
following compile-time failure.
Can't use an undefined value as an ARRAY reference at
/usr/share/shorewall/Shorewall/Chains.pm line 862.
Beta 5

View File

@ -625,7 +625,7 @@ net all DROP info</programlisting>then the chain name is 'net2all'
<para>Added in Shorewall 4.4.11 Beta 3. Traditionally, Shorewall has
cleared the packet mark in the first rule in the mangle FORWARD
chain. This behavior is maintained with the default setting of this
option (CLEAR_FORWARD_MARK=Yes). If FORWARD_CLEAR_MARK is set to
option (FORWARD_CLEAR_MARK=Yes). If FORWARD_CLEAR_MARK is set to
'No', packet marks set in the mangle PREROUTING chain are retained
in the FORWARD chains.</para>
</listitem>

View File

@ -522,7 +522,7 @@
<para>Added in Shorewall 4.4.11 Beta 3. Traditionally, Shorewall has
cleared the packet mark in the first rule in the mangle FORWARD
chain. This behavior is maintained with the default setting of this
option (CLEAR_FORWARD_MARK=Yes). If FORWARD_CLEAR_MARK is set to
option (FORWARD_CLEAR_MARK=Yes). If FORWARD_CLEAR_MARK is set to
'No', packet marks set in the mangle PREROUTING chain are retained
in the FORWARD chains.</para>
</listitem>