Shorewall Website updates

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1524 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-08-07 03:33:54 +00:00
parent ceaf86f709
commit 2b93d39f1c
5 changed files with 382 additions and 64 deletions

View File

@ -10,6 +10,8 @@
link="#0000ee" alink="#0000ee" vlink="#551a8b">
<a href="index.htm" target="_top" style="font-weight: bold;"><font
color="#ffffff">Home</font></a><font color="#ffffff"><br>
<a href="Introduction.html" style="color: rgb(255, 255, 255);"><span
style="font-weight: bold;">Introduction</span></a><br>
<a href="download.htm" style="font-weight: bold;"><font color="#ffffff">Download</font></a><font
color="#ffffff"><br>
<a href="Install.htm"><span style="font-weight: bold;"><font
@ -93,7 +95,9 @@ M. Eastep.</font></font></a><font size="2"><br>
color="#ffffff"><font color="#ffffff"><font color="#ffffff"><font
color="#ffffff"><font color="#ffffff"><font color="#ffffff"><font
color="#ffffff"><font color="#ffffff"><font color="#ffffff"><font
color="#ffffff"><font size="2"><br>
color="#ffffff"><font size="2">Please report errors&nbsp; on this site
to <a href="mailto:webmaster@shorewall.net"
style="color: rgb(255, 255, 255);">the Webmaster.</a><br>
<a href="copyright.htm"> </a> </font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></p>
</body>
</html>

View File

