holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Update man pages based on previous fix

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8049 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2008-01-12 01:47:58 +00:00
parent 3d84cec3a3
commit d4db69739c
4 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
manpages/shorewall-hosts.xml
View File

@ -206,8 +206,9 @@
network 192.168.3.0/24 and in a zone named 'vpn'.<programlisting>#ZONE HOST(S) OPTIONS 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> vpn ppp+:192.168.3.0/24</programlisting></para>
<para>It is especially recommended to define such a zone using this <para>If you are running a Shorewall version prior to 4.1.4, it is
file rather than <ulink especially recommended to define such a zone using this file rather
than <ulink
url="shorewall-interfaces.html">shorewall-interfaces</ulink>(8) if url="shorewall-interfaces.html">shorewall-interfaces</ulink>(8) if
there is another zone that uses a fixed PPP interface (for example, there is another zone that uses a fixed PPP interface (for example,
if the 'net' zone always interfaces through ppp0).</para> if the 'net' zone always interfaces through ppp0).</para>

5
manpages/shorewall-interfaces.xml
View File

@ -71,8 +71,9 @@ loc eth2 -</programlisting>
applies to all PPP interfaces, use 'ppp+'; that would match ppp0, applies to all PPP interfaces, use 'ppp+'; that would match ppp0,
ppp1, ppp2, …</para> ppp1, ppp2, …</para>
<para>Care must be exercised when using wildcards where there is <para>When using Shorewall versions before 4.1.4, care must be
another zone that uses a matching specific interface. See <ulink 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 url="shorewall-nesting.html">shorewall-nesting</ulink>(8) for a
discussion of this problem.</para> discussion of this problem.</para>

5
manpages/shorewall-nesting.xml
View File

@ -104,8 +104,9 @@
multiple ACCEPT+ rules. This technique also may be used when the ACTION is multiple ACCEPT+ rules. This technique also may be used when the ACTION is
REDIRECT.</para> REDIRECT.</para>
<para>Care must be taken when nesting occurs as a result of the use of <para>When using Shorewall versions before 4.1.4, care must be taken when
wildcard interfaces (interface names ends in '+').</para> nesting occurs as a result of the use of wildcard interfaces (interface
names ends in '+').</para>
<para>Here's an example. <para>Here's an example.
<filename>/etc/shorewall/zones</filename>:<programlisting> #ZONE TYPE OPTION <filename>/etc/shorewall/zones</filename>:<programlisting> #ZONE TYPE OPTION

7
manpages/shorewall-rules.xml
View File

@ -1158,9 +1158,10 @@
<listitem> <listitem>
<para>Shorewall does not impose as much structure on the Netfilter <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 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 a consequence, when using Shorewall versions before 4.1.4, care must
rules with zones defined with wildcard interfaces (those ending with be exercised when using DNAT and REDIRECT rules with zones defined
'+'. Here is an example:</para> with wildcard interfaces (those ending with '+'. Here is an
example:</para>
<para><ulink <para><ulink
url="shorewall-zones.html">shorewall-zones</ulink>(8):<programlisting> #ZONE TYPE OPTIONS url="shorewall-zones.html">shorewall-zones</ulink>(8):<programlisting> #ZONE TYPE OPTIONS