From 63e6973250b343d26bda9ffa7c101df14572d242 Mon Sep 17 00:00:00 2001 From: mhnoyes Date: Thu, 25 Dec 2003 17:17:31 +0000 Subject: [PATCH] fixed quotes git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@956 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs/IPSEC.xml | 34 +++++++++++++++++----------------- Shorewall-docs/Install.xml | 32 ++++++++++++++++---------------- 2 files changed, 33 insertions(+), 33 deletions(-) diff --git a/Shorewall-docs/IPSEC.xml b/Shorewall-docs/IPSEC.xml index 06bcbe94d..cba448471 100644 --- a/Shorewall-docs/IPSEC.xml +++ b/Shorewall-docs/IPSEC.xml @@ -30,8 +30,8 @@ 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 "GNU Free Documentation License". + Texts. A copy of the license is included in the section entitled + GNU Free Documentation License. @@ -195,7 +195,7 @@ conn packetdefault You need to define a zone for the remote subnet or include it in your local zone. In this example, we'll assume that you have created - a zone called "vpn" to represent the remote subnet. + a zone called vpn to represent the remote subnet. /etc/shorewall/zones localZONEDISPLAY
 At both systems, ipsec0 would be included in - /etc/shorewall/interfaces as a "vpn" interface: + /etc/shorewall/interfaces as a vpn interface: /etc/shorewall/interfaces system local & remoteZONEINTERFACEBROADCASTOPTIONSvpnipsec0
 - You will need to allow traffic between the "vpn" zone and - the "loc" zone -- if you simply want to admit all traffic in - both directions, you can use the policy file: + You will need to allow traffic between the vpn zone + and the loc zone -- if you simply want to admit all + traffic in both directions, you can use the policy file: /etc/shorewall/policy local & remoteSOURCE On systems A, you will need to allow traffic between the - "vpn1" zone and the "loc" zone as well as between - "vpn2" and the "loc" zone -- if you simply want to admit - all traffic in both directions, you can use the following policy file - entries on all three gateways: + vpn1 zone and the loc zone as well as + between vpn2 and the loc zone -- if you + simply want to admit all traffic in both directions, you can use the + following policy file entries on all three gateways:
/etc/shorewall/policy system A @@ -577,9 +577,9 @@ conn packetdefault
On systems B and C, you will need to allow traffic between the - "vpn" zone and the "loc" zone -- if you simply want to - admit all traffic in both directions, you can use the following policy - file entries on all three gateways: + vpn zone and the loc zone -- if you simply + want to admit all traffic in both directions, you can use the following + policy file entries on all three gateways: /etc/shorewall/policy system B & C @@ -692,7 +692,7 @@ conn packetdefault You need to define a zone for the laptop or include it in your local zone. In this example, we'll assume that you have created a - zone called "vpn" to represent the remote host. + zone called vpn to represent the remote host.
/etc/shorewall/zones localZONEDISPLAY You will need to configure /etc/shorewall/interfaces and establish - your "through the tunnel" policy as shown under the first + your through the tunnel policy as shown under the first example above. @@ -808,7 +808,7 @@ conn packetdefault a different updown script that adds the remote station to the appropriate zone when the connection comes up and that deletes the remote station when the connection comes down. For example, when 134.28.54.2 connects for the - vpn2 zone the 'up' part of the script will issue the command": + vpn2 zone the 'up' part of the script will issue the command: /sbin/shorewall add ipsec0:134.28.54.2 vpn2 diff --git a/Shorewall-docs/Install.xml b/Shorewall-docs/Install.xml index 418db52a8..217592c68 100644 --- a/Shorewall-docs/Install.xml +++ b/Shorewall-docs/Install.xml @@ -30,8 +30,8 @@ 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 "GNU Free Documentation License". + Texts. A copy of the license is included in the section entitled + GNU Free Documentation License. @@ -54,7 +54,7 @@ If you have RedHat 7.2 and are running iptables version 1.2.3 (at - a shell prompt, type "/sbin/iptables --version"), you must + a shell prompt, type /sbin/iptables --version), you must upgrade to version 1.2.4 either from the RedHat update site or from the Shorewall Errata @@ -95,12 +95,12 @@ YOU CAN NOT SIMPLY INSTALL - THE RPM AND ISSUE A "shorewall start" COMMAND. SOME + THE RPM AND ISSUE A shorewall start COMMAND. SOME CONFIGURATION IS REQUIRED BEFORE THE FIREWALL WILL START. IF YOU - ISSUE A "start" COMMAND AND THE FIREWALL FAILS TO START, - YOUR SYSTEM WILL NO LONGER ACCEPT ANY NETWORK TRAFFIC. IF THIS - HAPPENS, ISSUE A "shorewall clear" COMMAND TO RESTORE - NETWORK CONNECTIVITY. + ISSUE A start COMMAND AND THE FIREWALL FAILS TO + START, YOUR SYSTEM WILL NO LONGER ACCEPT ANY NETWORK TRAFFIC. IF + THIS HAPPENS, ISSUE A shorewall clear COMMAND TO + RESTORE NETWORK CONNECTIVITY. @@ -124,7 +124,7 @@ cd to the shorewall directory (the version is encoded in the - directory name as in "shorewall-1.1.10"). + directory name as in shorewall-1.1.10). @@ -185,8 +185,8 @@ Install the .lrp To install my version of Shorewall on a fresh Bering disk, simply - replace the "shorwall.lrp" file on the image with the file that - you downloaded. See the two-interface + replace the shorwall.lrp file on the image with the file + that you downloaded. See the two-interface QuickStart Guide for information about further steps required. @@ -213,9 +213,9 @@ rpm -Uvh <shorewall rpm file> - If you are installing version 1.2.0 and have one of the 1.2.0 - Beta RPMs installed, you must use the "--oldpackage" option - to rpm. + If you are installing version 1.2.0 and have one of the 1.2.0 + Beta RPMs installed, you must use the --oldpackage + option to rpm. rpm -Uvh --oldpackage shorewall-1.2-0.noarch.rpm @@ -284,7 +284,7 @@ cd to the shorewall directory (the version is encoded in the - directory name as in "shorewall-3.0.1"). + directory name as in shorewall-3.0.1). @@ -364,6 +364,6 @@
Uninstall/Fallback - See "Fallback and Uninstall". + See Fallback and Uninstall.
\ No newline at end of file