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

Manpage updates

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@6196 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-05-02 18:12:53 +00:00
parent 79d57a7751
commit 38a76d35ae
2 changed files with 21 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
manpages/shorewall-rules.xml
View File

@ -715,8 +715,10 @@
<para>2. No port ranges are included or your kernel and iptables <para>2. No port ranges are included or your kernel and iptables
contain extended multiport match support.</para> contain extended multiport match support.</para>
<para>Otherwise, a separate rule will be generated for each <para>Otherwise, unless you are using <ulink
port.</para> url="../Shorewall-perl.html">Shorewall-perl</ulink>, a separate rule
will be generated for each port. Shorewall-perl does not
automatically break up lists into individual rules.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -752,8 +754,10 @@
<para>2. No port ranges are included or your kernel and iptables <para>2. No port ranges are included or your kernel and iptables
contain extended multiport match support.</para> contain extended multiport match support.</para>
<para>Otherwise, a separate rule will be generated for each <para>Otherwise, unless you are using <ulink
port.</para> url="../Shorewall-perl.html">Shorewall-perl</ulink>, a separate
rule will be generated for each port. Shorewall-perl does not
automatically break up lists into individual rules.</para>
</blockquote> </blockquote>
</listitem> </listitem>
</varlistentry> </varlistentry>

13
manpages/shorewall.conf.xml
View File

@ -705,6 +705,19 @@
</listitem> </listitem>
</varlistentry> </varlistentry>
<varlistentry>
<term><emphasis role="bold">LOGTAGONLY=</emphasis>[<emphasis
role="bold">Yes</emphasis>|<emphasis role="bold">No</emphasis>]</term>
<listitem>
<para>Using the default LOGFORMAT, chain names may not exceed 11
characters or truncation of the log prefix may occur. Longer chain
names may be used with log tags if you set LOGTAGONLY=Yes. With
LOGTAGONLY=Yes, if a log tag is specified then the tag is included
in the log prefix in place of the chain name.</para>
</listitem>
</varlistentry>
<varlistentry> <varlistentry>
<term><emphasis role="bold">MACLIST_DISPOSITION=</emphasis>[<emphasis <term><emphasis role="bold">MACLIST_DISPOSITION=</emphasis>[<emphasis
role="bold">ACCEPT</emphasis>|<emphasis role="bold">ACCEPT</emphasis>|<emphasis