Update website for 4.2.9

This commit is contained in:
Tom Eastep 2009-05-14 09:48:58 -07:00
parent 88989ae98e
commit 2524d1c949
2 changed files with 9 additions and 5 deletions

View File

@ -26,7 +26,11 @@ License</a></span>".
<p>April 16, 2009<br>
</p>
<hr style="width: 100%; height: 2px;">
<p><strong>2000-04-16 Shorewall 4.2.8</strong></p>
<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>
<p><strong>2009-04-16 Shorewall 4.2.8<br>
</strong></p>
<p><strong></strong></p>
<pre>Problems Corrected in Shorewall 4.2.8<br><br>1) The 'start -f' command would previously skip the compilation step<br> unconditionally when the 'make' utility was not installed. Now, the<br> compilation step is run unconditionally in this case.<br><br>2) When ADD_IP_ALIASES=Yes in shorewall.conf, entries in<br> /etc/shorewall/nat produce this failure at compile time when<br> using Shorewall-perl:<br><br> ERROR: Internal Error in emit : /etc/shorewall/nat (line 12)<br><br>3) When LOG_MARTIANS=Yes with Shorewall-perl, setting logmartians=0 in<br> an entry in /etc/shorewall/interface failed to suppress martian<br> logging on the interface.<br><br>4) Shorewall-perl now generates rules with inversion that are<br> compatible with iptables 1.4.3.<br><br>5) When a network address was specified in the SOURCE or DEST column of<br> /etc/shorewall/tcfilters, Shorewall-perl was generating an incorrect<br> netmask.<br><br>New Features in 4.2.8<br><br>1) The /usr/share/shorewall/modules and /usr/share/shorewall6/modules<br> files have been updated for iptables 1.4.3/kernel 2.6.29.<br></pre>
<p><strong>2009-03-19 Shorewall 4.2.7</strong></p>

View File

@ -47,7 +47,7 @@
</tr>
</tbody>
</table>
<hr style="width: 100%; height: 2px;"><span style="font-weight: bold;">2009-05-13</span><br>
<hr style="width: 100%; height: 2px;"><span style="font-weight: bold;">2009-05-14</span><br>
<h3><a name="Releases"></a>Current Shorewall Releases</h3>
<table style="text-align: left; width: 100%;" border="0" cellpadding="2"
cellspacing="0">
@ -58,13 +58,13 @@
Stable Release</span><br>
</div>
</td>
<td style="vertical-align: top;"><span style="font-weight: bold;">4.2.8</span>
<td style="vertical-align: top;"><span style="font-weight: bold;">4.2.9</span>
(includes <a href="IPv6Support.html">IPv6 support.</a>)</td>
<td style="vertical-align: top;"><a
href="http://www1.shorewall.net/pub/shorewall/4.2/shorewall-4.2.8/releasenotes.txt">Release
href="http://www1.shorewall.net/pub/shorewall/4.2/shorewall-4.2.9/releasenotes.txt">Release
notes</a> </td>
<td style="vertical-align: top;"><a
href="http://www1.shorewall.net/pub/shorewall/4.2/shorewall-4.2.8/known_problems.txt">Known
href="http://www1.shorewall.net/pub/shorewall/4.2/shorewall-4.2.9/known_problems.txt">Known
Problems</a></td>
</tr>
<tr>