diff --git a/Shorewall-docs2/Documentation_Index.xml b/Shorewall-docs2/Documentation_Index.xml
index ed06eb47c..fef48c57c 100644
--- a/Shorewall-docs2/Documentation_Index.xml
+++ b/Shorewall-docs2/Documentation_Index.xml
@@ -15,7 +15,7 @@
- 2005-05-12
+ 2005-08-11
2001-2005
@@ -42,20 +42,6 @@
in both Docbook XML and HTML formats.
-
- Are you running Shorewall on Mandrake
- Linux with a two-interface setup?
-
- If so and if you configured your system while running a Mandrake
- release earlier than 10.0 final then this documentation will not apply
- directly to your environment. If you want to use the documentation that
- you find here, you will want to consider uninstalling what you have and
- installing a configuration that matches this documentation. See the Two-interface QuickStart Guide for
- details.
-
-
Introduction to
@@ -72,6 +58,20 @@
Please review the appropriate guide before trying to use this documentation
directly.
+
+ Are you running Shorewall on Mandrake
+ Linux with a two-interface setup?
+
+ If so and if you configured your system while running a Mandrake
+ release earlier than 10.0 final then this documentation will not apply
+ directly to your environment. If you want to use the documentation that
+ you find here, you will want to consider uninstalling what you have and
+ installing a configuration that matches this documentation. See the Two-interface QuickStart Guide for
+ details.
+
+
2.6 Kernel
diff --git a/Shorewall-docs2/ipsets.xml b/Shorewall-docs2/ipsets.xml
index 8dbbe0b35..4f057033e 100644
--- a/Shorewall-docs2/ipsets.xml
+++ b/Shorewall-docs2/ipsets.xml
@@ -15,7 +15,7 @@
- 2005-05-09
+ 2005-07-27
2005
@@ -52,7 +52,7 @@
Blacklists. Ipsets provide an effecient way to represent large
sets of addresses and you can maintain the lists without the need to
- restart or even refresh your Shorewall configuration.
+ restart or even refresh your Shorewall configuration.
@@ -185,4 +185,32 @@ ipset -B Blacklist 206.124.146.177 -b SMTP
Now only port 25 will be blocked from 206.124.146.177.
+
+
+ Defining Dynamic Zones using Ipsets
+
+ The use of ipsets provides a much better way to define dynamic zones
+ than is provided by the native Shorewall implementation. To define a
+ dynamic zone of hosts dyn that interface
+ through interface eth3, use:
+
+ /etc/shorewall/zones:
+
+ #ZONE IPSEC OPTIONS IN OPTIONS OUT OPTIONS
+dyn No
+
+ /etc/shorewall/interfaces:
+
+ #ZONE INTERFACE OPTIONS
+- eth3 …
+
+ /etc/shorewall/hosts:
+
+ #ZONE HOSTS OPTIONS
+dyn eth3:+Dyn
+
+ Now create an ipmap named Dyn and
+ you're all set. You can add and delete addresses from Dyn without having
+ to touch Shorewall.
+
\ No newline at end of file