mirror of
https://gitlab.com/shorewall/code.git
synced 2024-11-22 15:43:30 +01:00
Update documentation
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@7836 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
a64b437a2f
commit
1855f85527
@ -116,6 +116,19 @@ Other changes in Shorewall 4.1.2.
|
||||
|
||||
Those parameters that are supplied must have defined values.
|
||||
|
||||
Defaults are:
|
||||
|
||||
object '' ('check' command)
|
||||
directory ''
|
||||
verbosity 1
|
||||
timestamp 0
|
||||
debug 0
|
||||
export 0
|
||||
chains ''
|
||||
log ''
|
||||
log_verbosity -1
|
||||
|
||||
|
||||
Example:
|
||||
|
||||
use lib '/usr/share/shorewall-perl/';
|
||||
@ -132,7 +145,7 @@ Other changes in Shorewall 4.1.2.
|
||||
originating on the firewall must be coded in the POSTROUTING table.
|
||||
|
||||
3) Previously, Shorewall did not range-check the value of the
|
||||
VERBOSITY option in shorewall.conf. Beginnins with Shorewall 4.1.2:
|
||||
VERBOSITY option in shorewall.conf. Beginning with Shorewall 4.1.2:
|
||||
|
||||
a) A VERBOSITY setting outside the range -1 through 2 is rejected.
|
||||
b) After the -v and -q options are applied, the resulting value is
|
||||
|
@ -615,12 +615,12 @@ loc net ACCEPT</programlisting>
|
||||
<title>/usr/share/shorewall-perl/compiler.pl</title>
|
||||
|
||||
<para>While the compiler is normally run indirectly using
|
||||
/sbin/shorewall, it can be run directly as well.<programlisting><command>compiler.pl</command> [ <<emphasis>option</emphasis>> ... ] [ <<emphasis>filename</emphasis>> ]</programlisting></para>
|
||||
/sbin/shorewall, it can be run directly as well.<programlisting><command>compiler.pl</command> [ <emphasis>option</emphasis> ... ] [ <emphasis>filename</emphasis> ]</programlisting></para>
|
||||
|
||||
<para>If a <<emphasis>filename</emphasis>> is given, then the
|
||||
configuration will be compiled output placed in the named file. If
|
||||
<<emphasis>filename</emphasis>> is not given, then the
|
||||
configuration will simply be syntax checked.</para>
|
||||
<para>If a <emphasis>filename</emphasis> is given, then the
|
||||
configuration will be compiled and the output placed in the named file.
|
||||
If <emphasis>filename</emphasis> is not given, then the configuration
|
||||
will simply be syntax checked.</para>
|
||||
|
||||
<para>Options are:</para>
|
||||
|
||||
@ -631,7 +631,11 @@ loc net ACCEPT</programlisting>
|
||||
</simplelist>The <<emphasis>verbosity</emphasis>> is a number
|
||||
between 0 and 2 and corresponds to the VERBOSITY setting in
|
||||
<filename>shorewall.conf</filename>. This setting controls the verbosity
|
||||
of the compiler itself.<simplelist>
|
||||
of the compiler itself.<note>
|
||||
<para>The VERBOSITY setting in the
|
||||
<filename>shorewall.conf</filename> file read by the compiler will
|
||||
determine the default verbosity for the compiled program.</para>
|
||||
</note><simplelist>
|
||||
<member><emphasis role="bold">-e</emphasis></member>
|
||||
|
||||
<member><emphasis role="bold">--export</emphasis></member>
|
||||
@ -662,7 +666,16 @@ loc net ACCEPT</programlisting>
|
||||
|
||||
<para>Example (compiles the configuration in the current directory
|
||||
generating a script named 'firewall' and using VERBOSITY
|
||||
2).<programlisting><emphasis role="bold">/usr/share/shorewall-perl/compiler.pl -v 2 -d . firewall</emphasis></programlisting></para>
|
||||
2).<programlisting><emphasis role="bold">/usr/share/shorewall-perl/compiler.pl -v 2 -d . firewall</emphasis></programlisting><note>
|
||||
<para>The Perl-based compiler does not process
|
||||
<filename>/etc/shorewall/params</filename>. To include definitions
|
||||
in that file, you would need to do something like the
|
||||
following:<programlisting><command>. /usr/share/shorewall/lib.base # In case /etc/shorewall/params does INCLUDE
|
||||
set -a # Export all variables set in /etc/shorewall/params
|
||||
. /etc/shorewall/params
|
||||
set +a
|
||||
/usr/share/shorewall-perl/compiler.pl ...</command></programlisting></para>
|
||||
</note></para>
|
||||
</section>
|
||||
|
||||
<section id="Compiler">
|
||||
@ -698,7 +711,13 @@ loc net ACCEPT</programlisting>
|
||||
<term>$verbose</term>
|
||||
|
||||
<listitem>
|
||||
<para>The verbosity level (0-2).</para>
|
||||
<para>The verbosity level that the compiler will run with
|
||||
(0-2).<note>
|
||||
<para>The VERBOSITY setting in the
|
||||
<filename>shorewall.conf</filename> file read by the compiler
|
||||
will determine the default verbosity for the compiled
|
||||
program.</para>
|
||||
</note></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
@ -21,7 +21,7 @@ Sections, with no Front-Cover, and with no Back-Cover Texts. A copy of the
|
||||
license is included in the section entitled “<a href="GnuCopyright.htm"
|
||||
target="_self">GNU Free Documentation License</a>”.</p>
|
||||
|
||||
<p>2007-11-26</p>
|
||||
<p>2007-12-05</p>
|
||||
<hr style="width: 100%; height: 2px;">
|
||||
|
||||
<h2>Table of Contents</h2>
|
||||
@ -228,7 +228,7 @@ root@wookie:/usr/share/shorewall#</pre>
|
||||
4.0.0-4.0.5 can cause improper handing of PREROUTING and OUTPUT marks when
|
||||
HIGH_ROUTE_MARKS=Yes. Patches are also available to correct this problem:</p>
|
||||
|
||||
<p>Shorewall version 3.2.3-3.2.10, 3.4.0-3.4.7: <a
|
||||
<p>Shorewall version 3.2.3-3.2.11: <a
|
||||
href="http://www1.shorewall.net/pub/shorewall/3.2/shorewall-3.2.11/errata/patches/Shorewall/patch-3.2.11-1.diff">http://www1.shorewall.net/pub/shorewall/3.2/shorewall-3.2.11/errata/patches/Shorewall/patch-3.2.11-1.diff</a></p>
|
||||
|
||||
<p>Shorewall version 3.4.0-3.4.7: <a
|
||||
|
Loading…
Reference in New Issue
Block a user