More zone definition doc cleanup

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@5233 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-01-15 22:12:16 +00:00
parent b60a2a5b96
commit 9601242e57
2 changed files with 9 additions and 4 deletions

View File

@ -461,13 +461,13 @@ NET_OPTIONS=blacklist,norfc1918</programlisting>
<link linkend="CONTINUE">CONTINUE policy</link> described <link linkend="CONTINUE">CONTINUE policy</link> described
below.</para> below.</para>
<para>Beginning With Shorewall 3.0, you can adjust the order in <para>Beginning with Shorewall 3.0, you can adjust the order in
which Shorewall generates its rules by using special syntax in the which Shorewall generates its rules by using special syntax in the
ZONE column of <filename>/etc/shorewall/zones</filename>. Where a ZONE column of <filename>/etc/shorewall/zones</filename>. Where a
zone is nested in one or more other zones, you may follow the zone is nested in one or more other zones, you may follow the
(sub)zone name by ":" and a comma-separated list of the parent (sub)zone name by ":" and a comma-separated list of the parent
zones. The parent zones must have been defined in earlier records in zones. The parent zones must have been declared in earlier records
this file.</para> in this file.</para>
<para>Example:<blockquote> <para>Example:<blockquote>
<programlisting>#ZONE TYPE OPTIONS <programlisting>#ZONE TYPE OPTIONS
@ -475,6 +475,11 @@ parnt1 ipv4
parnt2 ipv4 parnt2 ipv4
child:parnt1,parnt2 ipv4</programlisting> child:parnt1,parnt2 ipv4</programlisting>
</blockquote></para> </blockquote></para>
<para>Even though zones <emphasis>parnt1</emphasis> and
<emphasis>parnt2</emphasis> are declared before zone
<emphasis>child</emphasis>, Shorewall will generate the rules for
<emphasis>child</emphasis> before either of the parent zones.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>

View File

@ -57,7 +57,7 @@
<para>Where a zone is nested in one or more other zones, you may <para>Where a zone is nested in one or more other zones, you may
follow the (sub)zone name by ":" and a comma-separated list of the follow the (sub)zone name by ":" and a comma-separated list of the
parent zones. The parent zones must have been defined in earlier parent zones. The parent zones must have been declared in earlier
records in this file.</para> records in this file.</para>
<para>Example:</para> <para>Example:</para>