extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-25 09:03:30 +01:00
Code Issues Packages Projects Releases Wiki Activity

Document use of .conf options as variables.

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2011-12-17 07:40:43 -08:00
parent 9d66f34932
commit 57d0550311
1 changed files with 15 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/configuration_file_basics.xml
View File

@ -1326,6 +1326,20 @@ SHELL cat /etc/shorewall/rules.d/*.rules 2&gt; /dev/null || true</programlisting
<para>For optional interfaces, if the interface is not usable at the time
that the firewall starts the all-zero address will be used (0.0.0.0 in
IPv4 and :: in IPv6), resulting in no packets matching the rule.</para>
<para>Beginning with Shorewall 4.4.27, you may also use options in <ulink
url="manpages/shorewall.conf.html">shorewall.conf</ulink> (5) (e.g.,
$BLACKLIST_LOGLEVEL).</para>
<note>
<para>When an option is set to 'No' in shorewall.conf, the corresponding
shell variable is will be empty.</para>
</note>
<note>
<para>Options that were not set in shorewall.conf will expand to their
default value.</para>
</note>
</section>
<section id="Embedded">
@ -1370,7 +1384,7 @@ ACCEPT dmz fw tcp 22</programlisting></para>
following:</para>
<programlisting>package Shorewall::User;
use Shorewall::Config qw/shorewall/;</programlisting>
use Shorewall::Config ( qw/shorewall/ );</programlisting>
<para>To produce output that will be processed by the compiler as if it
were embedded in the file at the point of the script, pass that output to