forked from extern/shorewall_code
Prepare website for 4.4.0 Beta 1
This commit is contained in:
parent
e2ae6453ac
commit
0d5a64866a
@ -5,7 +5,7 @@
|
||||
<!--/$Id$-->
|
||||
|
||||
<articleinfo>
|
||||
<title>Shorewall 4.3 Documentation</title>
|
||||
<title>Shorewall 4.4 Documentation</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
|
@ -21,7 +21,7 @@ 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>2009-02-27<br>
|
||||
<p>2009-06-14<br>
|
||||
</p>
|
||||
<hr style="width: 100%; height: 2px;"> <strong></strong>
|
||||
<br>
|
||||
@ -29,7 +29,8 @@ License</a></span>”.<br>
|
||||
cellspacing="0">
|
||||
<tbody>
|
||||
<tr style="font-weight: bold;">
|
||||
<td style="vertical-align: top; text-align: center;">Shorewall 4.3<br>
|
||||
<td style="vertical-align: top; text-align: center;">Shorewall
|
||||
4.4 Beta<br>
|
||||
(Development)<br>
|
||||
</td>
|
||||
<th style="vertical-align: top; text-align: center;">Shorewall
|
||||
|
@ -23,9 +23,12 @@ license is included in the section entitled <span
|
||||
href="GnuCopyright.htm" target="_self">GNU Free Documentation
|
||||
License</a></span>".
|
||||
</p>
|
||||
<p>April 16, 2009<br>
|
||||
<p>June 14, 2009<br>
|
||||
</p>
|
||||
<hr style="width: 100%; height: 2px;">
|
||||
<p><strong>2009-06-13 Shorewall 4.4.0 Beta 1</strong></p>
|
||||
<pre>Read the details at <a
|
||||
href="http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta1/releasenotes.txt">http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta1/releasenotes.txt</a><br><strong></strong></pre>
|
||||
<p><strong>2009-05-14 Shorewall 4.2.9</strong></p>
|
||||
<p><strong></strong></p>
|
||||
<pre>Problems corrected in Shorewall 4.2.9<br><br>1) The Shorweall-perl 4.2.8 compiler did not rename the output script<br> file with the result that:<br><br> a) Shorewall would not start for the first time after<br> installation.<br> b) Configuration changes were apparently ignored.<br><br>2) Placing a broadcast address in the BROADCAST column of<br> /etc/shorewall/interfaces caused Shorewall-perl to generate an<br> error:<br><br> ERROR: Invalid BROADCAST address : /etc/shorewall/interfaces\<br> (line 225)<br><br>3) When Shorewall could not determine the MAC address of of a gateway<br> router where multiple providers are configured through the same<br> interface, invalid iptables-restore input was generated. This<br> resulted in an error message similar to the following:<br><br> iptables-restore v1.3.5: Bad mac address `-j'<br><br>4) Shorewall-perl was not processing the tcrules file when<br> TC_ENABLED=No.<br><br>5) When 'all' appeared in the SOURCE column of a DNAT rule, no rule to<br> redirect output from the firewall itself was generated.<br> <br>6) The 'shorewall iprange' command failed to produce a minimal list of<br> networks.<br><br>New Features in Shorewall 4.2.9<br><br>1) Shorewall6 has now been validated on Ubuntu Hardy running kernel<br> 2.6.24. Shorewall6 is now supported on that kernel version.<br></pre>
|
||||
|
@ -38,7 +38,7 @@
|
||||
</tbody>
|
||||
</table>
|
||||
<p> </p>
|
||||
<hr><span style="font-weight: bold;">2009-06-01</span>
|
||||
<hr><span style="font-weight: bold;">2009-06-14</span>
|
||||
<h2><a name="Which"></a>Package Information</h2>
|
||||
<p><b>Before trying to install, we strongly urge you to read and print
|
||||
a
|
||||
@ -58,16 +58,15 @@ Choose this release if you value stability and good documentation. </li>
|
||||
<li>The prior STABLE release series is 4.0. We release updates to
|
||||
this series to correct problems but usually don't make enhancements to
|
||||
it. </li>
|
||||
<li>The DEVELOPMENT release series is 4.3
|
||||
<li>The DEVELOPMENT release series is 4.4 Beta
|
||||
(found in the
|
||||
'development' directory). Choose this release if you are <strong>very
|
||||
experienced</strong> <strong>user</strong> and you are willing to help
|
||||
test the code and report bugs. <span style="font-weight: bold;"></span>
|
||||
<strong></strong></li>
|
||||
'development' directory). Choose this release if you want to help
|
||||
shake out the bugs in the next stable release. <span
|
||||
style="font-weight: bold;"></span> <strong></strong></li>
|
||||
</ul>
|
||||
For additional information, see this article about the <a
|
||||
href="ReleaseModel.html">Shorewall Release Model</a>.
|
||||
<p>Beginning with Shorewall version 4.0.0 RC1, there are four related
|
||||
<p>In Shorewall version 4.0.*, there are four related
|
||||
packages:</p>
|
||||
<ul>
|
||||
<li><span style="font-weight: bold;">Shorewall-shell</span> -- the
|
||||
@ -83,12 +82,12 @@ installations.</li>
|
||||
<li><span style="font-weight: bold;">Shorewall-common</span> -- A
|
||||
base package required by both
|
||||
Shorewall-shell and Shorewall-perl.</li>
|
||||
<li><span style="font-weight: bold;">Shorewall Lite</span> -- a
|
||||
<li><span style="font-weight: bold;">Shorewall-lite</span> -- a
|
||||
light-weight Shorewall version that will run
|
||||
compiled firewall scripts generated on a system with one of the
|
||||
compiler packages installed.</li>
|
||||
</ul>
|
||||
Beginning with Shorewall version 4.2.4, there are two additional
|
||||
In Shorewall version 4.2.*, there are two additional
|
||||
packages that provide IPv6 support:<br>
|
||||
<ul>
|
||||
<li><span style="font-weight: bold;">Shorewall6</span> -- Provides
|
||||
@ -102,18 +101,57 @@ run compiled firewall scripts generated on a system with Shorewall6
|
||||
installed.<br>
|
||||
</li>
|
||||
</ul>
|
||||
In Shorewall version 4.4.*, the Shorewall-common, Shorewall-shell and
|
||||
Shorewall-perl packages are discontinued and replaced with a single <span
|
||||
style="font-weight: bold;">Shorewall</span> package which combined the
|
||||
functions of Shorewall-common and Shorewall-perl. The shell-based
|
||||
compiler is retired. So with Shorewall 4.4 onward, there are four
|
||||
packages:<br>
|
||||
<ul>
|
||||
<li><span style="font-weight: bold;">Shorewall </span>-- Includes
|
||||
everything needed to create an IPv4 firewall.</li>
|
||||
<li><span style="font-weight: bold;">Shorewall6 </span>-- Requires
|
||||
the Shorewall package and adds the capability to create an IPv6
|
||||
firewall.</li>
|
||||
<li><span style="font-weight: bold;">Shorewall-lite</span> -- a
|
||||
light-weight Shorewall version that will run
|
||||
compiled firewall scripts generated on a system with one of the
|
||||
compiler packages installed.</li>
|
||||
<li><span style="font-weight: bold;">Shorewall6-lite</span> -- a
|
||||
light-weight Shorewall6 version that will
|
||||
run compiled firewall scripts generated on a system with Shorewall6
|
||||
installed.</li>
|
||||
</ul>
|
||||
To summarize:
|
||||
<ul>
|
||||
<li>On at least one system in your network, you must install one or
|
||||
<li>If you are installing Shorewall 4.2 or earlier:<br>
|
||||
</li>
|
||||
<ul>
|
||||
<li>On at least one system in your network, you must install one or
|
||||
both of the compilers (Shorewall-shell and/or Shorewall-perl), the
|
||||
Shorewall-common package and possibly the Shorewall6 package..</li>
|
||||
<li>If you only have a single firewall, then that system should be
|
||||
Shorewall-common package and possibly the Shorewall6 package.</li>
|
||||
<li>If you only have a single firewall, then that system should be
|
||||
your firewall system.</li>
|
||||
<li>If you have more than one firewall, you may wish to install one
|
||||
<li>If you have more than one firewall, you may wish to install one
|
||||
or both of the compilers on a single <em>administrative</em> system
|
||||
and install Shorewall-lite and/or Shorewall6-lite on the firewalls.
|
||||
Doing so will allow for
|
||||
centralized administration and configuration of the firewalls.</li>
|
||||
</ul>
|
||||
<li>If you are installing Shorewall 4.4 or later:</li>
|
||||
<ul>
|
||||
<li>On at least one system in your network, you must install the
|
||||
Shorewall package. If you need IPv6 firewalls then you must also
|
||||
install the Shoreall6 package.</li>
|
||||
<li>If you have a single firewall, then that system should be your
|
||||
firewall system.</li>
|
||||
<li>If you have more than one firewall, you may wish to install
|
||||
Shorewall on a single <span style="font-style: italic;">administrative</span>
|
||||
system and install Shorewall-lite and/or Shorewall6-lite on the
|
||||
firewalls. Doing so will allow for centralized administration and
|
||||
configuration of the firewalls.<br>
|
||||
</li>
|
||||
</ul>
|
||||
</ul>
|
||||
<p>When RPM is used to install Shorewall, the compiler (shorewall-shell
|
||||
and/or shorewall-perl) and shorewall-common must be installed in a
|
||||
|
@ -47,7 +47,7 @@
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<hr style="width: 100%; height: 2px;"><span style="font-weight: bold;">2009-05-14</span><br>
|
||||
<hr style="width: 100%; height: 2px;"><span style="font-weight: bold;">2009-06-13</span><br>
|
||||
<h3><a name="Releases"></a>Current Shorewall Releases</h3>
|
||||
<table style="text-align: left; width: 100%;" border="0" cellpadding="2"
|
||||
cellspacing="0">
|
||||
@ -90,14 +90,15 @@ Problems</a><br>
|
||||
Release</span><br>
|
||||
</div>
|
||||
</td>
|
||||
<td style="vertical-align: top;"><span style="font-weight: bold;">4.3.10</span><br>
|
||||
<td style="vertical-align: top;"><span style="font-weight: bold;">4.4.0
|
||||
Beta 1</span><br>
|
||||
</td>
|
||||
<td style="vertical-align: top;"><a
|
||||
href="http://www1.shorewall.net/pub/shorewall/development/4.3/shorewall-4.3.10/releasenotes.txt">Release
|
||||
href="http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta1/releasenotes.txt">Release
|
||||
Notes<br>
|
||||
</a> </td>
|
||||
<td style="vertical-align: top;"><a
|
||||
href="http://www1.shorewall.net/pub/shorewall/development/4.3/shorewall-4.3.10/known_problems.txt">Known
|
||||
href="http://www1.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta1/known_problems.txt">Known
|
||||
Problems</a> </td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
Loading…
Reference in New Issue
Block a user