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>
|
||||
</itemizedlist>
|
||||
|
||||
<para>For an example of how to use these variables in both Shorewall-shell
|
||||
and Shorewall-perl, see <ulink url="PortKnocking.html">this
|
||||
article</ulink>.</para>
|
||||
<para>For an example of how to use these variablesl, see <ulink
|
||||
url="PortKnocking.html">this article</ulink>.</para>
|
||||
</section>
|
||||
|
||||
<section id="Extension">
|
||||
|
@ -37,6 +37,10 @@
|
||||
<note>
|
||||
<para>This information is provided primarily for Shorewall developers.
|
||||
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>
|
||||
|
||||
<section>
|
||||
|
@ -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
|
||||
a plus sign (+) as with the shell-based compiler.</para>
|
||||
|
||||
<para>Shorewall is now out of the ipset load/reload business. With
|
||||
scripts generated by the Perl-based Compiler, the Netfilter rule set
|
||||
is never cleared. That means that there is no opportunity for
|
||||
Shorewall to load/reload your ipsets since that cannot be done while
|
||||
there are any current rules using ipsets.</para>
|
||||
<para>Shorewall is now out of the ipset load/reload business with
|
||||
the exception of ipsets used for dynamic zones. With scripts
|
||||
generated by the Perl-based Compiler, the Netfilter rule set is
|
||||
never cleared. That means that there is no opportunity for Shorewall
|
||||
to load/reload your ipsets since that cannot be done while there are
|
||||
any current rules using ipsets.</para>
|
||||
|
||||
<para>So:</para>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user