fixed quotes

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@953 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
mhnoyes 2003-12-25 16:42:17 +00:00
parent 5e858d2555
commit ccba02be5d

View File

@ -30,15 +30,14 @@
document under the terms of the GNU Free Documentation License, Version document under the terms of the GNU Free Documentation License, Version
1.2 or any later version published by the Free Software Foundation; with 1.2 or any later version published by the Free Software Foundation; with
no Invariant Sections, with no Front-Cover, and with no Back-Cover no Invariant Sections, with no Front-Cover, and with no Back-Cover
Texts. A copy of the license is included in the section entitled &#34;<ulink Texts. A copy of the license is included in the section entitled
url="GnuCopyright.htm">GNU Free Documentation License</ulink>&#34;.</para> <quote><ulink url="GnuCopyright.htm">GNU Free Documentation License</ulink></quote>.</para>
</legalnotice> </legalnotice>
</articleinfo> </articleinfo>
<para>Shorewall includes built-in support for a wide range of VPN solutions. <para>Shorewall includes built-in support for a wide range of VPN solutions.
If you have need for a tunnel type that does not have explicit support, you If you have need for a tunnel type that does not have explicit support, you
can generally describe the tunneling software using &#34;generic can generally describe the tunneling software using <quote>generic tunnels</quote>.</para>
tunnels&#34;</para>
<section> <section>
<title>Bridging two Masqueraded Networks</title> <title>Bridging two Masqueraded Networks</title>
@ -66,8 +65,8 @@
</listitem> </listitem>
<listitem> <listitem>
<para>The tunnel interface on system A is &#34;tun0&#34; and the <para>The tunnel interface on system A is <quote>tun0</quote> and the
tunnel interface on system B is also &#34;tun0&#34;.</para> tunnel interface on system B is also <quote>tun0</quote>.</para>
</listitem> </listitem>
</orderedlist> </orderedlist>
@ -242,9 +241,9 @@
</tgroup> </tgroup>
</informaltable> </informaltable>
<para>You will need to allow traffic between the &#34;vpn&#34; zone and <para>You will need to allow traffic between the <quote>vpn</quote> zone
the &#34;loc&#34; zone on both systems -- if you simply want to admit all and the <quote>loc</quote> zone on both systems -- if you simply want to
traffic in both directions, you can use the policy file:</para> admit all traffic in both directions, you can use the policy file:</para>
<informaltable> <informaltable>
<tgroup cols="4"> <tgroup cols="4">