holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

fixed quotes

Browse Source 
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
1 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Shorewall-docs/GenericTunnels.xml
View File

@ -30,15 +30,14 @@
document under the terms of the GNU Free Documentation License, Version
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
Texts. A copy of the license is included in the section entitled &#34;<ulink
url="GnuCopyright.htm">GNU Free Documentation License</ulink>&#34;.</para>
Texts. A copy of the license is included in the section entitled
<quote><ulink url="GnuCopyright.htm">GNU Free Documentation License</ulink></quote>.</para>
</legalnotice>
</articleinfo>
<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
can generally describe the tunneling software using &#34;generic
tunnels&#34;</para>
can generally describe the tunneling software using <quote>generic tunnels</quote>.</para>
<section>
<title>Bridging two Masqueraded Networks</title>
@ -66,8 +65,8 @@
</listitem>
<listitem>
<para>The tunnel interface on system A is &#34;tun0&#34; and the
tunnel interface on system B is also &#34;tun0&#34;.</para>
<para>The tunnel interface on system A is <quote>tun0</quote> and the
tunnel interface on system B is also <quote>tun0</quote>.</para>
</listitem>
</orderedlist>
@ -242,9 +241,9 @@
</tgroup>
</informaltable>
<para>You will need to allow traffic between the &#34;vpn&#34; zone and
the &#34;loc&#34; zone on both systems -- if you simply want to admit all
traffic in both directions, you can use the policy file:</para>
<para>You will need to allow traffic between the <quote>vpn</quote> zone
and the <quote>loc</quote> zone on both systems -- if you simply want to
admit all traffic in both directions, you can use the policy file:</para>
<informaltable>
<tgroup cols="4">