<p>Lorenzo Martignoni reports that the packages are version 1.3.5a and are available at <ahref="http://security.dsi.unimi.it/~lorenzo/debian.html">http://security.dsi.unimi.it/~lorenzo/debian.html</a>.</p>
<p>Lorenzo Marignoni reports that the packages are available at <ahref="http://security.dsi.unimi.it/~lorenzo/debian.html">http://security.dsi.unimi.it/~lorenzo/debian.html</a>.</p>
<p><b>7/6/2002 - Shorewall 1.3.3 Released</b></p>
<p>In this version:</p>
<ul>
<li>Entries in /etc/shorewall/interface that use the wildcard character ("+")
now have the "multi" option assumed.</li>
<li>The 'rfc1918' chain in the mangle table has been renamed 'man1918' to
make log messages generated from that chain distinguishable from those
generated by the 'rfc1918' chain in the filter table.</li>
<li>Interface names appearing in the hosts file are now validated against the
interfaces file.</li>
<li>The TARGET column in the rfc1918 file is now checked for correctness.</li>
<li>The chain structure in the nat table has been changed to reduce the
number of rules that a packet must traverse and to correct problems with
NAT_BEFORE_RULES=No</li>
<li>The "hits" command has been enhanced.</li>
</ul>
<p><b>6/25/2002 - Samples Updated for 1.3.2</b></p>
<p>The comments in the sample configuration files have been updated to reflect
<p>Lorenzo Marignoni reports that the package is available at <ahref="http://security.dsi.unimi.it/~lorenzo/debian.html">http://security.dsi.unimi.it/~lorenzo/debian.html</a>.</p>
<p><b>6/19/2002 - Documentation Available in PDF Format</b></p>
<p>Thanks to Mike Martinez, the Shorewall Documentation is now available for
<ahref="download.htm">download</a> in <ahref="http://www.adobe.com">Adobe</a>
<p>Lorenzo Marignoni reports that the package is available at <ahref="http://security.dsi.unimi.it/~lorenzo/debian.html">http://security.dsi.unimi.it/~lorenzo/debian.html</a>.</p>
<p><b>6/2/2002 - Samples Corrected</b></p>
<p>The 1.3.0 samples configurations had several serious problems that prevented
DNS and SSH from working properly. These problems have been corrected in the
<p>The quick search on the home page now excludes the mailing list archives.
The <ahref="htdig/search.html">Extended Search</a> allows excluding the
archives or restricting the search to just the archives. An archive search form
is also available on the <ahref="mailing_list.htm">mailing list information
page</a>.</p>
<p><b>3/28/2002 - Debian Shorewall News (From Lorenzo Martignoni)</b></p>
<ul>
<li>The 1.2.10 Debian Package is available at <ahref="http://security.dsi.unimi.it/~lorenzo/debian.html">http://security.dsi.unimi.it/~lorenzo/debian.html</a>.</li>
<li>The 1.2.9 Debian Package is also available at <ahref="http://security.dsi.unimi.it/~lorenzo/debian.html">http://security.dsi.unimi.it/~lorenzo/debian.html</a>.</li>
</ul>
<p><b>3/1/2002 - 1.2.8 Debian Package is Available</b></p>
<li>The "fw" zone <ahref="Documentation.htm#FW">may now be given a
different name</a>.</li>
<li>You may now place end-of-line comments (preceded by '#') in any of the
configuration files</li>
<li>There is now protection against against two state changing operations
occuring concurrently. This is implemented using the 'lockfile' utility if
it is available (lockfile is part of procmail); otherwise, a less robust
technique is used. The lockfile is created in the STATEDIR defined in
/etc/shorewall/shorewall.conf and has the name "lock".</li>
<li>"shorewall start" no longer fails if "detect" is
specified in <ahref="Documentation.htm#Interfaces">/etc/shorewall/interfaces</a> for an interface with subnet mask 255.255.255.255.</li>
</ul>
<p><b>1/27/2002 - Shorewall 1.2.3 Debian Package Available </b>-- see <ahref="http://security.dsi.unimi.it/~lorenzo/debian.html">http://security.dsi.unimi.it/~lorenzo/debian.html</a></p>
<p>This is a minor feature and bugfix release. The single new feature is:</p>
<ul>
<li>Support for TCP MSS Clamp to PMTU -- This support is usually required when
the internet connection is via PPPoE or PPTP and may be enabled using the <ahref="Documentation.htm#ClampMSS">CLAMPMSS</a>
option in /etc/shorewall/shorewall.conf.</li>
</ul>
<p>The following problems were corrected:</p>
<ul>
<li>The "shorewall status" command no longer hangs.</li>
<li>The "shorewall monitor" command now displays the icmpdef chain</li>
<li>The CLIENT PORT(S) column in tcrules is no longer ignored</li>
</ul>
<p><b>1/18/2002 - Shorewall 1.2.2 packaged with new </b><ahref="http://leaf.sourceforge.net">LEAF</a><b>
release</b></p>
<p>Jacques Nilo and Eric Wolzak have released a kernel 2.4.16 LEAF distribution
that includes Shorewall 1.2.2. See <ahref="http://leaf.sourceforge.net/devel/jnilo">http://leaf.sourceforge.net/devel/jnilo</a>
for details.</p>
<p><b>1/11/2002 - Debian Package (.deb) Now Available - </b>Thanks to <ahref="mailto:lorenzo.martignoni@milug.org">Lorenzo
Martignoni</a>, a 1.2.2 Shorewall Debian package is now available. There is a
link to Lorenzo's site from the <ahref="download.htm">Shorewall download page</a>.</p>
<p><b>1/9/2002 - Updated 1.2.2 /sbin/shorewall available - </b><ahref="/pub/shorewall/errata/1.2.2/shorewall">This
corrected version </a>restores the "shorewall status" command to
health.</p>
<p><b>1/8/2002 - Shorewall 1.2.2 Released</b></p>
<p>In version 1.2.2</p>
<ul>
<li>Support for IP blacklisting has been added
<ul>
<li>You specify whether you want packets from blacklisted hosts dropped or
rejected using the <ahref="Documentation.htm#BLDisposition">BLACKLIST_DISPOSITION
</a>setting in /etc/shorewall/shorewall.conf</li>
<li>You specify whether you want packets from blacklisted hosts logged and
at what syslog level using the <ahref="Documentation.htm#BLLoglevel">BLACKLIST_LOGLEVEL</a>
setting in /etc/shorewall/shorewall.conf</li>
<li>You list the IP addresses/subnets that you wish to blacklist in <ahref="Documentation.htm#Blacklist">/etc/shorewall/blacklist</a></li>
<li>You specify the interfaces you want checked against the blacklist
using the new "<ahref="Documentation.htm#BLInterface">blacklist</a>"
option in /etc/shorewall/interfaces.</li>
<li>The black list is refreshed from /etc/shorewall/blacklist by the
"shorewall refresh" command.</li>
</ul>
</li>
<li>Use of TCP RST replies has been expanded
<ul>
<li>TCP connection requests rejected because of a REJECT policy are now
replied with a TCP RST packet.</li>
<li>TCP connection requests rejected because of a protocol=all rule in
/etc/shorewall/rules are now replied with a TCP RST packet.</li>
</ul>
</li>
<li>A <ahref="Documentation.htm#Logfile">LOGFILE</a> specification has been
added to /etc/shorewall/shorewall.conf. LOGFILE is used to tell the
/sbin/shorewall program where to look for Shorewall messages.</li>
</ul>
<p><b>1/5/2002 - New Parameterized Samples (<ahref="ftp://ftp.shorewall.net/pub/shorewall/samples-1.2.0/"target="_blank">version
1.2.0</a>) released. </b>These are minor updates to the previously-released
samples. There are two new rules added:</p>
<ul>
<li>Unless you have explicitly enabled Auth connections (tcp port 113) to your
firewall, these connections will be REJECTED rather than DROPPED. This
speeds up connection establishment to some servers.</li>
<li>Orphan DNS replies are now silently dropped.</li>
</ul>
<p>See the README file for upgrade instructions.</p>
<p><b>1/1/2002 - <u><fontcolor="#FF6633">Shorewall Mailing List Moving</font></u></b></p>
<p>The Shorewall mailing list hosted at <ahref="http://sourceforge.net"> Sourceforge</a> is moving to Shorewall.net.
If you are a current subscriber to the list at Sourceforge, please <ahref="shorewall_mailing_list_migration.htm">see
these instructions</a>. If you would like to subscribe to the new list, visit <ahref="http://www.shorewall.net/mailman/listinfo/shorewall-users">http://www.shorewall.net/mailman/listinfo/shorewall-users</a>.</p>
<p><b>12/19/2001 - Thanks to <ahref="mailto:scowles@infohiiway.com">Steve
Cowles</a>, there is now a Shorewall mirror in Texas. </b>This web site is
mirrored at <ahref="http://www.infohiiway.com/shorewall"target="_top">http://www.infohiiway.com/shorewall</a>
and the ftp site is at <ahref="ftp://ftp.infohiiway.com/pub/mirrors/shorewall">ftp://ftp.infohiiway.com/pub/mirrors/shorewall</a>.<b> </b></p>
<p><b>11/30/2001 - A new set of the parameterized <ahref="ftp://ftp.shorewall.net/pub/shorewall/samples-1.1.18">Sample
Configurations</a> has been released</b>. In this version:</p>
<ul>
<li>Ping is now allowed between the zones.</li>
<li>In the three-interface configuration, it is now possible to configure the
internet services that are to be available to servers in the DMZ. </li>
</ul>
<p><b>11/20/2001 - The current version of Shorewall is 1.1.18. </b></p>
<p>In this version:</p>
<ul>
<li>The spelling of ADD_IP_ALIASES has been corrected in the shorewall.conf
file</li>
<li>The logic for deleting user-defined chains has been simplified so that it
avoids a bug in the LRP version of the 'cut' utility.</li>
<li>The /var/lib/lrpkg/shorwall.conf file has been corrected to properly
display the NAT entry in that file.</li>
</ul>
<p><b>11/19/2001 - Thanks to <ahref="mailto:shorewall@timelord.sk">Juraj
Ontkanin</a>, there is now a Shorewall mirror in the Slovak Republic</b>. The website is now mirrored at <ahref="http://www.nrg.sk/mirror/shorewall"target="_top">http://www.nrg.sk/mirror/shorewall</a>
and the FTP site is mirrored at <ahref="ftp://ftp.nrg.sk/mirror/shorewall">ftp://ftp.nrg.sk/mirror/shorewall</a>.</p>
<p><b>11/1/2001 - The current version of Shorewall is 1.1.17</b>. I intend
this to be the last of the 1.1 Shorewall releases.</p>
<p> In this version:</p>
<ul>
<li>The handling of <ahref="Documentation.htm#Aliases">ADD_IP_ALIASES</a>
has been corrected.<2E></li>
</ul>
<p><b>10/22/2001 - The current version of Shorewall is 1.1.16</b>. In this
version:</p>
<ul>
<li>A new "shorewall show connections" command has been added.</li>
<li>In the "shorewall monitor" output, the currently tracked
connections are now shown on a separate page.</li>
<li>Prior to this release, Shorewall unconditionally added the external IP
adddress(es) specified in /etc/shorewall/nat. Beginning with version
1.1.16, a new parameter (<ahref="Documentation.htm#Aliases">ADD_IP_ALIASES</a>)
may be set to "no" (or "No") to inhibit this behavior.
This allows IP aliases created using your distribution's network
configuration tools to be used in static NAT. </li>
</ul>
<p><b>10/15/2001 - The current version of Shorewall is 1.1.15.</b> In this
version:</p>
<ul>
<li>Support for nested zones has been improved. See <ahref="Documentation.htm#Nested">
the documentation</a>
for details</li>
<li>Shorewall now correctly checks the alternate configuration directory for
the 'zones' file.</li>
</ul>
<p><b>10/4/2001 - The current version of Shorewall is 1.1.14.</b> In this version</p>
<ul>
<li>Shorewall now supports alternate configuration directories. When an
alternate directory is specified when starting or restarting Shorewall
(e.g., "shorewall -c /etc/testconf restart"), Shorewall will first
look for configuration files in the alternate directory then in
/etc/shorewall. To create an alternate configuration simply:<br>
1. Create a New Directory<br>
2. Copy to that directory any of your configuration files that you want to
change.<br>
3. Modify the copied files as needed.<br>
4. Restart Shorewall specifying the new directory.</li>
<li>The rules for allowing/disallowing icmp echo-requests (pings) are now
moved after rules created when processing the rules file. This allows you to
add rules that selectively allow/deny ping based on source or destination
address.</li>
<li>Rules that specify multiple client ip addresses or subnets no longer cause
startup failures.</li>
<li>Zone names in the policy file are now validated against the zones file.</li>
<li>If you have <ahref="Documentation.htm#MangleEnabled">packet mangling</a>
support enabled, the "<ahref="Documentation.htm#Interfaces">norfc1918</a>"
interface option now logs and drops any incoming packets on the interface
that have an RFC 1918 destination address.</li>
</ul>
<p><b>9/12/2001 - The current version of Shorewall is 1.1.13</b>. In this version</p>
<ul>
<li>Shell variables can now be used to parameterize Shorewall rules.</li>
<li>The second column in the hosts file may now contain a comma-separated
list.<br>
<br>
Example:<br>
sea
eth0:130.252.100.0/24,206.191.149.0/24</li>
<li>Handling of multi-zone interfaces has been improved. See the <ahref="Documentation.htm#Interfaces">documentation
for the /etc/shorewall/interfaces file</a>.</li>
</ul>
<p><b>8/28/2001 - The current version of Shorewall is 1.1.12</b>. In this version</p>
<ul>
<li>Several columns in the rules file may now contain comma-separated lists.</li>
<li>Shorewall is now more rigorous in parsing the options in
/etc/shorewall/interfaces.</li>
<li>Complementation using "!" is now supported in rules.</li>
</ul>
<p><b>7/28/2001 - The current version of Shorewall is 1.1.11</b>. In this version</p>
<ul>
<li>A "shorewall refresh" command has been added to allow for
refreshing the rules associated with the broadcast address on a dynamic
interface. This command should be used in place of "shorewall
restart" when the internet interface's IP address changes.</li>
<li>The /etc/shorewall/start file (if any) is now processed after all
temporary rules have been deleted. This change prevents the accidental
removal of rules added during the processing of that file.</li>
<li>The "dhcp" interface option is now applicable to firewall
interfaces used by a DHCP server running on the firewall.</li>
<li>The RPM can now be built from the .tgz file using "rpm -tb" </li>
</ul>
<p><b>7/6/2001 - The current version of Shorewall is 1.1.10.</b> In this version</p>
<ul>
<li>Shorewall now enables Ipv4 Packet Forwarding by default. Packet forwarding
may be disabled by specifying IP_FORWARD=Off in
/etc/shorewall/shorewall.conf. If you don't want Shorewall to enable or
disable packet forwarding, add IP_FORWARDING=Keep to your
/etc/shorewall/shorewall.conf file.</li>
<li>The "shorewall hits" command no longer lists extraneous service
names in its last report.</li>
<li>Erroneous instructions in the comments at the head of the firewall script
have been corrected.</li>
</ul>
<p><b>6/23/2001 - The current version of Shorewall is 1.1.9.</b> In this version</p>
<ul>
<li>The "tunnels" file <u>really</u> is in the RPM now.</li>
<li>SNAT can now be applied to port-forwarded connections.</li>
<li>A bug which would cause firewall start failures in some dhcp configurations
has been fixed.</li>
<li>The firewall script now issues a message if you have the name of an
interface in the second column in an entry in /etc/shorewall/masq and that
interface is not up.</li>
<li>You can now configure Shorewall so that it<ahref="Documentation.htm#NatEnabled"> doesn't require the NAT and/or
mangle netfilter modules</a>.</li>
<li>Thanks to Alex Polishchuk, the "hits" command
from seawall is now in shorewall.</li>
<li>Support for <ahref="IPIP.htm">IPIP tunnels</a> has been added.</li>
</ul>
<p><b>6/18/2001 - The current version of Shorewall is 1.1.8</b>. In this version</p>
<ul>
<li>A typo in the sample rules file has been corrected.</li>
<li>It is now possible to restrict masquerading by<ahref="Documentation.htm#Masq">
destination host or subnet.</a></li>
<li>It is now possible to have static <ahref="NAT.htm#LocalPackets">NAT rules
applied to packets originating on the firewall itself</a>.</li>
</ul>
<p><b>6/2/2001 - The current version of Shorewall is 1.1.7.</b> In this version</p>
<ul>
<li>The TOS rules are now deleted when the firewall is stopped.</li>
<li>The .rpm will now install regardless of which version of iptables is
installed.</li>
<li>The .rpm will now install without iproute2 being installed.</li>
<li>The documentation has been cleaned up.</li>
<li>The sample configuration files included in Shorewall have been formatted
to 80 columns for ease of editing on a VGA console.</li>
</ul>
<p><b>5/25/2001 - The current version of Shorewall is 1.1.6</b>. In this version</p>
<ul>
<li><ahref="Documentation.htm#lograte">You may now rate-limit the packet log.</a></li>
<li><fontface="Century Gothic, Arial, Helvetica"> Previous versions of
Shorewall have an implementation of Static NAT which violates the principle
of least surprise. NAT only occurs for packets arriving at (DNAT) or
send from (SNAT) the interface named in the INTERFACE column of
/etc/shorewall/nat. Beginning with version 1.1.6, NAT effective regardless
of which interface packets come from or are destined to. To get
compatibility with prior versions, I have added a new "ALL <ahref="NAT.htm#AllInterFaces">"ALL
INTERFACES" column to /etc/shorewall/nat</a>. By placing
"no" or "No" in the new column, the NAT behavior of
prior versions may be retained. </font></li>
<li>The treatment of <ahref="IPSEC.htm#RoadWarrior">IPSEC Tunnels where the remote
gateway is a standalone system has been improved</a>. Previously, it was
necessary to include an additional rule allowing UDP port 500 traffic to
pass through the tunnel. Shorewall will now create this rule automatically
when you place the name of the remote peer's zone in a new GATEWAY ZONE
column in /etc/shorewall/tunnels. </li>
</ul>
<p><b>5/20/2001 - The current version of Shorewall is 1.1.5.</b> In this version</p>
<ul>
<li><ahref="Documentation.htm#modules">You may now pass parameters when loading
netfilter modules and you can specify the modules to load.</a></li>
<li>Compressed modules are now loaded. This requires that you modutils support
loading compressed modules.</li>
<li><ahref="Documentation.htm#TOS">You may now set the Type of Service (TOS)
field in packets.</a></li>
<li>Corrected rules generated for port redirection (again).</li>
</ul>
<p><b>5/10/2001 - The current version of Shorewall is 1.1.4.</b> In this version</p>
<ul>
<li><ahref="Documentation.htm#Conf">Accepting RELATED connections is now
optional.</a></li>
<li>Corrected problem where if "shorewall start" aborted early
(due to kernel configuration errors for example), superfluous 'sed' error
messages were reported.</li>
<li>Corrected rules generated for port redirection.</li>
<li>The order in which iptables kernel modules are loaded has been
corrected (Thanks to Mark Pavlidis). </li>
</ul>
<p><b>4/28/2001 - The current version of Shorewall is 1.1.3.</b> In this version</p>
<ul>
<li>Correct message issued when Proxy ARP address added (Thanks to Jason Kirtland).</li>
<li>/tmp/shorewallpolicy-$$ is now removed if there is an error while starting the firewall.</li>
<li>/etc/shorewall/icmp.def and /etc/shorewall/common.def are now used to define the icmpdef and common chains unless overridden by the presence of /etc/shorewall/icmpdef or /etc/shorewall/common.</li>
<li>In the .lrp, the file /var/lib/lrpkg/shorwall.conf has been corrected. An extra space after "/etc/shorwall/policy" has been removed and "/etc/shorwall/rules" has been added.</li>
<li>When a sub-shell encounters a fatal error and has stopped the firewall, it now kills the main shell so that the main shell will not continue.</li>
<li>A problem has been corrected where a sub-shell stopped the firewall and main shell continued resulting in a perplexing error message
referring to "common.so" resulted.</li>
<li>Previously, placing "-" in the PORT(S) column in /etc/shorewall/rules resulted in an error message during start. This has been corrected.</li>
<li>The first line of "install.sh" has been corrected -- I had inadvertently deleted the initial "#".</li>
</ul>
<p><b>4/12/2001 - The current version of Shorewall is 1.1.2.</b> In this version</p>
<ul>
<li>Port redirection now works again.</li>
<li>The icmpdef and common chains <ahref="Documentation.htm#Icmpdef">may
now be user-defined</a>.</li>
<li>The firewall no longer fails to start if "routefilter" is
specified for an interface that isn't started. A warning message is now
issued in this case.</li>
<li>The LRP Version is renamed "shorwall" for 8,3 MSDOS file
system compatibility.</li>
<li>A couple of LRP-specific problems were corrected.</li>
</ul>
<p><b>4/8/2001 - Shorewall is now affiliated with the <ahref="http://leaf.sourceforge.net">Leaf
