Formatting changes in the config file basics doc

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2757 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-09-30 14:15:51 +00:00
parent 9b293f5ed6
commit 9c956521d8

View File

@ -551,9 +551,9 @@ DNAT net loc:192.168.1.3 tcp 4000:4100</programlisting>
to distinguish them from variables used internally within the Shorewall to distinguish them from variables used internally within the Shorewall
programs</para> programs</para>
<example> <para>Example:</para>
<title>Using Shell Variables</title>
<blockquote>
<programlisting>&nbsp;&nbsp;&nbsp; /etc/shorewall/params <programlisting>&nbsp;&nbsp;&nbsp; /etc/shorewall/params
NET_IF=eth0 NET_IF=eth0
@ -568,6 +568,7 @@ DNAT net loc:192.168.1.3 tcp 4000:4100</programlisting>
net eth0 130.252.100.255 routefilter,norfc1918 net eth0 130.252.100.255 routefilter,norfc1918
</programlisting> </programlisting>
</blockquote>
<para>Variables may be used anywhere in the other configuration <para>Variables may be used anywhere in the other configuration
files.</para> files.</para>
@ -595,8 +596,7 @@ DNAT net loc:192.168.1.3 tcp 4000:4100</programlisting>
</listitem> </listitem>
<listitem> <listitem>
<para>Should not assume anything about the state of <para>Should not assume anything about the state of Shorewall.</para>
Shorewall.</para>
</listitem> </listitem>
<listitem> <listitem>
@ -607,10 +607,10 @@ DNAT net loc:192.168.1.3 tcp 4000:4100</programlisting>
<para>One possible use of this feature is to compensate for recent Linux <para>One possible use of this feature is to compensate for recent Linux
behavior in which the identity of network interfaces varies from boot to behavior in which the identity of network interfaces varies from boot to
boot (what is <filename class="devicefile">eth0</filename> after one boot (what is <filename class="devicefile">eth0</filename> after one boot
boot may be <filename class="devicefile">eth1</filename> after the may be <filename class="devicefile">eth1</filename> after the next).
next). <trademark>SuSE</trademark> users, for example, can take the <trademark>SuSE</trademark> users, for example, can take the following
following approach:</para> approach:</para>
<programlisting>wookie:~ # lspci <programlisting>wookie:~ # lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04) 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
@ -633,7 +633,6 @@ wookie:~ #</programlisting>
<programlisting>EXT_IF=$(getcfg-interface bus-pci-0000:00:05.0) <programlisting>EXT_IF=$(getcfg-interface bus-pci-0000:00:05.0)
INT_IF=$(getcfg-interface bus-pci-0000:00:03.0)</programlisting> INT_IF=$(getcfg-interface bus-pci-0000:00:03.0)</programlisting>
</example>
<caution> <caution>
<para>The <command>shorewall save</command> and <command>shorewall <para>The <command>shorewall save</command> and <command>shorewall
@ -641,7 +640,7 @@ INT_IF=$(getcfg-interface bus-pci-0000:00:03.0)</programlisting>
workaround for unstable interface names. In particular, you should set workaround for unstable interface names. In particular, you should set
OPTIONS="" in <filename>/etc/default/shorewall</filename> or OPTIONS="" in <filename>/etc/default/shorewall</filename> or
<filename>/etc/sysconfig/shorewall</filename> so that the "-f" option <filename>/etc/sysconfig/shorewall</filename> so that the "-f" option
will not be specified on startup at boot time. </para> will not be specified on startup at boot time.</para>
</caution> </caution>
</section> </section>