Fix formatting in exclusion manpage

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5236 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-01-16 21:22:28 +00:00
parent aec586f75f
commit a7140da85b
3 changed files with 22 additions and 22 deletions

View File

@ -102,8 +102,10 @@
<listitem>
<para>Packet Source.</para>
<para>The name of an interface, an address (host or net) or an
interface name followed by ":" and a host or net address.</para>
<para>The name of an <replaceable>interface</replaceable>, an
<replaceable>address</replaceable> (host or net) or an
<replaceable>interface</replaceable> name followed by ":" and a host
or net <replaceable>address</replaceable>.</para>
</listitem>
</varlistentry>
@ -148,20 +150,20 @@
role="bold">all</emphasis>|<emphasis>ipp2p-option</emphasis>|<emphasis>port-name-or-number</emphasis>[,<emphasis>port-name-or-number</emphasis>]...}</term>
<listitem>
<para>Destination Port number. If the PROTOCOL is <emphasis
role="bold">ipp2p</emphasis> then this column must contain an
<emphasis>ipp2p-option</emphasis> ("iptables -m ipp2p --help")
without the leading "--". If no option is given in this column,
<emphasis role="bold">ipp2p</emphasis> is assumed.</para>
<para>Service name from services(5) or <emphasis>port
number</emphasis>. May only be specified if the protocol is
<emphasis role="bold">tcp</emphasis> or <emphasis
<para>Destination Port number. Service name from services(5) or
<emphasis>port number</emphasis>. May only be specified if the
protocol is <emphasis role="bold">tcp</emphasis> or <emphasis
role="bold">udp</emphasis> (6 or 17).</para>
<para>You may place a comma-separated list of port names or numbers
in this column if your kernel and iptables include multiport match
support.</para>
<para>If the PROTOCOL is <emphasis role="bold">ipp2p</emphasis> then
this column must contain an <emphasis>ipp2p-option</emphasis>
("iptables -m ipp2p --help") without the leading "--". If no option
is given in this column, <emphasis role="bold">ipp2p</emphasis> is
assumed.</para>
</listitem>
</varlistentry>
@ -172,7 +174,7 @@
role="bold">all</emphasis>|<emphasis>port-name-or-number</emphasis>[,<emphasis>port-name-or-number</emphasis>]...}</term>
<listitem>
<para>Source Port Service name from services(5) or <emphasis>port
<para>Service name from services(5) or <emphasis>port
number</emphasis>. May only be specified if the protocol is TCP or
UDP (6 or 17).</para>
@ -274,4 +276,4 @@
shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5),
shorewall-tos(5), shorewall-tunnels(5), shorewall-zones(5)</para>
</refsect1>
</refentry>
</refentry>

View File

@ -15,11 +15,8 @@
<refsynopsisdiv>
<cmdsynopsis>
<command>!</command>
<arg choice="plain">address-or-range</arg>
<arg rep="repeat">,address-or-range</arg>
<arg choice="plain"
rep="repeat"><option>!</option><replaceable>address-or-range</replaceable>[,<replaceable>address-or-range</replaceable>]</arg>
</cmdsynopsis>
</refsynopsisdiv>

View File

@ -851,9 +851,10 @@
role="bold">0</emphasis>|<emphasis role="bold">1</emphasis>]</term>
<listitem>
<para>Traditionally, Shorewall has created rules for the complete
matrix of Networks defined by the zones, interfaces and hosts files.
Any traffic that didn't correspond to an element of that matrix was
<para>Traditionally, Shorewall has created rules for <ulink
url="../ScalabilityAndPerformance.html">the complete matrix of host
groups defined by the zones, interfaces and hosts files</ulink>. Any
traffic that didn't correspond to an element of that matrix was
rejected in one of the built-in changes. When the matrix is sparse,
this results in lots of largely useless rules.</para>
@ -1167,7 +1168,7 @@
<member>1 — Major progress messages displayed</member>
<member>2 — All progress messages displayed (old default
<member>2 — All progress messages displayed (pre Shorewall-3.2.0
behavior)</member>
</simplelist>