diff --git a/docs/Actions.xml b/docs/Actions.xml
index aae4e4176..bdd10a822 100644
--- a/docs/Actions.xml
+++ b/docs/Actions.xml
@@ -224,6 +224,9 @@ ACCEPT - - tcp 135,139,445
When using Shorewall 4.4.16 or later, there are no restrictions
regarding which targets can be used within your action.
+
+ The SOURCE and DEST columns in the action file may not include
+ zone names; those are given when the action is invoked.
@@ -578,7 +581,7 @@ add_rule $chainref, '-d 224.0.0.0/4 -j DROP';
Limit:none:SSHA,3,60 net $FW tcp 22
Using Shorewall 4.4.16 or later, you can also invoke the action this
- way:
+ way:
#ACTION SOURCE DEST PROTO DEST PORT(S)
Limit(SSHA,3,60):none net $FW tcp 22
diff --git a/docs/LennyToSqueeze.xml b/docs/LennyToSqueeze.xml
index 1bc54f48b..9d2b556b9 100644
--- a/docs/LennyToSqueeze.xml
+++ b/docs/LennyToSqueeze.xml
@@ -120,7 +120,7 @@
- In Squeeze, there are five packages:
+ In Squeeze, there are six slightly different packages:
@@ -144,6 +144,12 @@
runs IPv6 firewall scripts.
+
+ shorewall-init — Allows the firewall to be closed before
+ interfaces are brought up and also allows the firewall to react to
+ interfaces coming up and going down.
+
+
shorewall-doc — Documentation.
@@ -223,8 +229,8 @@
by Shorewall 4.4.x
You should not be receiving this error if you are upgrading
- from Lenny since BRIDGING=Yes did not work in that
- release
+ from Lenny since BRIDGING=Yes did not work in that release
+ eitherIf you are upgrading from a release using a kernel
earlier than 2.6.20, then BRIDGING=Yes did work correctly with
Shorewall-shell.
@@ -424,8 +430,8 @@ loc Local The local LAN
# OPTIONS OPTIONS
You will need to add an entry for your firewall zone. The default
- name for the firewall zone is 'fw' but may have been overriden using
- the FW option in
+ name for the firewall zone is 'fw' but may have been overriden in your
+ old configuration using the FW option in
shorewall.conf.#ZONE TYPE OPTIONS IN OUT