forked from extern/shorewall_code
Update man pages based on previous fix
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8049 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
3d84cec3a3
commit
d4db69739c
@ -206,8 +206,9 @@
|
||||
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>It is especially recommended to define such a zone using this
|
||||
file rather than <ulink
|
||||
<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).</para>
|
||||
|
@ -71,8 +71,9 @@ loc eth2 -</programlisting>
|
||||
applies to all PPP interfaces, use 'ppp+'; that would match ppp0,
|
||||
ppp1, ppp2, …</para>
|
||||
|
||||
<para>Care must be exercised when using wildcards where there is
|
||||
another zone that uses a matching specific interface. See <ulink
|
||||
<para>When using Shorewall versions before 4.1.4, care must be
|
||||
exercised when using wildcards where there is another zone that uses
|
||||
a matching specific interface. See <ulink
|
||||
url="shorewall-nesting.html">shorewall-nesting</ulink>(8) for a
|
||||
discussion of this problem.</para>
|
||||
|
||||
|
@ -104,8 +104,9 @@
|
||||
multiple ACCEPT+ rules. This technique also may be used when the ACTION is
|
||||
REDIRECT.</para>
|
||||
|
||||
<para>Care must be taken when nesting occurs as a result of the use of
|
||||
wildcard interfaces (interface names ends in '+').</para>
|
||||
<para>When using Shorewall versions before 4.1.4, care must be taken when
|
||||
nesting occurs as a result of the use of wildcard interfaces (interface
|
||||
names ends in '+').</para>
|
||||
|
||||
<para>Here's an example.
|
||||
<filename>/etc/shorewall/zones</filename>:<programlisting> #ZONE TYPE OPTION
|
||||
|
@ -1158,9 +1158,10 @@
|
||||
<listitem>
|
||||
<para>Shorewall does not impose as much structure on the Netfilter
|
||||
rules in the 'nat' table as it does on those in the filter table. As
|
||||
a consequence, care must be exercised when using DNAT and REDIRECT
|
||||
rules with zones defined with wildcard interfaces (those ending with
|
||||
'+'. Here is an example:</para>
|
||||
a consequence, when using Shorewall versions before 4.1.4, care must
|
||||
be exercised when using DNAT and REDIRECT rules with zones defined
|
||||
with wildcard interfaces (those ending with '+'. Here is an
|
||||
example:</para>
|
||||
|
||||
<para><ulink
|
||||
url="shorewall-zones.html">shorewall-zones</ulink>(8):<programlisting> #ZONE TYPE OPTIONS
|
||||
|
Loading…
Reference in New Issue
Block a user