forked from extern/shorewall_code
Minor documentation updates
Signed-off-by: Tom Eastep <teastep@shorewall.net> git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@9806 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
4b419186bc
commit
9d03fe20e0
@ -670,9 +670,8 @@ acton:info:test $FW net</programlisting>
|
|||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
||||||
<para>For an example of how to use these variables in both Shorewall-shell
|
<para>For an example of how to use these variablesl, see <ulink
|
||||||
and Shorewall-perl, see <ulink url="PortKnocking.html">this
|
url="PortKnocking.html">this article</ulink>.</para>
|
||||||
article</ulink>.</para>
|
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section id="Extension">
|
<section id="Extension">
|
||||||
|
@ -36,7 +36,11 @@
|
|||||||
|
|
||||||
<note>
|
<note>
|
||||||
<para>This information is provided primarily for Shorewall developers.
|
<para>This information is provided primarily for Shorewall developers.
|
||||||
Users are expected to install from pre-built tarballs or packages. </para>
|
Users are expected to install from pre-built tarballs or packages.</para>
|
||||||
|
|
||||||
|
<para>Beginning with Shorewall 4.4, the Shorewall project will use Git as
|
||||||
|
it's SCM system rather than SVN. This document will be updated prior to
|
||||||
|
the release of 4.4 to refect the move to Git.</para>
|
||||||
</note>
|
</note>
|
||||||
|
|
||||||
<section>
|
<section>
|
||||||
@ -256,7 +260,7 @@
|
|||||||
</variablelist>
|
</variablelist>
|
||||||
|
|
||||||
<para>You should ensure that you have the latest script. The scripts
|
<para>You should ensure that you have the latest script. The scripts
|
||||||
change periodically as we move through the release cycles. </para>
|
change periodically as we move through the release cycles.</para>
|
||||||
|
|
||||||
<para>The scripts may need to be modified to fit your particular
|
<para>The scripts may need to be modified to fit your particular
|
||||||
environment. There are a number of variables that are set near the front
|
environment. There are a number of variables that are set near the front
|
||||||
@ -440,7 +444,7 @@
|
|||||||
<term><emphasis>prior release</emphasis></term>
|
<term><emphasis>prior release</emphasis></term>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>The release to be used to generate patch files. </para>
|
<para>The release to be used to generate patch files.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
</variablelist>
|
</variablelist>
|
||||||
|
@ -348,11 +348,12 @@ insert_rule $filter_table->{OUTPUT}, 1, "-p udp --sport 1701 -j ACCEPT";
|
|||||||
used in a Shorewall configuration file, the name must be preceded by
|
used in a Shorewall configuration file, the name must be preceded by
|
||||||
a plus sign (+) as with the shell-based compiler.</para>
|
a plus sign (+) as with the shell-based compiler.</para>
|
||||||
|
|
||||||
<para>Shorewall is now out of the ipset load/reload business. With
|
<para>Shorewall is now out of the ipset load/reload business with
|
||||||
scripts generated by the Perl-based Compiler, the Netfilter rule set
|
the exception of ipsets used for dynamic zones. With scripts
|
||||||
is never cleared. That means that there is no opportunity for
|
generated by the Perl-based Compiler, the Netfilter rule set is
|
||||||
Shorewall to load/reload your ipsets since that cannot be done while
|
never cleared. That means that there is no opportunity for Shorewall
|
||||||
there are any current rules using ipsets.</para>
|
to load/reload your ipsets since that cannot be done while there are
|
||||||
|
any current rules using ipsets.</para>
|
||||||
|
|
||||||
<para>So:</para>
|
<para>So:</para>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user