From f5a4a8f73236ec57a6dab1c440f9e5302fbe0bcf Mon Sep 17 00:00:00 2001 From: teastep Date: Mon, 24 Jul 2006 16:40:57 +0000 Subject: [PATCH] Update web site and docs to reflect end of support life for 2.4 git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@4273 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-lite/changelog.txt | 1 + docs/ReleaseModel.xml | 4 +++- docs/support.xml | 8 +++---- web/Documentation.html | 9 +++---- web/News.htm | 4 +++- web/support.html | 46 +++++++++++++----------------------- 6 files changed, 31 insertions(+), 41 deletions(-) diff --git a/Shorewall-lite/changelog.txt b/Shorewall-lite/changelog.txt index 16fe7d89a..d8f01b5de 100644 --- a/Shorewall-lite/changelog.txt +++ b/Shorewall-lite/changelog.txt @@ -6,3 +6,4 @@ Changes in 3.3.0 3) Fixed modules/xmodules snafu. +4) Fix comments in shorewall-lite. diff --git a/docs/ReleaseModel.xml b/docs/ReleaseModel.xml index b2060245f..4c2540738 100644 --- a/docs/ReleaseModel.xml +++ b/docs/ReleaseModel.xml @@ -22,6 +22,8 @@ 2005 + 2006 + Thomas M. Eastep @@ -123,7 +125,7 @@ - The currently-supported major releases are 2.4.x and 3.x. + The currently-supported major releases are 3.0.x and 3.1.x.
diff --git a/docs/support.xml b/docs/support.xml index 725ddce8b..6edbdfc8a 100644 --- a/docs/support.xml +++ b/docs/support.xml @@ -57,12 +57,12 @@ The two currently-supported Shorewall major releases are 3.0 and 2.4. + url="ReleaseModel.html">major releases are 3.0 and 3.2. - Shorewall versions earlier than 2.4.0 are no longer supported; - we will only answer your question if it deals with upgrading from - these old releases to a current one. + Shorewall versions earlier than 3.0.0 are no longer supported; + we will try to help but I will personally not spend time reading + earlier code to try to help you solve a problem. diff --git a/web/Documentation.html b/web/Documentation.html index e587a255c..a08b4c9b0 100644 --- a/web/Documentation.html +++ b/web/Documentation.html @@ -20,7 +20,7 @@ Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.

-

2006-07-20
+

2006-07-24


@@ -45,11 +45,8 @@ Example:
-
-
In the above case, you want to select the 'Shorewall 3.x' link -below.
-
-Please note that versions of Shorewall earlier than 2.4.0 are no longer +
+Please note that versions of Shorewall earlier than 3.0.0 are no longer supported.

Alphabetical indexes of all Articles

diff --git a/web/News.htm b/web/News.htm index c1e845060..fb00d55a3 100644 --- a/web/News.htm +++ b/web/News.htm @@ -28,7 +28,9 @@ Documentation License”.
2006-03-21 Shorewall 3.2.1
Problems Corrected in Shorewall 3.2.1:

1) The output formatting of the 'hits' command under BusyBox 1.2.0 has
been corrected.

2) Shorewall no longer requires extended MARK support to use the 'track'
provider option when HIGH_ROUTE_MARKS=No.

3) The output of the 'hits' command was previously scrambled if
/etc/services contained spaces as column delimiters rather than
tabs.

4) The /usr/share/shorewall/xmodules file was previously just a copy
of /usr/share/shorewall/modules.

5) The version number in the comments at the top of shorewall.conf has
been corrected.

6) The script generated when the -e option is given to the 'compile'
command is setting CONFIG_PATH to the value given in the remote
firewall's shorewall.conf processed at compile time. This is
generally incorrect and results in the inability to load any kernel
modules on the firewall during 'shorewall-lite [re]start'.

Problems Corrected in Shorewall Lite 3.2.1:

1) The output formatting of the 'hits' command under BusyBox 1.2.0 has
been corrected.

2) The output of the 'hits' command was previously scrambled if
/etc/services contained spaces as column delimiters rather than
tabs.

3) The /usr/share/shorewall-lite/xmodules file was previously just a
copy of /usr/share/shorewall-lite/modules.

4) The version number in the comments at the top of shorewall.conf has
been corrected.
-2006-07-19 Shorewall bridge/firewall + +
2006-07-19 +Shorewall bridge/firewall support change upcoming
I regret to announce that Shorewall bridge/firewall support in its
current form (BRIDGING=Yes in shorewall.conf) is going away. I will
retain the code in Shorewall for the foreseeable future but users
migrating to new kernels coming out next year will find that their
current bridge configurations no longer work. Shorewall bridge/firewall
users upgrading to more immediate new kernel releases (possibly as early
as 2.6.18) will find Netfilter warning messages appearing in their
kernel log when Shorewall [re]starts.

The reason that this support is going away is that the underlying
Netfilter feature that BRIDGING=Yes depends on (physdev match) is being
reduced in scope to the point that it will no longer be possible to use
that feature for Shorewall zone definition. There is a significant list
of pending Netfilter bug reports than cannot be resolved so long as
'physdev match' works the way that it does today.

While 'physdev match' was a great idea in terms of the function that it
provides, it appears impossible to implement that function without
breaking other parts of the greater Linux IP stack; in short, 'physdev
match' in its current form should never have been released in the first
place.

So -- what can current Shorewall bridge/firewall users do?
-----------------------------------------------------------------------
a) Configure Shorewall as if you have a simple bridge
(GNU Free Documentation License”.

-

2006-06-15
+

2006-07-24


@@ -45,50 +45,40 @@ Example:
-
-
In the above case, you want to select the 'Shorewall 3.x' links -below.
-
-Please note that versions of Shorewall earlier than 2.4.0 are no longer +
+Please note that versions of Shorewall earlier than 3.0.0 are no longer supported.

Self-Help Resources