@ -10,60 +10,83 @@
<base target="main">
<meta name="Microsoft Theme" content="none">
</head>
<body>
<table border="0" cellpadding="0" cellspacing="0"
style="border-collapse: collapse;" width="100%" id="AutoNumber1"
bgcolor="#3366ff" height="90">
<tbody>
<tr>
<td width="100%" bgcolor="#ffffff">
<ul>
<li style="font-weight: bold;"><a href="index.htm" target="_top">Home</a></li>
<li style="font-weight: bold;"><a href="download.htm">Download</a></li>
<li><a href="Install.htm"><span style="font-weight: bold;">Installation</span></a>
</li>
<li><b><a href="Documentation_Index.html">Documentation</a></b></li>
<li><a href="FAQ.htm"><span style="font-weight: bold;">FAQ</span>s</a>&nbsp;
(<a href="http://wiki.rettc.com/wiki.phtml?title=Wiki_Shorewall_FAQ"
target="_top">Wiki</a>)</li>
<li><a href="troubleshoot.htm"><span style="font-weight: bold;">Troubleshooting</span></a></li>
<li><a href="support.htm"><span style="font-weight: bold;">Support</span></a></li>
</ul>
<ul>
<li> <a href="shorewall_features.htm">Features</a></li>
<li><a href="Shorewall_Doesnt.html">What it
Cannot Do</a> </li>
<li> <a href="shorewall_prerequisites.htm">Requirements</a></li>
<li><a href="http://lists.shorewall.net">Mailing
Lists</a><a href="http://lists.shorewall.net"> </a> </li>
<li><a href="upgrade_issues.htm">Upgrade
Issues</a></li>
<li><a href="errata.htm">Errata</a></li>
<li><a href="shorewall_mirrors.htm">Mirrors</a> </li>
<li> <a href="News.htm">News Archive</a></li>
<li> <a
href="http://cvs.shorewall.net/Shorewall_CVS_Access.html">CVS
Repository</a></li>
<li> <a href="quotes.htm">Quotes from Users</a></li>
<li><a href="useful_links.html">Useful Links</a></li>
<li> <a href="shoreline.htm">About the Author</a></li>
<li> <a href="shorewall_index.htm#Donations">Donations</a></li>
</ul>
<ul>
</ul>
</td>
</tr>
</tbody>
</table>
<p><a href="copyright.htm"><font size="2">Copyright</font> © <font
size="2">2001-2004 Thomas M. Eastep.</font></a><br>
<body style="background-color: rgb(51, 102, 255); color: rgb(0, 0, 0);"
link="#0000ee" alink="#0000ee" vlink="#551a8b">
<a href="index.htm" target="_top" style="color: rgb(255, 255, 255);">Home</a><br
style="color: rgb(255, 255, 255);">
<a href="Introduction.html" style="color: rgb(255, 255, 255);">Introduction</a><br
style="color: rgb(255, 255, 255);">
<a href="download.htm" style="color: rgb(255, 255, 255);">Download</a><br
style="color: rgb(255, 255, 255);">
<a href="Install.htm" style="color: rgb(255, 255, 255);"><span
style="font-weight: bold;">Installation</span></a><a href="Install.htm"
style="color: rgb(255, 255, 255);"><span
style="color: rgb(255, 255, 255);"> </span></a><br>
<a href="Documentation.htm" style="color: rgb(255, 255, 255);"
font-weight="" bold=""><span ="">Documentation</span></a><br
style="color: rgb(255, 255, 255);">
<a href="FAQ.htm" style="color: rgb(255, 255, 255);"><span
style="font-weight: bold;">FAQ</span>s</a><span
style="color: rgb(255, 255, 255);">&nbsp;
(</span><a
href="http://wiki.rettc.com/wiki.phtml?title=Wiki_Shorewall_FAQ"
target="_top" style="color: rgb(255, 255, 255);">Wiki</a><span
style="color: rgb(255, 255, 255);">)</span><br
style="color: rgb(255, 255, 255);">
<a href="troubleshoot.htm" style="color: rgb(255, 255, 255);"><span
style="font-weight: bold;">Troubleshooting</span></a><br
style="color: rgb(255, 255, 255);">
<a href="support.htm" style="color: rgb(255, 255, 255);"><span
style="font-weight: bold;">Support</span></a><a href="support.htm"
style="color: rgb(255, 255, 255);"><span
style="color: rgb(255, 255, 255);">
</span></a><br style="color: rgb(255, 255, 255);">
<a href="shorewall_features.htm" style="color: rgb(255, 255, 255);">Features</a><br
style="color: rgb(255, 255, 255);">
<a href="Shorewall_Doesnt.html" style="color: rgb(255, 255, 255);">What
it
Cannot Do</a><span style="color: rgb(255, 255, 255);"> </span><br
style="color: rgb(255, 255, 255);">
<a href="shorewall_prerequisites.htm" style="color: rgb(255, 255, 255);">Requirements</a><br
style="color: rgb(255, 255, 255);">
<a href="http://lists.shorewall.net" style="color: rgb(255, 255, 255);">Mailing
Lists</a><a href="http://lists.shorewall.net"
style="color: rgb(255, 255, 255);"> </a> <br
style="color: rgb(255, 255, 255);">
<a href="upgrade_issues.htm" style="color: rgb(255, 255, 255);">Upgrade
Issues</a><br style="color: rgb(255, 255, 255);">
<a href="errata.htm" style="color: rgb(255, 255, 255);">Errata</a><br
style="color: rgb(255, 255, 255);">
<a href="shorewall_mirrors.htm" style="color: rgb(255, 255, 255);">Mirrors</a><span
style="color: rgb(255, 255, 255);"> </span><br
style="color: rgb(255, 255, 255);">
<a href="News.htm" style="color: rgb(255, 255, 255);">News
Archive</a><br style="color: rgb(255, 255, 255);">
<a href="http://cvs.shorewall.net/Shorewall_CVS_Access.html"
style="color: rgb(255, 255, 255);">CVS
Repository</a><br style="color: rgb(255, 255, 255);">
<a href="quotes.htm" style="color: rgb(255, 255, 255);">Quotes
from Users</a><br style="color: rgb(255, 255, 255);">
<a href="useful_links.html" style="color: rgb(255, 255, 255);">Useful
Links</a><br style="color: rgb(255, 255, 255);">
<a href="shoreline.htm" style="color: rgb(255, 255, 255);">About
the Author</a><br style="color: rgb(255, 255, 255);">
<a href="shorewall_index.htm#Donations"
style="color: rgb(255, 255, 255);">Donations</a>
<ul style="color: rgb(255, 255, 255);">
</ul>
<p><a href="copyright.htm" style="color: rgb(255, 255, 255);"><font
size="2">Copyright</font> © <font size="2">2001-2004 Thomas M. Eastep.</font></a><br>
</p>
<h1 align="center"><b><a href="http://www.sf.net"><img align="left"
alt="SourceForge Logo"
src="http://sourceforge.net/sflogo.php?group_id=22587&amp;type=1" title=""
style="border: 0px solid ; width: 88px; height: 31px;"></a></b></h1>
<br>
This site is hosted by the generous folks at <a
href="http://www.sf.net">SourceForge.net</a>
<small><span style="color: rgb(255, 255, 255);">Please report errors on
this site
to </span><a href="mailto:webmaster@shorewall.net"
style="color: rgb(255, 255, 255);">the Webmaster</a><span
style="color: rgb(255, 255, 255);">.</span></small><br>
</body>
</html>

