Update version and release docs to start work on 4.3.13

Shorewall-lite/fallback.sh

@@ -28,7 +28,7 @@
 #       shown below. Simply run this script to revert to your prior version of
 #       Shoreline Firewall.
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall-lite/install.sh

@@ -22,7 +22,7 @@
 #       Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall-lite/shorewall-lite.spec

@@ -1,5 +1,5 @@
 %define name shorewall-lite
-%define version 4.3.12
+%define version 4.3.13
 %define release 0base
 
 Summary: Shoreline Firewall Lite is an iptables-based firewall for Linux systems.
@@ -98,6 +98,8 @@ fi
 %doc COPYING changelog.txt releasenotes.txt
 
 %changelog
+* Sun Jun 07 2009 Tom Eastep tom@shorewall.net
+- Updated to 4.3.13-0base
 * Fri Jun 05 2009 Tom Eastep tom@shorewall.net
 - Updated to 4.3.12-0base
 * Sun May 10 2009 Tom Eastep tom@shorewall.net

Shorewall-lite/uninstall.sh

@@ -26,7 +26,7 @@
 #       You may only use this script to uninstall the version
 #       shown below. Simply run this script to remove Shorewall Firewall
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall/Perl/Shorewall/Config.pm

@@ -325,7 +325,7 @@ sub initialize( $ ) {
 		    TC_SCRIPT => '',
 		    EXPORT => 0,
 		    UNTRACKED => 0,
-		    VERSION => "4.3.12",
+		    VERSION => "4.3.13",
 		    CAPVERSION => 40309 ,
 		  );
 

Shorewall/changelog.txt

@@ -1,3 +1,7 @@
+Changes in Shorewall 4.3.13
+
+None.
+
 Changes in Shorewall 4.3.12
 
 1) Eliminate 'large quantum' warnings.

Shorewall/install.sh

@@ -22,7 +22,7 @@
 #       Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall/known_problems.txt

@@ -1 +1 @@
-There are no known problems in Shorewall version 4.3.12
+There are no known problems in Shorewall version 4.3.13

Shorewall/releasenotes.txt

@@ -1,4 +1,4 @@
-Shorewall 4.3.12
+Shorewall 4.3.13
 
 Shorewall 4.3 is the development thread for Shorewall 4.4 which will be
 released late in 2009.
@@ -105,19 +105,10 @@ released late in 2009.
     using NULL_ROUTE_RFC1918=Yes instead. 
 
 ----------------------------------------------------------------------------
-          P R O B L E M S   C O R R E C T E D   I N   4 . 3 . 12
+          P R O B L E M S   C O R R E C T E D   I N   4 . 3 . 13
 ----------------------------------------------------------------------------
 
-1)  A 'large quantum' warning log message during restart has been
+None.
-    eliminated. The log message occurred when an interface with a large
-    OUT-BANDWIDTH was defined in /etc/shorewall/tcdevices.
-
-2)  The 'shorewall reset' command no longer generates this error:
-
-    	/sbin/shorewall: 885: report: not found
-
-3)  A mis-coded test after the 'findgw' script was executed caused the
-    value returned by that script to be ignored.
 
 ----------------------------------------------------------------------------
              K N O W N   P R O B L E M S   R E M A I N I N G
@@ -126,77 +117,10 @@ released late in 2009.
 None.
 
 ----------------------------------------------------------------------------
-                N E W   F E A T U R E S   I N   4 . 3 . 12
+                N E W   F E A T U R E S   I N   4 . 3 . 13
 ----------------------------------------------------------------------------
 
