forked from extern/shorewall_code
Cosmetic change to rules manpage
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8621 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
931d316e04
commit
10025d41b9
@ -181,7 +181,7 @@
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>ACCEPT!</term>
|
||||
<term><emphasis role="bold">ACCEPT!</emphasis></term>
|
||||
|
||||
<listitem>
|
||||
<para>like ACCEPT but exempts the rule from being suppressed
|
||||
@ -210,7 +210,7 @@
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>DROP!</term>
|
||||
<term><emphasis role="bold">DROP!</emphasis></term>
|
||||
|
||||
<listitem>
|
||||
<para>like DROP but exempts the rule from being suppressed by
|
||||
@ -229,7 +229,7 @@
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>REJECT!</term>
|
||||
<term><emphasis role="bold">REJECT!</emphasis></term>
|
||||
|
||||
<listitem>
|
||||
<para>like REJECT but exempts the rule from being suppressed
|
||||
@ -327,7 +327,7 @@
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>CONTINUE!</term>
|
||||
<term><emphasis role="bold">CONTINUE!</emphasis></term>
|
||||
|
||||
<listitem>
|
||||
<para>like CONTINUE but exempts the rule from being suppressed
|
||||
@ -356,7 +356,7 @@
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>QUEUE!</term>
|
||||
<term><emphasis role="bold">QUEUE!</emphasis></term>
|
||||
|
||||
<listitem>
|
||||
<para>like QUEUE but exempts the rule from being suppressed by
|
||||
@ -379,7 +379,7 @@
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>NFQUEUE!</term>
|
||||
<term><emphasis role="bold">NFQUEUE!</emphasis></term>
|
||||
|
||||
<listitem>
|
||||
<para>like NFQUEUE but exempts the rule from being suppressed
|
||||
@ -615,11 +615,11 @@
|
||||
IP/MAC/subnet address as described above (e.g., <emphasis
|
||||
role="bold">loc:eth1:192.168.1.5</emphasis>).</para>
|
||||
|
||||
<para>It is important to note that when <emphasis role="bold">using
|
||||
Shorewall-shell</emphasis> and specifying an address list that will
|
||||
be split (i.e., a comma separated list), there is a subtle behavior
|
||||
which has the potential to cause confusion. Consider the two
|
||||
examples below:</para>
|
||||
<para>It is important to note that when <emphasis
|
||||
role="bold">using Shorewall-shell</emphasis> and specifying an
|
||||
address list that will be split (i.e., a comma separated list),
|
||||
there is a subtle behavior which has the potential to cause
|
||||
confusion. Consider the two examples below:</para>
|
||||
</blockquote>
|
||||
|
||||
<para>Examples:</para>
|
||||
@ -645,6 +645,7 @@
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<blockquote>
|
||||
<para>That is, the interface name must be explicitly stated for
|
||||
each member of the comma separated list. Again, this distinction
|
||||
|
Loading…
Reference in New Issue
Block a user