From 3aa0c59c48485112ac7fcbb5fd471bfbd9db3e34 Mon Sep 17 00:00:00 2001 From: mhnoyes Date: Wed, 24 Dec 2003 14:47:55 +0000 Subject: [PATCH] changed from numbered sect1 tags to recursive section tags git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@927 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs/upgrade_issues.xml | 76 +++++++++++++++---------------- 1 file changed, 38 insertions(+), 38 deletions(-) diff --git a/Shorewall-docs/upgrade_issues.xml b/Shorewall-docs/upgrade_issues.xml index 915cd9d44..769edf465 100644 --- a/Shorewall-docs/upgrade_issues.xml +++ b/Shorewall-docs/upgrade_issues.xml @@ -20,7 +20,7 @@ - +
Important It is important that you read all of the sections on this page where the version number mentioned in the section title is later than what you are currently running. @@ -45,8 +45,8 @@ You can use the shorewall check command to see the groups associated with each of your zones. - - +
+
Version >= 1.4.8 @@ -55,8 +55,8 @@ - - +
+
Version >= 1.4.6 @@ -77,20 +77,20 @@ zone eth1:192.168.1.0/24,192.168.2.0/24 - - +
+
Version >= 1.4.4 If you are upgrading from 1.4.3 and have set the LOGMARKER variable in /etc/shorewall/shorewall.conf, then you must set the new LOGFORMAT variable appropriately and remove your setting of LOGMARKER. - - +
+
Version 1.4.4 If you have zone names that are 5 characters long, you may experience problems starting Shorewall because the in a logging rule is too long. Upgrade to Version 1.4.4a to fix this problem. - - +
+
Version >= 1.4.2 There are some cases where you may want to handle traffic from a particular group to itself. While I personally think that such a setups are ridiculous, there are two cases covered in this documentation where it can occur: @@ -110,8 +110,8 @@ zone eth1:192.168.1.0/24,192.168.2.0/24 If you have either of these cases, you will want to review the current documentation and change your configuration accordingly. - - +
+
Version >= 1.4.1 @@ -166,8 +166,8 @@ z2 z1 NONE - - +
+
Version 1.4.1 @@ -176,8 +176,8 @@ z2 z1 NONE - - +
+
Version >= 1.4.0 @@ -248,8 +248,8 @@ error: failed dependencies:iproute is needed by shorewall-1.4.0-1 - - +
+
Version 1.4.0 @@ -270,8 +270,8 @@ error: failed dependencies:iproute is needed by shorewall-1.4.0-1 - - +
+
Version >= 1.3.14 Beginning in version 1.3.14, Shorewall treats entries in /etc/shorewall/masq differently. The change involves entries with an interface name in the SUBNET (second) column: @@ -340,8 +340,8 @@ eth0 192.168.1.0/24 206.124.146.176 Version 1.3.14 also introduced simplified ICMP echo-request (ping) handling. The option OLD_PING_HANDLING=Yes in /etc/shorewall/shorewall.conf is used to specify that the old (pre-1.3.14) ping handling is to be used (If the option is not set in your /etc/shorewall/shorewall.conf then OLD_PING_HANDLING=Yes is assumed). I don't plan on supporting the old handling indefinitely so I urge current users to migrate to using the new handling as soon as possible. See the 'Ping' handling documentation for details. - - +
+
Version 1.3.10 @@ -353,8 +353,8 @@ rpm -Uvh --force shorewall-1.3.10-1.noarch.rpm - - +
+
Version >= 1.3.9 @@ -363,8 +363,8 @@ rpm -Uvh --force shorewall-1.3.10-1.noarch.rpm - - +
+
Version >= 1.3.8 @@ -373,8 +373,8 @@ rpm -Uvh --force shorewall-1.3.10-1.noarch.rpm - - +
+
Version >= 1.3.7 @@ -391,8 +391,8 @@ run_iptables -A icmpdef -p ICMP --icmp-type parameter-problem -j ACCEPT - - +
+
Upgrading Bering to Shorewall >= 1.3.3 @@ -427,8 +427,8 @@ ACCEPT loc fw tcp 80 - - +
+
Version 1.3.6 and 1.3.7 @@ -461,8 +461,8 @@ run_iptables -A common -p tcp --tcp-flags ACK,FIN,RST ACK -j ACCEPT - - +
+
Versions >= 1.3.5 @@ -491,8 +491,8 @@ REDIRECT loc 3128 tcp 80 - - +
+
Version >= 1.3.2 @@ -501,5 +501,5 @@ REDIRECT loc 3128 tcp 80 - +