-1)  Support for the "Hierarchical Fair Service Curve" (HFSC) queuing
+None.
-    discipline has been added. HFSC is superior to the "Hierarchical
-    Token Bucket" queuing discipline where realtime traffic such as
-    VOIP is being used.
-
-    An excellent overview of HFSC on Linux may be found at
-    http://linux-ip.net/articles/hfsc.en/.
-
-    To use HFSC, several changes need to be made to your traffic
-    shaping configuration:
-
-    	    - To use HFSC on an interface rather than HTB, specify the
-              'hfsc' option in the OPTIONS column in the interfaces's
-              entry in /etc/shorewall/tcdevices.
-
-	    - Modify the RATE colum  for each 'leaf' class (class with no
-              parent class specified) defined for the interface.
-
-	      When using HFSC, the RATE column may specify 1, 2 or 3
-	      pieces of information separated by colons (":").
-
-	      1. The Guaranteed bandwidth (as always).
-	      2. The Maximum delay (DMAX) that the first queued packet
-	         in the class should experience. The delay is expressed
-	         in milliseconds and may be followed by 'ms' (e.g.,
-	      	 10ms. Note that there may be no white space between the
-	      	 number and 'ms'). 
-              3. The maximum transmission unit (UMAX) for this class of
-	         traffic. If not specified, the MTU of the interface is
-		 used. The length is specified in bytes and may be
-	         followed by 'b' (e.g., 800b. Note that there may be no
-	         white space between the number and 'b').
-
-              DMAX should be specified for each leaf class. The Shorewall
-              compiler will issue a warning if DMAX is omitted.
-
-	      Example:
-
-		 full/2:10ms:1500b
-
-                 Guaranteed bandwidth is 1/2 of the devices
-                 OUT-BANDWIDTH. Maximum delay is 10ms. Maximum packet
-                 size is 1500 bytes.
-
-2)  Support for ipset bindings has been removed. Jozsef Kadlecsik has
-    already removed such support from ipset itself.
-
-3)  Optional TOS and LENGTH fields have been added to the tcfilters
-    file.
-
-    The TOS field may contain any of the following:
-
-    	tos-minimize-delay
-	tos-maximuze-throughput
-	tos-maximize-reliability
-	tos-minimize-cost
-	tos-normal-service
-	Hex-number
-	Hex-number/Hex-number
-
-    The hex numbers must have exactly two digits.
-
-    The LENGTH value must be a numeric power of two between 32 and 8192
-    inclusive. Packets with a total length that is strictly less that
-    the specified value will match the rule.
-
-4)  Support for 'norfc1918' has been removed. See the Migration
-    Considerations above.
 
 ----------------------------------------------------------------------------
                  N E W   F E A T U R E S   IN   4 . 3
@@ -717,3 +641,73 @@ None.
     default class is guaranteed half of the download capacity and my
     work system (172.20.1.107) is guarandeed the other half.
 	
+
+20) Support for the "Hierarchical Fair Service Curve" (HFSC) queuing
+    discipline has been added. HFSC is superior to the "Hierarchical
+    Token Bucket" queuing discipline where realtime traffic such as
+    VOIP is being used.
+
+    An excellent overview of HFSC on Linux may be found at
+    http://linux-ip.net/articles/hfsc.en/.
+
+    To use HFSC, several changes need to be made to your traffic
+    shaping configuration:
+
+    	    - To use HFSC on an interface rather than HTB, specify the
+              'hfsc' option in the OPTIONS column in the interfaces's
+              entry in /etc/shorewall/tcdevices.
+
+	    - Modify the RATE colum  for each 'leaf' class (class with no
+              parent class specified) defined for the interface.
+
+	      When using HFSC, the RATE column may specify 1, 2 or 3
+	      pieces of information separated by colons (":").
+
+	      1. The Guaranteed bandwidth (as always).
+	      2. The Maximum delay (DMAX) that the first queued packet
+	         in the class should experience. The delay is expressed
+	         in milliseconds and may be followed by 'ms' (e.g.,
+	      	 10ms. Note that there may be no white space between the
+	      	 number and 'ms'). 
+              3. The maximum transmission unit (UMAX) for this class of
+	         traffic. If not specified, the MTU of the interface is
+		 used. The length is specified in bytes and may be
+	         followed by 'b' (e.g., 800b. Note that there may be no
+	         white space between the number and 'b').
+
+              DMAX should be specified for each leaf class. The Shorewall
+              compiler will issue a warning if DMAX is omitted.
+
+	      Example:
+
+		 full/2:10ms:1500b
+
+                 Guaranteed bandwidth is 1/2 of the devices
+                 OUT-BANDWIDTH. Maximum delay is 10ms. Maximum packet
+                 size is 1500 bytes.
+
+21) Support for ipset bindings has been removed. Jozsef Kadlecsik has
+    already removed such support from ipset itself.
+
+22) Optional TOS and LENGTH fields have been added to the tcfilters
+    file.
+
+    The TOS field may contain any of the following:
+
+    	tos-minimize-delay
+	tos-maximuze-throughput
+	tos-maximize-reliability
+	tos-minimize-cost
+	tos-normal-service
+	Hex-number
+	Hex-number/Hex-number
+
+    The hex numbers must have exactly two digits.
+
+    The LENGTH value must be a numeric power of two between 32 and 8192
+    inclusive. Packets with a total length that is strictly less that
+    the specified value will match the rule.
+
+23) Support for 'norfc1918' has been removed. See the Migration
+    Considerations above.
+

