forked from extern/shorewall_code
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
This commit is contained in:
parent
719f14d064
commit
f5a4a8f732
@ -6,3 +6,4 @@ Changes in 3.3.0
|
||||
|
||||
3) Fixed modules/xmodules snafu.
|
||||
|
||||
4) Fix comments in shorewall-lite.
|
||||
|
@ -22,6 +22,8 @@
|
||||
|
||||
<year>2005</year>
|
||||
|
||||
<year>2006</year>
|
||||
|
||||
<holder>Thomas M. Eastep</holder>
|
||||
</copyright>
|
||||
|
||||
@ -123,7 +125,7 @@
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>The currently-supported major releases are 2.4.x and 3.x.</para>
|
||||
<para>The currently-supported major releases are 3.0.x and 3.1.x.</para>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
|
@ -57,12 +57,12 @@
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>The two currently-supported Shorewall <ulink
|
||||
url="ReleaseModel.html">major releases</ulink> are 3.0 and 2.4.</para>
|
||||
url="ReleaseModel.html">major releases</ulink> are 3.0 and 3.2.</para>
|
||||
|
||||
<note>
|
||||
<para>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.</para>
|
||||
<para>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.</para>
|
||||
</note>
|
||||
</listitem>
|
||||
|
||||
|
@ -20,7 +20,7 @@ Texts. A copy of the license is included in the section entitled “<span
|
||||
class="quote"><a href="GnuCopyright.htm" target="_self">GNU Free
|
||||
Documentation License</a></span>”.<br>
|
||||
</p>
|
||||
<p>2006-07-20<br>
|
||||
<p>2006-07-24<br>
|
||||
</p>
|
||||
<hr style="width: 100%; height: 2px;"> <span style="font-weight: bold;"></span><span
|
||||
style="font-weight: bold;"><span style="text-decoration: underline;"></span></span>
|
||||
@ -45,11 +45,8 @@ Example:<br>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<span style="font-weight: bold;"><br>
|
||||
</span>In the above case, you want to select the 'Shorewall 3.x' link
|
||||
below.<br>
|
||||
<br>
|
||||
Please note that versions of Shorewall earlier than 2.4.0 are no longer
|
||||
<span style="font-weight: bold;"></span><br>
|
||||
Please note that versions of Shorewall earlier than 3.0.0 are no longer
|
||||
supported.<br>
|
||||
<h2>Alphabetical indexes of all Articles<br>
|
||||
</h2>
|
||||
|
@ -28,7 +28,9 @@ Documentation License</a></span>”.<br>
|
||||
<span style="font-weight: bold;">2006-03-21 Shorewall 3.2.1<br>
|
||||
</span><span style="font-weight: bold;"></span>
|
||||
<pre>Problems Corrected in Shorewall 3.2.1:<br><br>1) The output formatting of the 'hits' command under BusyBox 1.2.0 has<br> been corrected.<br><br>2) Shorewall no longer requires extended MARK support to use the 'track'<br> provider option when HIGH_ROUTE_MARKS=No.<br><br>3) The output of the 'hits' command was previously scrambled if<br> /etc/services contained spaces as column delimiters rather than<br> tabs.<br><br>4) The /usr/share/shorewall/xmodules file was previously just a copy<br> of /usr/share/shorewall/modules.<br><br>5) The version number in the comments at the top of shorewall.conf has<br> been corrected.<br><br>6) The script generated when the -e option is given to the 'compile'<br> command is setting CONFIG_PATH to the value given in the remote<br> firewall's shorewall.conf processed at compile time. This is<br> generally incorrect and results in the inability to load any kernel<br> modules on the firewall during 'shorewall-lite [re]start'.<br><br>Problems Corrected in Shorewall Lite 3.2.1:<br><br>1) The output formatting of the 'hits' command under BusyBox 1.2.0 has<br> been corrected.<br><br>2) The output of the 'hits' command was previously scrambled if<br> /etc/services contained spaces as column delimiters rather than<br> tabs.<br><br>3) The /usr/share/shorewall-lite/xmodules file was previously just a<br> copy of /usr/share/shorewall-lite/modules.<br><br>4) The version number in the comments at the top of shorewall.conf has<br> been corrected.<br></pre>
|
||||
<span style="font-weight: bold;">2006-07-19 Shorewall bridge/firewall
|
||||
<span style="font-weight: bold;"></span>
|
||||
<hr style="width: 100%; height: 2px;"><span style="font-weight: bold;">2006-07-19
|
||||
Shorewall bridge/firewall
|
||||
support change upcoming<br>
|
||||
</span><span style="font-weight: bold;"></span>
|
||||
<pre><tt>I regret to announce that Shorewall bridge/firewall support in its</tt><br><tt>current form (BRIDGING=Yes in shorewall.conf) is going away. I will</tt><br><tt>retain the code in Shorewall for the foreseeable future but users</tt><br><tt>migrating to new kernels coming out next year will find that their</tt><br><tt>current bridge configurations no longer work. Shorewall bridge/firewall</tt><br><tt>users upgrading to more immediate new kernel releases (possibly as early</tt><br><tt>as 2.6.18) will find Netfilter warning messages appearing in their</tt><br><tt>kernel log when Shorewall [re]starts.</tt><br><br><tt>The reason that this support is going away is that the underlying</tt><br><tt>Netfilter feature that BRIDGING=Yes depends on (physdev match) is being</tt><br><tt>reduced in scope to the point that it will no longer be possible to use</tt><br><tt>that feature for Shorewall zone definition. There is a significant list</tt><br><tt>of pending Netfilter bug reports than cannot be resolved so long as</tt><br><tt>'physdev match' works the way that it does today.</tt><br><br><tt>While 'physdev match' was a great idea in terms of the function that it</tt><br><tt>provides, it appears impossible to implement that function without</tt><br><tt>breaking other parts of the greater Linux IP stack; in short, 'physdev</tt><br><tt>match' in its current form should never have been released in the first</tt><br><tt>place.</tt><br><br><tt>So -- what can current Shorewall bridge/firewall users do? </tt><br><tt>-----------------------------------------------------------------------</tt><br><tt>a) Configure Shorewall as if you have a simple bridge</tt><br><tt>(<a
|
||||
|
@ -20,7 +20,7 @@ Texts. A copy of the license is included in the section entitled “<span
|
||||
class="quote"><a href="GnuCopyright.htm" target="_self">GNU Free
|
||||
Documentation License</a></span>”.<br>
|
||||
</p>
|
||||
<p>2006-06-15<br>
|
||||
<p>2006-07-24<br>
|
||||
</p>
|
||||
<hr style="width: 100%; height: 2px;"> <span style="font-weight: bold;"></span><span
|
||||
style="font-weight: bold;"><span style="text-decoration: underline;"></span></span>
|
||||
@ -45,50 +45,40 @@ Example:<br>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<span style="font-weight: bold;"><br>
|
||||
</span>In the above case, you want to select the 'Shorewall 3.x' links
|
||||
below.<br>
|
||||
<br>
|
||||
Please note that versions of Shorewall earlier than 2.4.0 are no longer
|
||||
<span style="font-weight: bold;"></span><br>
|
||||
Please note that versions of Shorewall earlier than 3.0.0 are no longer
|
||||
supported.<br>
|
||||
<h2>Self-Help Resources</h2>
|
||||
<ul>
|
||||
<li>QuickStart Guides
|
||||
(HOWTOs for setting up Shorewall in popular configurations)<br>
|
||||
<div style="margin-left: 40px;"> <a
|
||||
href="2.0/shorewall_quickstart_guide.htm">Shorewall 2.x</a><br>
|
||||
<a href="shorewall_quickstart_guide.htm">Shorewall3.x</a></div>
|
||||
href="shorewall_quickstart_guide.htm">Shorewall3.x</a></div>
|
||||
</li>
|
||||
<li>Installation/Upgrade Instructions<br>
|
||||
<div style="margin-left: 40px;"><a href="2.0/Install.htm">Shorewall
|
||||
2.x</a><br>
|
||||
<a href="Install.htm">Shorewall 3.x</a><br>
|
||||
<div style="margin-left: 40px;"> <a href="Install.htm">Shorewall
|
||||
3.x</a><br>
|
||||
</div>
|
||||
</li>
|
||||
<li>Shorewall Features (What it
|
||||
can do)<br>
|
||||
<div style="margin-left: 40px;"><a href="2.0/shorewall_features.htm">Shorewall
|
||||
2.x</a><br>
|
||||
<a href="shorewall_features.htm">Shorewall 3.x</a><br>
|
||||
<div style="margin-left: 40px;"> <a href="shorewall_features.htm">Shorewall
|
||||
3.x</a><br>
|
||||
</div>
|
||||
</li>
|
||||
<li>Limitations (Some things that
|
||||
it cannot do)<br>
|
||||
<div style="margin-left: 40px;"><a href="2.0/Shorewall_Doesnt.html">Shorewall
|
||||
2.x</a><br>
|
||||
<a href="Shorewall_Doesnt.html">Shorewall 3.x</a><br>
|
||||
<div style="margin-left: 40px;"> <a href="Shorewall_Doesnt.html">Shorewall
|
||||
3.x</a><br>
|
||||
</div>
|
||||
</li>
|
||||
<li>FAQs<br>
|
||||
<div style="margin-left: 40px;"><a href="2.0/FAQ.htm">Shorewall 2.x</a>
|
||||
<br>
|
||||
<a href="FAQ.htm">Shorewall 3.x</a><br>
|
||||
<li>FAQs<a href="2.0/FAQ.htm"></a><br>
|
||||
<div style="margin-left: 40px;"> <a href="FAQ.htm">Shorewall 3.x</a><br>
|
||||
</div>
|
||||
</li>
|
||||
<li>Troubleshooting Guide<br>
|
||||
<div style="margin-left: 40px;"><a href="2.0/troubleshoot.htm">Shorewall
|
||||
2.x</a> <br>
|
||||
<a href="troubleshoot.htm">Shorewall 3.x</a><br>
|
||||
<li>Troubleshooting Guide<a href="2.0/troubleshoot.htm"></a><br>
|
||||
<div style="margin-left: 40px;"> <a href="troubleshoot.htm">Shorewall
|
||||
3.x</a><br>
|
||||
</div>
|
||||
</li>
|
||||
<li><a href="upgrade_issues.htm">Upgrade Issues</a> (when you
|
||||
@ -114,9 +104,7 @@ in a newer version.<br>
|
||||
<h2>Getting Help</h2>
|
||||
<ul>
|
||||
<li>Reporting a problem or asking for help<br>
|
||||
<div style="margin-left: 40px;"><a href="2.0/support.htm">Shorewall
|
||||
2.x</a><br>
|
||||
<a href="support.htm">Shorewall
|
||||
<div style="margin-left: 40px;"> <a href="support.htm">Shorewall
|
||||
3.x</a><br>
|
||||
</div>
|
||||
</li>
|
||||
|
Loading…
Reference in New Issue
Block a user