From 94571c8baf81e2d74750c682ab00ff8d3ebd67fa Mon Sep 17 00:00:00 2001 From: judas_iscariote Date: Fri, 27 May 2005 23:34:33 +0000 Subject: [PATCH] fix multiple typos git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@2191 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs2/User_defined_Actions.xml | 18 +++++++++--------- Shorewall-docs2/VPNBasics.xml | 4 ++-- Shorewall-docs2/upgrade_issues.xml | 16 ++++++++-------- 3 files changed, 19 insertions(+), 19 deletions(-) diff --git a/Shorewall-docs2/User_defined_Actions.xml b/Shorewall-docs2/User_defined_Actions.xml index 3bb366588..9b1c8c059 100755 --- a/Shorewall-docs2/User_defined_Actions.xml +++ b/Shorewall-docs2/User_defined_Actions.xml @@ -58,8 +58,8 @@ underscore characters) as well as valid Netfilter chain names. If you intend to log from the action, the name must have a maximum of 11 characters. It is recommended that the name you select for a new - action begins with with a capital letter; that way, the name won't - conflict with a Shorewall-defined chain name. + action begins with a capital letter; that way, the name won't conflict + with a Shorewall-defined chain name. Beginning with Shorewall-2.0.0-Beta1, the name of the action may be optionally followed by a colon (:) and ACCEPT, DROP @@ -149,8 +149,8 @@ port>:<high port>. This column is ignored if PROTOCOL = all but must be entered if - any of the following ields are supplied. In that case, it is suggested - that this field contain -. + any of the following fields are supplied. In that case, it is + suggested that this field contain -. If your kernel contains multi-port match support, then only a single Netfilter rule will be generated if in this list and in the @@ -266,7 +266,7 @@ LogAndAccept loc fw tcp 22 or Shorewall-defined action will cause each rule in the action to be logged with the specified level (and tag). - The extent to which logging of action rules occur is goverend by the + The extent to which logging of action rules occur is governed by the following: @@ -427,8 +427,8 @@ Reject:REJECT #Common Action for REJECT policy These entries designate the action named Drop as the common action for DROP policies and the common action - Reject as the common action for REJECT policies. - + Reject as the common action for REJECT + policies. The purpose of common actions is: @@ -436,7 +436,7 @@ Reject:REJECT #Common Action for REJECT policy To avoid filling your log with useless clutter. For example, one of the things that the Drop action does is to silently drop SMB - traffic by invoking the DropSMB action. + traffic by invoking the DropSMB action. @@ -457,7 +457,7 @@ Reject:REJECT #Common Action for REJECT policy
- Creating an Action using an Extension Script + Creating an Action using an Extension Script There may be cases where you wish to create a chain with rules that can't be constructed using the tools defined in the action.template. In diff --git a/Shorewall-docs2/VPNBasics.xml b/Shorewall-docs2/VPNBasics.xml index dedfd7995..0621ac534 100644 --- a/Shorewall-docs2/VPNBasics.xml +++ b/Shorewall-docs2/VPNBasics.xml @@ -98,7 +98,7 @@ Local-host-to-local-gateway. This traffic has a source address in the local network or on the gateway itself. The destination IP address is that of a remote host; - either the remote gateway itself or a host behind that gaeway. + either the remote gateway itself or a host behind that gateway. @@ -115,7 +115,7 @@
What does this mean with Shorewall? - When Shorewall is installed on a VPN gateway system, it catagorizes + When Shorewall is installed on a VPN gateway system, it categorizes the VPN-related traffic slightly differently: diff --git a/Shorewall-docs2/upgrade_issues.xml b/Shorewall-docs2/upgrade_issues.xml index 630cb6ba3..9b51338cd 100644 --- a/Shorewall-docs2/upgrade_issues.xml +++ b/Shorewall-docs2/upgrade_issues.xml @@ -21,7 +21,7 @@ 2004 - Thomas M. Eastep + 2005 Thomas M. Eastep @@ -176,7 +176,7 @@ DNAT loc loc:192.168.1.12 tcp 80 - 130.252.100.69

@@ -211,9 +211,9 @@ DNAT loc loc:192.168.1.12 tcp 80 - 130.252.100.69

iptables then those commands must also be written to the restore file (a temporary file in /var/lib/shorewall that is renamed - /var/lib/shorewall/restore-base at the - completeion of the /sbin/shorewall command). The - following functions should be of help: + /var/lib/shorewall/restore-base at the completion + of the /sbin/shorewall command). The following + functions should be of help: @@ -306,7 +306,7 @@ DNAT loc loc:192.168.1.12 tcp 80 - 130.252.100.69

The NAT_BEFORE_RULES option has been removed from shorewall.conf. The behavior of Shorewall 2.0 is as if NAT_BEFORE_RULES=No had been specified. In other words, DNAT - rules now always take precidence over one-to-one NAT + rules now always take precedence over one-to-one NAT specifications. @@ -587,8 +587,8 @@ z1 z2 NONE z2 z1 NONE Note that NONE policies are generally used in pairs - unless there is asymetric routing where only the traffic on one - direction flows through the firewall and you are using a NONE polciy + unless there is asymmetric routing where only the traffic on one + direction flows through the firewall and you are using a NONE policy in the other direction.