Shorewall/shorewall.spec

@@ -1,5 +1,5 @@
 %define name shorewall
-%define version 4.3.12
+%define version 4.3.13
 %define release 0base
 
 Summary: Shoreline Firewall is an iptables-based firewall for Linux systems.
@@ -104,6 +104,8 @@ fi
 %doc COPYING INSTALL changelog.txt releasenotes.txt Contrib/* Samples 
 
 %changelog
+* Sun Jun 07 2009 Tom Eastep tom@shorewall.net
+- Updated to 4.3.13-0base
 * Fri Jun 05 2009 Tom Eastep tom@shorewall.net
 - Updated to 4.3.12-0base
 * Fri Jun 05 2009 Tom Eastep tom@shorewall.net

Shorewall/uninstall.sh

@@ -26,7 +26,7 @@
 #       You may only use this script to uninstall the version
 #       shown below. Simply run this script to remove Shorewall Firewall
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall6-lite/fallback.sh

@@ -28,7 +28,7 @@
 #       shown below. Simply run this script to revert to your prior version of
 #       Shoreline Firewall.
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall6-lite/install.sh

@@ -22,7 +22,7 @@
 #       Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall6-lite/shorewall6-lite.spec

@@ -1,5 +1,5 @@
 %define name shorewall6-lite
-%define version 4.3.12
+%define version 4.3.13
 %define release 0base
 
 Summary: Shoreline Firewall 6 Lite is an ip6tables-based firewall for Linux systems.
@@ -89,6 +89,8 @@ fi
 %doc COPYING changelog.txt releasenotes.txt
 
 %changelog
+* Sun Jun 07 2009 Tom Eastep tom@shorewall.net
+- Updated to 4.3.13-0base
 * Fri Jun 05 2009 Tom Eastep tom@shorewall.net
 - Updated to 4.3.12-0base
 * Sun May 10 2009 Tom Eastep tom@shorewall.net

Shorewall6-lite/uninstall.sh

@@ -26,7 +26,7 @@
 #       You may only use this script to uninstall the version
 #       shown below. Simply run this script to remove Shorewall Firewall
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall6/fallback.sh

@@ -28,7 +28,7 @@
 #       shown below. Simply run this script to revert to your prior version of
 #       Shoreline Firewall.
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall6/install.sh

@@ -22,7 +22,7 @@
 #       Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 #
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {

Shorewall6/shorewall6.spec

@@ -1,5 +1,5 @@
 %define name shorewall6
-%define version 4.3.12
+%define version 4.3.13
 %define release 0base
 
 Summary: Shoreline Firewall 6 is an ip6tables-based firewall for Linux systems.
@@ -93,6 +93,8 @@ fi
 %doc COPYING INSTALL changelog.txt releasenotes.txt tunnel ipsecvpn ipv6 Samples6
 
 %changelog
+* Sun Jun 07 2009 Tom Eastep tom@shorewall.net
+- Updated to 4.3.13-0base
 * Fri Jun 05 2009 Tom Eastep tom@shorewall.net
 - Updated to 4.3.12-0base
 * Sun May 10 2009 Tom Eastep tom@shorewall.net

Shorewall6/uninstall.sh

@@ -26,7 +26,7 @@
 #       You may only use this script to uninstall the version
 #       shown below. Simply run this script to remove Shorewall Firewall
 
-VERSION=4.3.12
+VERSION=4.3.13
 
 usage() # $1 = exit status
 {