From da92ac965bc015b3c4fb32d887f80417d3f445c1 Mon Sep 17 00:00:00 2001 From: teastep Date: Sat, 26 Nov 2005 19:31:15 +0000 Subject: [PATCH] Remove another anachronism from the setup guide git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3073 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs2/shorewall_setup_guide.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Shorewall-docs2/shorewall_setup_guide.xml b/Shorewall-docs2/shorewall_setup_guide.xml index a9a79957f..9115d6b30 100644 --- a/Shorewall-docs2/shorewall_setup_guide.xml +++ b/Shorewall-docs2/shorewall_setup_guide.xml @@ -123,7 +123,7 @@ As each file is introduced, I suggest that you look through the actual file on your system -- each file contains detailed configuration - instructions and some contain default entries. + instructions. Shorewall views the network where it is running as being composed of a set of zones. In this guide, we will use the following zones: @@ -248,7 +248,7 @@ dmz ipv4 A to the firewall and are also allowed from the firewall to zone B DOES NOT mean that these connections are allowed from zone A to zone B (in other words, policies and rules - involving the firewall zone are not transitibe). It rather means that you + involving the firewall zone are not transitive). It rather means that you can have a proxy running on the firewall that accepts a connection from zone A and then establishes its own separate connection from the firewall to zone B.