extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-08 08:44:05 +01:00
Code Issues Packages Projects Releases Wiki Activity

Purge more manpages of outdated references

Browse Source
This commit is contained in:
Tom Eastep 2009-07-15 19:15:52 -07:00
parent f16b2300b6
commit 58f0110ad3
4 changed files with 8 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
manpages/shorewall-hosts.xml
View File

@ -241,15 +241,6 @@
for each remote client. The clients are assigned IP addresses in the
network 192.168.3.0/24 and in a zone named 'vpn'.<programlisting>#ZONE HOST(S) OPTIONS
vpn ppp+:192.168.3.0/24</programlisting></para>
<para>If you are running a Shorewall version prior to 4.1.4, it is
especially recommended to define such a zone using this file rather
than <ulink
url="shorewall-interfaces.html">shorewall-interfaces</ulink>(8) if
there is another zone that uses a fixed PPP interface (for example,
if the 'net' zone always interfaces through ppp0). See <ulink
url="shorewall-nesting.html">shorewall-nesting</ulink>(8) for
additional information.</para>
</listitem>
</varlistentry>
</variablelist>

3
manpages6/shorewall6-notrack.xml
View File

@ -27,9 +27,6 @@
connection tracking. Traffic matching entries in this fill will not be
tracked.</para>
<para>The file was added in shorewall6-perl 4.2.7 and is not supported by
shorewall6-shell or by earlier versions of shorewall6-perl.</para>
<para>The columns in the file are as follows.</para>
<variablelist>

12
manpages6/shorewall6-tcrules.xml
View File

@ -155,12 +155,12 @@
not followed the value with <option>:F</option>) or the OUTPUT
chain (SOURCE is <emphasis role="bold">$FW</emphasis>). With
HIGH_ROUTE_MARKS=Yes, non-zero mark values less that 256 are not
permitted. Shorewall6 4.1 and later versions prohibit non-zero
mark values less that 256 in the OUTPUT chain when
HIGH_ROUTE_MARKS=Yes. While earlier versions allow such values
in the OUTPUT chain, it is strongly recommended that with
HIGH_ROUTE_MARKS=Yes, you use the POSTROUTING chain to apply
traffic shaping marks/classification.</para>
permitted. Shorewall6 prohibits non-zero mark values less that
256 in the OUTPUT chain when HIGH_ROUTE_MARKS=Yes. While earlier
versions allow such values in the OUTPUT chain, it is strongly
recommended that with HIGH_ROUTE_MARKS=Yes, you use the
POSTROUTING chain to apply traffic shaping
marks/classification.</para>
</listitem>
<listitem>

10
manpages6/shorewall6.conf.xml
View File

@ -119,10 +119,6 @@
role="bold">none</emphasis>}</term>
<listitem>
<para>In earlier Shorewall6 versions, a "default action" for DROP
and REJECT policies was specified in the file
/usr/share/shorewall6/actions.std.</para>
<para>To allow for default rules to be applied when USE_ACTIONS=No,
the DROP_DEFAULT, REJECT_DEFAULT, ACCEPT_DEFAULT, QUEUE_DEFAULT and
NFQUEUE_DEFAULT options have been added.</para>
@ -891,11 +887,9 @@ net all DROP info</programlisting>then the chain name is 'net2all'
<listitem>
<para>This parameter specifies the directory/directories where your
kernel netfilter modules may be found. If you leave the variable
empty, Shorewall6 will supply the value "/lib/modules/`uname
-r`/kernel/net/ipv4/netfilter" in versions of Shorewall6 prior to
3.2.4 and "/lib/modules/`uname
empty, Shorewall6 will supply "/lib/modules/`uname
-r`/kernel/net/ipv4/netfilter:/lib/modules/`uname
-r`/kernel/net/ipv4/netfilter" in later versions.</para>
-r`/kernel/net/ipv4/netfilter".</para>
</listitem>
</varlistentry>