View File

@ -22,7 +22,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>2004-06-15<br>
<p>2004-07-06<br>
</p>
<hr style="width: 100%; height: 2px;">
<p><b>I strongly urge you to read and print a copy of the <a
@ -54,7 +54,15 @@ chkconfig or insserv). If you find that it works in other cases, let <a
href="mailto:teastep@shorewall.net"> me</a> know so that I can mention
them here. See the <a href="Install.htm">Installation Instructions</a>
if you have problems installing the RPM.</li>
<li>If you are running LRP, download the .lrp file.<br>
<li>If you are running LEAF Bering or Bering uClibc, download the
.lrp file<br>
<br>
<span style="font-weight: bold;">Note</span>: Beginning with the
2.1 Development release, the .lrp file is named shorewall-lrp-<span
style="font-style: italic;">version</span>.tgz (e.g.,
shorewall-lrp-2.1.0.tgz). Simply rename this file to shorwall.lrp when
you move it to your LEAF system.<br>
<br>
</li>
<li>If you run <a href="http://www.debian.org"><b>Debian</b></a> and
would like a .deb package, Shorewall is included in both the <a

View File

@ -37,7 +37,7 @@ Documentation License</a></span>”.</p>
</div>
</div>
<div>
<p class="pubdate">2004-07-02<br>
<p class="pubdate">2004-07-29<br>
</p>
<hr style="width: 100%; height: 2px;"></div>
<h3>Table of Contents</h3>
@ -51,9 +51,15 @@ Shorewall</a><br>
two-interface setup?</a><br>
<a href="#License">License</a><br>
</div>
<a href="#News">News</a><a href="#2_0_3b"><br>
<a href="#News">News</a><a href="#2_0_7"><br>
</a>
<div style="margin-left: 40px;"><a href="#2_0_3c">Shorewall 2.0.3c</a><br>
<div style="margin-left: 40px;"><a href="#2_0_7">Shorewall 2.0.7</a><br>
<a href="#2_0_6">Shorewall 2.0.6</a><br>
<a href="#2_0_5">Shorewall 2.0.5</a><br>
<a href="#2_0_4">Shorewall 2.0.4</a><br>
<a href="#Release_Model">New Release
Model</a><br>
<a href="#2_0_3c">Shorewall 2.0.3c</a><br>
<a href="#2_0_3b">Shorewall 2.0.3b</a><br>
<a href="#2_0_3a">Shorewall 2.0.3a</a><br>
<a href="#2_0_3">Shorewall
@ -152,8 +158,280 @@ Documentation License"</a>. </div>
<p> </p>
<hr style="width: 100%; height: 2px;">
<h2><a name="News"></a>News</h2>
<span style="font-weight: bold;"><a name="2_0_3c"><span
style="font-weight: bold;">7/02/2004 -
<span style="font-weight: bold;"><a name="2_0_7"></a>7/29/2004 -
Shorewall 2.0.7<br>
<br>
</span>Problems Corrected:<br>
<ol>
<li>The PKTTYPE option introduced in version 2.0.6 is now used when
generating rules to REJECT packets. Broadcast packets are silently
dropped rather than being rejected with an ICMP (which is a protocol
violation) and users whose kernels have broken packet type match
support are likely to see messages reporting this violation. Setting
PKTTYPE=No should cause these messages to cease.</li>
<li>Multiple interfaces with the 'blacklist' option no longer result
in an error message at startup.</li>
<li>The following has been added to /etc/shorewall/bogons:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.0.0.0&nbsp;&nbsp; RETURN<br>
<br>
This prevents the 'nobogons' option from logging DHCP 'DISCOVER'
broadcasts.<br>
</li>
</ol>
New Features:<br>
<br>
<ol>
<li>To improve supportability, the "shorewall status" command now
includes IP and Route configuration information.<br>
<br>
&nbsp;&nbsp; Example:<br>
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; IP Configuration</span><br
style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 1: lo:
&lt;LOOPBACK,UP&gt; mtu 16436 qdisc noqueue</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
inet6 ::1/128 scope host</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 2: eth0:
&lt;BROADCAST,MULTICAST,PROMISC,UP&gt; mtu 1500 qdisc pfifo_fast qlen
1000</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
link/ether 00:a0:c9:15:39:78 brd ff:ff:ff:ff:ff:ff</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
inet6 fe80::2a0:c9ff:fe15:3978/64 scope link</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 3: eth1:
&lt;BROADCAST,MULTICAST,PROMISC,UP&gt; mtu 1500 qdisc pfifo_fast qlen
1000</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
link/ether 00:a0:c9:a7:d7:bf brd ff:ff:ff:ff:ff:ff</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
inet6 fe80::2a0:c9ff:fea7:d7bf/64 scope link</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 5: sit0@NONE:
&lt;NOARP&gt; mtu 1480 qdisc noop</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
link/sit 0.0.0.0 brd 0.0.0.0</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 6: eth2:
&lt;BROADCAST,MULTICAST,PROMISC,UP&gt; mtu 1500 qdisc pfifo_fast qlen
1000</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
link/ether 00:40:d0:07:3a:1b brd ff:ff:ff:ff:ff:ff</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
inet6 fe80::240:d0ff:fe07:3a1b/64 scope link</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 7: br0:
&lt;BROADCAST,MULTICAST,NOTRAILERS,UP&gt; mtu 1500 qdisc noqueue</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
link/ether 00:40:d0:07:3a:1b brd ff:ff:ff:ff:ff:ff</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
inet 192.168.1.3/24 brd 192.168.1.255 scope global br0</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
inet6 fe80::240:d0ff:fe07:3a1b/64 scope link</span><br
style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; Routing Rules</span><br
style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp;
0:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from all lookup local</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 32765:&nbsp;
from all fwmark&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ca lookup www.out</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 32766:&nbsp;
from all lookup main</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 32767:&nbsp;
from all lookup default</span><br style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; Table local:</span><br
style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; broadcast
192.168.1.0 dev br0&nbsp; proto kernel&nbsp; scope link&nbsp; src
192.168.1.3</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; broadcast
127.255.255.255 dev lo&nbsp; proto kernel&nbsp; scope link&nbsp; src
127.0.0.1</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; local
192.168.1.3 dev br0&nbsp; proto kernel&nbsp; scope host&nbsp; src
192.168.1.3</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; broadcast
192.168.1.255 dev br0&nbsp; proto kernel&nbsp; scope link&nbsp; src
192.168.1.3</span><br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; broadcast
127.0.0.0 dev lo&nbsp; proto kernel&nbsp; scope link&nbsp; src 127.0.0.1</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; local 127.0.0.1
dev lo&nbsp; proto kernel&nbsp; scope host&nbsp; src 127.0.0.1</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; local
127.0.0.0/8 dev lo&nbsp; proto kernel&nbsp; scope host&nbsp; src
127.0.0.1</span><br style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; Table www.out:</span><br
style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; default via
192.168.1.3 dev br0</span><br style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; Table main:</span><br
style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; 192.168.1.0/24
dev br0&nbsp; proto kernel&nbsp; scope link&nbsp; src 192.168.1.3</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; default via
192.168.1.254 dev br0</span><br style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;">&nbsp;&nbsp; Table default:</span><br
style="font-family: monospace;">
</li>
</ol>
<span style="font-weight: bold;"><a name="2_0_6"></a>7/16/2004 -
Shorewall 2.0.6<br>
<br>
</span>Problems Corrected:<br>
<ul>
<li>Some users have reported the packet type match option in
iptables/Netfilter failing to match certain broadcast packets. The
result is that the firewall log shows a lot of broadcast packets.<br>
<br>
Other users have complained of the following message when starting
Shorewall:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
modprobe: cant locate module ipt_pkttype<br>
<br>
Users experiencing either of these problems can use PKTTYPE=No in
shorewall.conf to cause Shorewall to use IP address filtering of
broadcasts rather than packet type.</li>
<li>The shorewall.conf and zones file are no longer given execute
permission by the installer script.</li>
<li>ICMP packets that are in the INVALID state are now dropped by the
Reject and Drop default actions. They do so using the new 'dropInvalid'
builtin action.<br>
</li>
</ul>
<span style="font-weight: bold;"><a name="2_0_5"></a>7/10/2004 -
Shorewall 2.0.5<br>
</span><br>
Problems Corrected:<br>
<ul>
<li>If DISABLE_IPV6=Yes in shorewall.conf then harmless error
messages referring to $RESTOREBASE are generated during <span
style="font-weight: bold;">shorewall stop</span>.</li>
<li>An anachronistic comment concerning a mangle option has been
removed from shorewall.conf.<br>
</li>
</ul>
<a name="2_0_4"></a><span style="font-weight: bold;">7/06/2004 -
Shorewall 2.0.4<br>
</span><br>
Problems Corrected:<br>
<ul>
<li>Rules with $FW as the source zone and that specify logging can
cause "shorewall start" to fail.<br>
</li>
</ul>
<a name="Release_Model"></a><span style="font-weight: bold;">7/03/2004
- New Shorewall Release Model<br>
<br>
</span>Effective today, Shorewall is adopting a new release model which
takes ideas from the one used in the Linux Kernel and from the release
model for Postfix.<br>
<ol>
<li>Releases continue to have a three-level identification <span
style="font-style: italic;">x.y.z</span> (e.g., 2.0.3).<br>
</li>
<li>The first two levels (<span style="font-style: italic;">x.y)</span>
designate the <span style="font-style: italic;">Major Release Number</span>
(e.g., 2.0)</li>
<li>The third level (<span style="font-style: italic;">z</span>)
designates the <span style="font-style: italic;">Minor Release Number</span>.</li>
<li>Even numbered major releases (e.g., <span
style="font-style: italic;">1.4, 2.0, 2.2, ...)</span> are <span
style="font-style: italic;">Stable Releases</span>. No new features
are added to stable releases and new minor releases of a stable release
will only contain bug fixes. Installing a new minor release for the
major release that you are currently running involves no migration
issues (for example, if you are running 1.4.10 and I release 1.4.11,
your current configuration is 100% compatible with the new release).</li>
<li>Support is available through the <a
href="http://lists.shorewall.net">Mailing List </a>for the two most
recent Stable Releases.<br>
</li>
<li>Odd numbered major releases (e.g., 2.1, 2.3, ...) are <span
style="font-style: italic;">Development Releases</span>. Development
releases are where new functionality is introduced. Documentation for
new features will be available but it may not be up to the standards of
the stable release documentation. Sites running Development Releases
should be prepared to play an active role in testing new features. Bug
fixes and problem resolution for the development release take a back
seat to support of the stable releases. Problem reports for the current
development release should be sent to the <a
href="mailto:shorewall-devel@lists.shorewall.net">Shorewall
Development Mailing List</a>.<br>
</li>
<li>When the level of functionality of the current development
release is judged adaquate, the Beta period for a new Stable release
will begin. Beta releases have identifications of the form <span
style="font-style: italic;">x.y.0-BetaN</span> where <span
style="font-style: italic;">x.y</span> is the number of the next
Stable Release and <span style="font-style: italic;">N</span>=1,2,3...
. Betas are expected to occur rougly once per year. Beta releases may
contain new functionality not present in the previous beta release
(e.g., 2.2.0-Beta4 may contain functionality not present in
2.2.0-Beta3). When I'm confident that the current Beta release is
stable, I will release the first <span style="font-style: italic;">Release
Candidate. </span>Release candidates have identifications of the form <span
style="font-style: italic;">x.y.0-RCn </span>where<span
style="font-style: italic;"> <span style="font-style: italic;">x.y</span>
</span>is the number of the next Stable Release and<span
style="font-style: italic;"> <span style="font-style: italic;">n</span></span>=1,2,3...
. Release candidates contain no new functionailty -- they only contain
bug fixes. When the stability of the current release candidate is
judged to be sufficient then that release candidate will be released as
the new stable release (e.g., 2.2.0). At that time, the new stable
release and the prior stable release are those that are supported.</li>
<li>What does it mean for a major release to be <span
style="font-style: italic;">supported?</span> It means that I will
answer questions about the release and that if a bug is found, I will
fix the bug and include the fix in the next minor release.</li>
<li>Between minor releases, bug fixes will continue to be made
available through the Errata page for each major release.<br>
</li>
</ol>
The immediate implications of this change are as follows:<br>
<ol>
<li>The functionality of the 2.0 major release is frozen at the level
of minor release 2.0.3.</li>
<li>The two major releases currently supported are 1.4 and 2.0.</li>
<li>I will be opening the 2.1 development release shortly with the
release of 2.1.0.</li>
<li>Bug-fix releases with identifications of the form <span
style="font-style: italic;">x.y.zX </span>where X=a,b,c,... (e.g.,
2.0.3c) will not be seen in the future.<br>
</li>
</ol>
<span style="font-weight: bold;"></span><span style="font-weight: bold;"><a
name="2_0_3c"><span style="font-weight: bold;">7/02/2004 -
Shorewall 2.0.3c<br>
<br>
</span></a></span>Problems Corrected<span style="font-weight: bold;">:<br>
@ -371,16 +649,16 @@ Netfilter configuration tool.<br>
<div style="text-align: center;"> </div>
</div>
<hr style="width: 100%; height: 2px;">
<h2><a name="Donations"></a>Donations
</h2>
<p style="text-align: left;"> </p>
<h2><a name="Donations"></a>Donations</h2>
<p style="text-align: left;"><big><a href="http://www.alz.org"
target="_top"><img src="images/alz_logo2.gif" title=""
target="_top"><img src="images/alz_logo2.gif"
alt="(Alzheimer's Association Logo)"
style="border: 0px solid ; width: 300px; height: 60px;" align="left"></a></big></p>
style="border: 0px solid ; width: 300px; height: 60px;" align="right"></a></big></p>
<h2></h2>
<p style="text-align: left;"> </p>
<h2><big><a href="http://www.starlight.org" target="_top"><img
src="images/newlog.gif" title="" alt="(Starlight Foundation Logo)"
style="border: 0px solid ; width: 59px; height: 102px;" align="left"></a></big></h2>
style="border: 0px solid ; width: 59px; height: 102px;" align="right"></a></big></h2>
<p style="text-align: left;"><big>Shorewall
is free but
if you

View File

@ -33,7 +33,7 @@ Documentation License</a></span>”.</p>
</div>
</div>
<div>
<p class="pubdate">2004-07-02</p>
<p class="pubdate">2004-07-14</p>
</div>
</div>
<hr></div>
@ -48,6 +48,11 @@ Documentation License</a></span>”.</p>
<td align="left" valign="middle">Linux Advanced Routing and
Traffic Control Howto: <a href="http://ds9a.nl/lartc" target="_top">http://ds9a.nl/lartc</a></td>
</tr>
<tr>
<td style="vertical-align: top;">Traffic Shaping Howto: <a
target="_top" href="http://www.tldp.org/HOWTO/Traffic-Control-HOWTO/">http://www.tldp.org/HOWTO/Traffic-Control-HOWTO/</a><br>
</td>
</tr>
<tr valign="middle">
<td align="left" valign="middle">Iproute Downloads: <a
href="ftp://ftp.inr.ac.ru/ip-routing" target="_top">ftp://ftp.inr.ac.ru/ip-routing</a></td>