diff --git a/manpages/shorewall-interfaces.xml b/manpages/shorewall-interfaces.xml index 18d303f32..de77bce44 100644 --- a/manpages/shorewall-interfaces.xml +++ b/manpages/shorewall-interfaces.xml @@ -161,7 +161,7 @@ loc eth2 - Only those interfaces with the option will have their setting - changes; the value assigned to the setting will be the value + changed; the value assigned to the setting will be the value specified (if any) or 1 if no value is given. @@ -188,7 +188,7 @@ loc eth2 - 2 - reply only if the target IP address is local address configured on the incoming interface and the sender's IP - address is part from same subnet on this interface + address is part from same subnet on this interface's address 3 - do not reply for local addresses configured with scope host, only resolutions for global and link @@ -290,11 +290,11 @@ loc eth2 - role="bold">logmartians. Even if you do not specify the option, it is a good idea to specify because your distribution - may be enabling route filtering without you knowing it. + may have enabled route filtering without you knowing it. Only those interfaces with the option will have their setting - changes; the value assigned to the setting will be the value + changed; the value assigned to the setting will be the value specified (if any) or 1 if no value is given. To find out if route filtering is set on a given @@ -510,12 +510,12 @@ loc eth2 - (sets /proc/sys/net/ipv4/conf/interface/accept_source_route to 1). Only set this option if you know what you are doing. - This might represent a security risk and is not usually - needed. + This might represent a security risk and is usually + unneeded. Only those interfaces with the option will have their setting - changes; the value assigned to the setting will be the value + changed; the value assigned to the setting will be the value specified (if any) or 1 if no value is given. @@ -579,7 +579,7 @@ loc eth2 - Suppose you have eth0 connected to a DSL modem and eth1 connected to your local network and that your local subnet is - 192.168.1.0/24. The interface gets it's IP address via DHCP from + 192.168.1.0/24. The interface gets its IP address via DHCP from subnet 206.191.149.192/27. You have a DMZ with subnet 192.168.2.0/24 using eth2. diff --git a/manpages/shorewall-masq.xml b/manpages/shorewall-masq.xml index 081c30f48..cbe1bfa5a 100644 --- a/manpages/shorewall-masq.xml +++ b/manpages/shorewall-masq.xml @@ -409,7 +409,7 @@ Only locally-generated connections will match if this column is non-empty. - When this column is non-empty, the rule applies only if the + When this column is non-empty, the rule matches only if the program generating the output is running under the effective user and/or group specified (or is NOT running under that id if "!" is given). diff --git a/manpages/shorewall-nat.xml b/manpages/shorewall-nat.xml index 1d9bf4e67..c44e46396 100644 --- a/manpages/shorewall-nat.xml +++ b/manpages/shorewall-nat.xml @@ -63,7 +63,7 @@ role="bold">:[digit]] - Interfacees that have the Interfaces that have the EXTERNAL address. If ADD_IP_ALIASES=Yes in shorewall.conf(5), Shorewall will automatically add the EXTERNAL address to this diff --git a/manpages/shorewall-netmap.xml b/manpages/shorewall-netmap.xml index bf3eb0c53..52c742ced 100644 --- a/manpages/shorewall-netmap.xml +++ b/manpages/shorewall-netmap.xml @@ -43,7 +43,7 @@ Must be DNAT or SNAT. If DNAT, traffic entering INTERFACE and addressed to NET1 has - it's destination address rewritten to the corresponding address in + its destination address rewritten to the corresponding address in NET2. If SNAT, traffic leaving INTERFACE with a source address in diff --git a/manpages/shorewall-policy.xml b/manpages/shorewall-policy.xml index 87e010b0d..80029f8e7 100644 --- a/manpages/shorewall-policy.xml +++ b/manpages/shorewall-policy.xml @@ -41,7 +41,7 @@ For $FW and for all of the zones defined in /etc/shorewall/zones, the POLICY for connections from the zone to itself is ACCEPT (with no - logging or TCP connection rate limiting but may be overridden by an + logging or TCP connection rate limiting) but may be overridden by an entry in this file. The overriding entry must be explicit (cannot use "all" in the SOURCE or DEST). @@ -95,7 +95,7 @@ Policy if no match from the rules file is found. - If the policy is other than CONTINUE or NONE then the policy + If the policy is neither CONTINUE nor NONE then the policy may be followed by ":" and one of the following: diff --git a/manpages/shorewall-providers.xml b/manpages/shorewall-providers.xml index d5f8f9fe9..4806b6ce4 100644 --- a/manpages/shorewall-providers.xml +++ b/manpages/shorewall-providers.xml @@ -175,7 +175,7 @@ specified will get outbound traffic load-balanced among them. By default, all interfaces with specified will have the same weight (1). You can change the - weight of an interface by specifiying + weight of an interface by specifying weight where weight is the weight of the route out of this interface. diff --git a/manpages/shorewall-proxyarp.xml b/manpages/shorewall-proxyarp.xml index 99f17e01c..29a7dc854 100644 --- a/manpages/shorewall-proxyarp.xml +++ b/manpages/shorewall-proxyarp.xml @@ -67,8 +67,8 @@ or yes in this column. Otherwise, enter no or No or leave the column empty and Shorewall - will add the route for you. If Shorewall adds the route,the route - will be persistent if the PERSISTENT column contains Yes; otherwise, shorewall stop or http://www.netfilter.org/projects/ulogd/index.html - and can be configured to log all Shorewall message to their own log + and can be configured to log all Shorewall messages to their own log file The following options may be set in shorewall.conf. @@ -262,7 +262,7 @@ role="bold">Yes|No] - If set, the behavior of the 'start' command is change; if no + If set, the behavior of the 'start' command is changed; if no files in /etc/shorewall have been changed since the last successful start or restart command, then the compilation step is skipped and the compiled script that @@ -362,7 +362,7 @@ If this option is set to No then Shorewall won't clear the current traffic control rules during - [re]start. This setting is intended for use by people that prefer to + [re]start. This setting is intended for use by people who prefer to configure traffic shaping when the network interfaces come up rather than when the firewall is started. If that is what you want to do, set TC_ENABLED=Yes and CLEAR_TC=No and do not supply an