2003-12-30 02:19:52 +01:00
|
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
|
|
|
<html>
|
|
|
|
|
<head>
|
|
|
|
|
<meta content="HTML Tidy, see www.w3.org" name="generator">
|
|
|
|
|
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
|
|
|
|
|
<title>Shoreline Firewall (Shorewall) 1.4</title>
|
|
|
|
|
<base target="_self">
|
|
|
|
|
</head>
|
|
|
|
|
<body>
|
|
|
|
|
<div>
|
|
|
|
|
<table border="0" cellpadding="0" cellspacing="0" id="AutoNumber4"
|
|
|
|
|
style="border-collapse: collapse; width: 100%; height: 100%;">
|
|
|
|
|
<tbody>
|
|
|
|
|
<tr>
|
|
|
|
|
<td width="90%">
|
|
|
|
|
<h2>Introduction to Shorewall</h2>
|
|
|
|
|
<h3>This is the Shorewall 1.4 Web Site</h3>
|
|
|
|
|
The information on this site applies only to 1.4.x releases of
|
|
|
|
|
Shorewall. For older versions:<br>
|
|
|
|
|
<ul>
|
|
|
|
|
<li>The 1.3 site is <a href="http://www.shorewall.net/1.3"
|
|
|
|
|
target="_top">here.</a></li>
|
|
|
|
|
<li>The 1.2 site is <a href="http://shorewall.net/1.2/"
|
|
|
|
|
target="_top">here</a>.</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<h3>Glossary</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<li><a href="http://www.netfilter.org">Netfilter</a> - the
|
|
|
|
|
packet filter facility built into the 2.4 and later Linux kernels.</li>
|
|
|
|
|
<li>ipchains - the packet filter facility built into the 2.2
|
|
|
|
|
Linux kernels. Also the name of the utility program used to configure
|
|
|
|
|
and control that facility. Netfilter can be used in ipchains
|
|
|
|
|
compatibility mode.</li>
|
|
|
|
|
<li>iptables - the utility program used to configure and
|
|
|
|
|
control Netfilter. The term 'iptables' is often used to refer to the
|
|
|
|
|
combination of iptables+Netfilter (with Netfilter not in ipchains
|
|
|
|
|
compatibility mode).</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<h3>What is Shorewall?</h3>
|
|
|
|
|
The Shoreline Firewall, more commonly known as "Shorewall", is
|
|
|
|
|
high-level tool for configuring Netfilter. You describe your
|
|
|
|
|
firewall/gateway requirements using entries in a set of configuration
|
|
|
|
|
files. Shorewall reads those configuration files and with the help of
|
|
|
|
|
the iptables utility, Shorewall configures Netfilter to match your
|
|
|
|
|
requirements. Shorewall can be used on a dedicated firewall system, a
|
|
|
|
|
multi-function gateway/router/server or on a standalone GNU/Linux
|
|
|
|
|
system. Shorewall does not use Netfilter's ipchains compatibility mode
|
|
|
|
|
and can thus take advantage of Netfilter's connection state tracking
|
|
|
|
|
capabilities.<br>
|
|
|
|
|
<br>
|
|
|
|
|
Shorewall is <span style="text-decoration: underline;">not</span> a
|
|
|
|
|
daemon. Once Shorewall has configured Netfilter, it's job is complete
|
|
|
|
|
although the <a href="starting_and_stopping_shorewall.htm">/sbin/shorewall
|
|
|
|
|
program can be used at any time to monitor the Netfilter firewall</a>.<br>
|
|
|
|
|
<h3>Getting Started with Shorewall</h3>
|
|
|
|
|
New to Shorewall? Start by selecting the <a
|
|
|
|
|
href="shorewall_quickstart_guide.htm">QuickStart Guide</a> that most
|
|
|
|
|
closely match your environment and follow the step by step instructions.<br>
|
|
|
|
|
<h3>Looking for Information?</h3>
|
|
|
|
|
The <a href="Documentation_Index.html">Documentation
|
|
|
|
|
Index</a> is a good place to start as is the Quick Search in the frame
|
|
|
|
|
above.
|
|
|
|
|
<h3>License</h3>
|
|
|
|
|
This program is free software; you can redistribute it and/or modify it
|
|
|
|
|
under the terms of <a href="http://www.gnu.org/licenses/gpl.html">Version
|
|
|
|
|
2 of the GNU General Public License</a> as published by the Free
|
|
|
|
|
Software Foundation.<br>
|
|
|
|
|
<p>This program is distributed in the hope that it will be
|
|
|
|
|
useful, but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
|
General Public License for more detail.</p>
|
|
|
|
|
<p>You should have received a copy of the GNU General Public
|
|
|
|
|
License along with this program; if not, write to the Free Software
|
|
|
|
|
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA</p>
|
|
|
|
|
Permission is granted to copy, distribute and/or modify this document
|
|
|
|
|
under the terms of the GNU Free Documentation License, Version 1.2 or
|
|
|
|
|
any later version published by the Free Software Foundation; with no
|
|
|
|
|
Invariant Sections, with no Front-Cover, and with no Back-Cover Texts.
|
|
|
|
|
A copy of the license is included in the section entitled <a>"GNU Free
|
|
|
|
|
Documentation License"</a>.
|
2004-01-13 23:33:26 +01:00
|
|
|
<p>Copyright © 2001-2004 Thomas M. Eastep </p>
|
2003-12-30 02:19:52 +01:00
|
|
|
<h3>Running Shorewall on Mandrake with a two-interface setup?</h3>
|
|
|
|
|
If so, the documentation <b></b>on this site will not apply directly
|
|
|
|
|
to your setup. If you want to use the documentation that you find here,
|
|
|
|
|
you will want to consider uninstalling what you have and installing a
|
|
|
|
|
setup that matches the documentation on this site. See the <a
|
|
|
|
|
href="two-interface.htm">Two-interface QuickStart Guide</a> for
|
|
|
|
|
details.<br>
|
|
|
|
|
<h2>News</h2>
|
2004-01-31 04:35:08 +01:00
|
|
|
<p><b>1/30/2004 - Shorewall 1.4.10</b><b> <img alt="(New)"
|
2003-12-30 02:19:52 +01:00
|
|
|
src="images/new10.gif"
|
2004-01-31 04:35:08 +01:00
|
|
|
style="border: 0px solid ; width: 28px; height: 12px;" title=""></b></p>
|
|
|
|
|
<p>Problems Corrected since version 1.4.9</p>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>The column descriptions in the action.template file did not
|
|
|
|
|
match the column headings. That has been corrected.</li>
|
|
|
|
|
<li>The presence of IPV6 addresses on devices generated error
|
|
|
|
|
messages during [re]start if ADD_IP_ALIASES=Yes or ADD_SNAT_ALIASES=Yes
|
|
|
|
|
are specified in /etc/shorewall/shorewall.conf. These messages have
|
|
|
|
|
been eliminated.</li>
|
|
|
|
|
<li>The CONTINUE action in /etc/shorewall/rules now works
|
|
|
|
|
correctly. A couple of problems involving rate limiting have been
|
|
|
|
|
corrected. These bug fixes courtesy of Steven Jan Springl.</li>
|
|
|
|
|
<li>Shorewall now tried to avoid sending an ICMP response to
|
|
|
|
|
broadcasts and smurfs.</li>
|
|
|
|
|
<li>Specifying "-" or "all" in the PROTO column of an action no
|
|
|
|
|
longer causes a startup error. <br>
|
|
|
|
|
<br>
|
|
|
|
|
</li>
|
|
|
|
|
</ol>
|
|
|
|
|
Migragion Issues:<br>
|
|
|
|
|
<br>
|
|
|
|
|
None.<br>
|
|
|
|
|
<br>
|
|
|
|
|
New Features:<br>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>The INTERFACE column in the /etc/shorewall/masq file may
|
|
|
|
|
now specify a destination list. <br>
|
|
|
|
|
<br>
|
|
|
|
|
Example:<br>
|
|
|
|
|
<br>
|
|
|
|
|
#INTERFACE
|
|
|
|
|
SUBNET ADDRESS<br>
|
|
|
|
|
eth0:192.0.2.3,192.0.2.16/28 eth1<br>
|
|
|
|
|
<br>
|
|
|
|
|
If the list begins with "!" then SNAT will occur only if the
|
|
|
|
|
destination IP address is NOT included in the list.<br>
|
|
|
|
|
<br>
|
|
|
|
|
</li>
|
|
|
|
|
<li>Output traffic control rules (those with the firewall as
|
|
|
|
|
the source) may now be qualified by the effective userid and/or
|
|
|
|
|
effective group id of the program generating the output. This feature
|
|
|
|
|
is courtesy of Frédéric LESPEZ.<br>
|
|
|
|
|
<br>
|
|
|
|
|
A new USER column has been added to /etc/shorewall/tcrules. It may
|
|
|
|
|
contain :<br>
|
|
|
|
|
<br>
|
|
|
|
|
[<user name or number>]:[<group
|
|
|
|
|
name or number>]<br>
|
|
|
|
|
<br>
|
|
|
|
|
The colon is optionnal when specifying only a user.<br>
|
|
|
|
|
<br>
|
|
|
|
|
Examples : john: / john / :users /
|
|
|
|
|
john:users<br>
|
|
|
|
|
<br>
|
|
|
|
|
</li>
|
|
|
|
|
<li>A "detectnets" interface option has been added for entries
|
|
|
|
|
in /etc/shorewall/interfaces. This option automatically taylors the
|
|
|
|
|
definition of the zone named in the ZONE column to include just
|
|
|
|
|
those hosts that have routes through the interface named in the
|
|
|
|
|
INTERFACE column. The named interface must be UP when Shorewall is
|
|
|
|
|
[re]started.<br>
|
|
|
|
|
<br>
|
|
|
|
|
WARNING: DO NOT SET THIS OPTION ON YOUR INTERNET INTERFACE! <br>
|
|
|
|
|
</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<p><b>1/17/2004 - FAQ Wiki Available </b><b></b></p>
|
|
|
|
|
<p>It has been asserted that the use of CVS for maintaining the
|
|
|
|
|
Shorewall documentation has been a barrier to community participation.
|
|
|
|
|
To test this theory, Alex Martin <a
|
|
|
|
|
href="http://wiki.rettc.com/wiki.phtml?title=Wiki_Shorewall_FAQ">has
|
|
|
|
|
created a Wiki</a> and with the help of Mike Noyes has populated the
|
|
|
|
|
Wiki with the Shorewall FAQ. <br>
|
|
|
|
|
</p>
|
|
|
|
|
<p><b>1/13/2004 - Shorewall 1.4.9 </b><b> </b></p>
|
2003-12-30 02:19:52 +01:00
|
|
|
<p>Problems Corrected since version 1.4.8:</p>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>There has been a low continuing level of confusion over the
|
|
|
|
|
terms "Source NAT" (SNAT) and "Static NAT". To avoid future confusion,
|
|
|
|
|
all instances of "Static NAT" have been replaced with "One-to-one NAT"
|
|
|
|
|
in the documentation and configuration files.</li>
|
|
|
|
|
<li>The description of NEWNOTSYN in shorewall.conf has been
|
|
|
|
|
reworded for clarity.</li>
|
|
|
|
|
<li>Wild-card rules (those involving "all" as SOURCE or DEST)
|
|
|
|
|
will no longer produce an error if they attempt to add a rule that
|
|
|
|
|
would override a NONE policy. The logic for expanding these wild-card
|
|
|
|
|
rules now simply skips those (SOURCE,DEST) pairs that have a NONE
|
|
|
|
|
policy.</li>
|
|
|
|
|
<li>DNAT rules that also specified SNAT now work reliably.
|
|
|
|
|
Previously, there were cases where the SNAT specification was
|
|
|
|
|
effectively ignored.<br>
|
|
|
|
|
</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<p>Migration Issues:</p>
|
|
|
|
|
<p> None.<br>
|
|
|
|
|
<br>
|
|
|
|
|
New Features: </p>
|
|
|
|
|
<ol>
|
|
|
|
|
<li>The documentation has been completely rebased to Docbook
|
|
|
|
|
XML. The documentation is now released as separate HTML and XML
|
|
|
|
|
packages.<br>
|
|
|
|
|
</li>
|
|
|
|
|
<li>To cut down on the number of "Why are these ports closed
|
|
|
|
|
rather than stealthed?" questions, the SMB-related rules in
|
|
|
|
|
/etc/shorewall/common.def have been changed from 'reject' to 'DROP'.</li>
|
|
|
|
|
<li>For easier identification, packets logged under the
|
|
|
|
|
'norfc1918' interface option are now logged out of chains named
|
|
|
|
|
'rfc1918'. Previously, such packets were logged under chains named
|
|
|
|
|
'logdrop'.</li>
|
|
|
|
|
<li>Distributors and developers seem to be regularly inventing
|
|
|
|
|
new naming conventions for kernel modules. To avoid the need to change
|
|
|
|
|
Shorewall code for each new convention, the MODULE_SUFFIX option has
|
|
|
|
|
been added to shorewall.conf. MODULE_SUFFIX may be set to the suffix
|
|
|
|
|
for module names in your particular distribution. If MODULE_SUFFIX is
|
|
|
|
|
not set in shorewall.conf, Shorewall will use the list "o gz ko o.gz".<br>
|
|
|
|
|
<br>
|
|
|
|
|
To see what suffix is used by your distribution:<br>
|
|
|
|
|
<br>
|
|
|
|
|
ls /lib/modules/$(uname -r)/kernel/net/ipv4/netfilter<br>
|
|
|
|
|
<br>
|
|
|
|
|
All of the files listed should have the same suffix (extension). Set
|
|
|
|
|
MODULE_SUFFIX to that suffix.<br>
|
|
|
|
|
<br>
|
|
|
|
|
Examples:<br>
|
|
|
|
|
<br>
|
|
|
|
|
If all files end in ".kzo" then set
|
|
|
|
|
MODULE_SUFFIX="kzo"<br>
|
|
|
|
|
If all files end in ".kz.o" then set
|
|
|
|
|
MODULE_SUFFIX="kz.o"</li>
|
|
|
|
|
<li>Support for user defined rule ACTIONS has been implemented
|
|
|
|
|
through two new files:<br>
|
|
|
|
|
<br>
|
|
|
|
|
/etc/shorewall/actions - used to list the user-defined ACTIONS.<br>
|
|
|
|
|
/etc/shorewall/action.template - For each user defined <action>,
|
|
|
|
|
copy this file to /etc/shorewall/action.<action> and add the
|
|
|
|
|
appropriate rules for that <action>. Once an <action> has
|
|
|
|
|
been defined, it may be used like any of the builtin ACTIONS (ACCEPT,
|
|
|
|
|
DROP, etc.) in /etc/shorewall/rules.<br>
|
|
|
|
|
<br>
|
|
|
|
|
Example: You want an action that logs a packet at the 'info' level and
|
|
|
|
|
accepts the connection.<br>
|
|
|
|
|
<br>
|
|
|
|
|
In /etc/shorewall/actions, you would add:<br>
|
|
|
|
|
<br>
|
|
|
|
|
LogAndAccept<br>
|
|
|
|
|
<br>
|
|
|
|
|
You would then copy /etc/shorewall/action.template to
|
2004-01-13 23:33:26 +01:00
|
|
|
/etc/shorewall/action.LogAndAccept and in that file, you would add the
|
|
|
|
|
two
|
2003-12-30 02:19:52 +01:00
|
|
|
rules:<br>
|
|
|
|
|
LOG:info<br>
|
|
|
|
|
ACCEPT<br>
|
|
|
|
|
</li>
|
|
|
|
|
<li>The default value for NEWNOTSYN in shorewall.conf is now
|
|
|
|
|
"Yes" (non-syn TCP packets that are not part of an existing connection
|
|
|
|
|
are filtered according to the rules and policies rather than being
|
|
|
|
|
dropped). I have made this change for two reasons:<br>
|
|
|
|
|
<br>
|
|
|
|
|
a) NEWNOTSYN=No tends to result in lots of "stuck" connections since
|
|
|
|
|
any timeout during TCP session tear down results in the firewall
|
|
|
|
|
dropping all of the retries.<br>
|
|
|
|
|
<br>
|
|
|
|
|
b) The old default of NEWNOTSYN=No and LOGNEWNOTSYN=info resulted in
|
|
|
|
|
lots of confusing messages when a connection got "stuck". While I could
|
|
|
|
|
have changed the default value of LOGNEWNOTSYN to suppress logging, I
|
2004-01-13 23:33:26 +01:00
|
|
|
dislike defaults that silently throw away packets.</li>
|
|
|
|
|
<li>The common.def file now contains an entry that silently
|
|
|
|
|
drops ICMP packets with a null source address. Ad Koster reported a
|
|
|
|
|
case where these were occuring frequently as a result of a broken
|
|
|
|
|
system on his external network.<br>
|
2003-12-30 02:19:52 +01:00
|
|
|
<br>
|
|
|
|
|
</li>
|
|
|
|
|
</ol>
|
|
|
|
|
<p><a href="News.htm">More News</a></p>
|
|
|
|
|
<p><a href="http://leaf.sourceforge.net" target="_top"><img
|
2004-01-07 22:59:17 +01:00
|
|
|
alt="(Leaf Logo)"
|
|
|
|
|
style="border: 0px solid ; height: 36px; width: 49px;"
|
|
|
|
|
src="images/leaflogo.gif" title=""></a> Jacques Nilo and Eric Wolzak
|
|
|
|
|
have a LEAF
|
2003-12-30 02:19:52 +01:00
|
|
|
(router/firewall/gateway on a floppy, CD or compact flash) distribution
|
|
|
|
|
called <i>Bering</i> that features Shorewall-1.4.2 and Kernel-2.4.20.
|
|
|
|
|
You can find their work at: <a
|
|
|
|
|
href="http://leaf.sourceforge.net/devel/jnilo">http://leaf.sourceforge.net/devel/jnilo<br>
|
|
|
|
|
</a></p>
|
|
|
|
|
<b>Congratulations to Jacques and Eric on the recent release of
|
2004-01-07 22:59:17 +01:00
|
|
|
Bering 1.2!!!</b><br>
|
2003-12-30 02:19:52 +01:00
|
|
|
<div>
|
|
|
|
|
<div style="text-align: center;"> </div>
|
|
|
|
|
</div>
|
|
|
|
|
<h2><a name="Donations"></a>Donations</h2>
|
|
|
|
|
<p style="text-align: left;"><a href="http://www.starlight.org"><img
|
|
|
|
|
align="left" alt="(Starlight Logo)" hspace="10" src="images/newlog.gif"
|
|
|
|
|
style="border: 4px solid ; width: 57px; height: 100px;" title=""></a><br>
|
|
|
|
|
<big>Shorewall is free but if you try it and find it useful,
|
|
|
|
|
please consider making a donation to <a href="http://www.starlight.org">Starlight
|
|
|
|
|
Children's Foundation</a>. Thanks!</big><br>
|
|
|
|
|
<a href="http://www.starlight.org"></a></p>
|
|
|
|
|
</td>
|
|
|
|
|
</tr>
|
2004-01-31 04:35:08 +01:00
|
|
|
<tr>
|
|
|
|
|
<td style="vertical-align: top;"><br>
|
|
|
|
|
</td>
|
|
|
|
|
</tr>
|
2003-12-30 02:19:52 +01:00
|
|
|
</tbody>
|
|
|
|
|
</table>
|
|
|
|
|
</div>
|
2004-01-31 04:35:08 +01:00
|
|
|
<p><font size="2">Updated 01/30/2004 - <a href="support.htm">Tom Eastep</a></font><br>
|
2003-12-30 02:19:52 +01:00
|
|
|
</p>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
