forked from extern/shorewall_code
edfbafc0cb
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@691 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
326 lines
14 KiB
HTML
326 lines
14 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<html>
|
|
<head>
|
|
<meta http-equiv="Content-Type"
|
|
content="text/html; charset=windows-1252">
|
|
<title>Shoreline Firewall (Shorewall) 1.4</title>
|
|
<base target="_self">
|
|
</head>
|
|
<body>
|
|
<table cellpadding="0" cellspacing="4"
|
|
style="border-collapse: collapse;" width="100%" id="AutoNumber3"
|
|
bgcolor="#3366ff">
|
|
<tbody>
|
|
<tr>
|
|
<td width="33%" height="90" valign="middle" align="center"><a
|
|
href="http://www.cityofshoreline.com"> </a>
|
|
<div align="center"> <img src="images/Logo1.png"
|
|
alt="(Shorewall Logo)" width="430" height="90" align="middle"> </div>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<div align="center">
|
|
<div align="center"> </div>
|
|
<center>
|
|
<div align="center"> </div>
|
|
<table border="0" cellpadding="0" cellspacing="0"
|
|
style="border-collapse: collapse;" width="100%" id="AutoNumber4">
|
|
<tbody>
|
|
<tr>
|
|
<td width="90%">
|
|
<h2>Introduction<br>
|
|
</h2>
|
|
<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.<br>
|
|
</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).<br>
|
|
</li>
|
|
</ul>
|
|
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>
|
|
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 details.<br>
|
|
<br>
|
|
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>
|
|
<p><a href="copyright.htm">Copyright 2001, 2002, 2003 Thomas M.
|
|
Eastep</a></p>
|
|
<h2>This is the Shorewall 1.4 Web Site</h2>
|
|
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>.<br>
|
|
</li>
|
|
</ul>
|
|
<h2>Getting Started with Shorewall</h2>
|
|
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>
|
|
<h2>Looking for Information?</h2>
|
|
The <a href="shorewall_quickstart_guide.htm#Documentation">Documentation
|
|
Index</a> is a good place to start as is the Quick Search to your
|
|
right.
|
|
<h2>Running Shorewall on Mandrake with a two-interface setup?</h2>
|
|
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>
|
|
<p><b>8/9/2003 - Snapshot 1.4.6_20030809</b><b> <img
|
|
style="border: 0px solid ; width: 28px; height: 12px;"
|
|
src="images/new10.gif" alt="(New)" title=""></b><b> </b></p>
|
|
<blockquote>
|
|
<p><a href="http://shorewall.net/pub/shorewall/Snapshots/">http://shorewall.net/pub/shorewall/Snapshots/</a><br>
|
|
<a href="ftp://shorewall.net/pub/shorewall/Snapshots/"
|
|
target="_top">ftp://shorewall.net/pub/shorewall/Snapshots/</a></p>
|
|
</blockquote>
|
|
<b>Problems Corrected since version 1.4.6</b><br>
|
|
<ol>
|
|
<li>Corrected problem in 1.4.6 where the MANGLE_ENABLED
|
|
variable was being tested before it was set.</li>
|
|
<li>Corrected handling of MAC addresses in the SOURCE column of
|
|
the tcrules file. Previously, these addresses resulted in an invalid
|
|
iptables command.</li>
|
|
<li>The "shorewall stop" command is now disabled when
|
|
/etc/shorewall/startup_disabled exists. This prevents people from
|
|
shooting themselves in the foot prior to having configured Shorewall.</li>
|
|
<li>A change introduced in version 1.4.6 caused error messages
|
|
during "shorewall [re]start" when ADD_IP_ALIASES=Yes and ip addresses
|
|
were being added to a PPP interface; the addresses were successfully
|
|
added in spite of the messages.<br>
|
|
<br>
|
|
The firewall script has been modified to eliminate the error messages<br>
|
|
</li>
|
|
</ol>
|
|
<b>Migration Issues:</b><br>
|
|
<ol>
|
|
<li>Once you have installed this version of Shorewall, you must
|
|
restart Shorewall before you may use the 'drop', 'reject', 'allow' or
|
|
'save' commands.</li>
|
|
<li>To maintain strict compatibility with previous versions,
|
|
current uses of "shorewall drop" and "shorewall reject" should be
|
|
replaced with "shorewall dropall" and "shorewall rejectall" </li>
|
|
</ol>
|
|
<b>New Features:</b><br>
|
|
<ol>
|
|
<li>Shorewall now creates a dynamic blacklisting chain for each
|
|
interface defined in /etc/shorewall/interfaces. The 'drop' and 'reject'
|
|
commands use the routing table to determine which of these chains is to
|
|
be used for blacklisting the specified IP address(es).<br>
|
|
<br>
|
|
Two new commands ('dropall' and 'rejectall') have been introduced that
|
|
do what 'drop' and 'reject' used to do; namely, when an address is
|
|
blacklisted using these new commands, it will be blacklisted on all of
|
|
your firewall's interfaces.</li>
|
|
<li>Thanks to Steve Herber, the 'help' command can now give
|
|
command-specific help (e.g., shorewall help <command>).</li>
|
|
<li>A new option "ADMINISABSENTMINDED" has been added to
|
|
/etc/shorewall/shorewall.conf. This option has a default value of "No"
|
|
for existing users which causes Shorewall's 'stopped' state to
|
|
continue as it has been; namely, in the stopped state only traffic
|
|
to/from hosts listed in /etc/shorewall/routestopped is accepted.<br>
|
|
<br>
|
|
With ADMINISABSENTMINDED=Yes (the default for new installs), in
|
|
addition to traffic to/from the hosts listed in
|
|
/etc/shorewall/routestopped, Shorewall will allow:<br>
|
|
<br>
|
|
a) All traffic originating from the firewall itself; and<br>
|
|
b) All traffic that is part of or related to an
|
|
already-existing connection.<br>
|
|
<br>
|
|
In particular, with ADMINISABSENTMINDED=Yes, a "shorewall stop"
|
|
entered through an ssh session will not kill the session.<br>
|
|
<br>
|
|
Note though that even with ADMINISABSENTMINDED=Yes, it is still
|
|
possible for people to shoot themselves in the foot.<br>
|
|
<br>
|
|
Example:<br>
|
|
<br>
|
|
/etc/shorewall/nat:<br>
|
|
<br>
|
|
206.124.146.178
|
|
eth0:0 192.168.1.5 <br>
|
|
<br>
|
|
/etc/shorewall/rules:<br>
|
|
<br>
|
|
ACCEPT net
|
|
loc:192.168.1.5 tcp 22<br>
|
|
ACCEPT loc
|
|
fw tcp 22<br>
|
|
<br>
|
|
From a remote system, I ssh to 206.124.146.178 which establishes an SSH
|
|
connection with local system 192.168.1.5. I then create a second SSH
|
|
connection
|
|
from that computer to the firewall and confidently type "shorewall
|
|
stop".
|
|
As part of its stop processing, Shorewall removes eth0:0 which kills my
|
|
SSH
|
|
connection to 192.168.1.5!!!</li>
|
|
<li>Given the wide range of VPN software, I can never hope to
|
|
add specific support for all of it. I have therefore decided to add
|
|
"generic" tunnel support.<br>
|
|
<br>
|
|
Generic tunnels work pretty much like any of the other tunnel types.
|
|
You usually add a zone to represent the systems at the other end of the
|
|
tunnel and you add the appropriate rules/policies to<br>
|
|
implement your security policy regarding traffic to/from those systems.<br>
|
|
<br>
|
|
In the /etc/shorewall/tunnels file, you can have entries of the form:<br>
|
|
<br>
|
|
generic:<protocol>[:<port>] <zone> <ip
|
|
address> <gateway zones><br>
|
|
<br>
|
|
where:<br>
|
|
<br>
|
|
<protocol> is the protocol
|
|
used by the tunnel<br>
|
|
<port> if the protocol
|
|
is 'udp' or 'tcp' then this is the destination port number used by the
|
|
tunnel.<br>
|
|
<zone> is the zone of
|
|
the remote tunnel gateway<br>
|
|
<ip address> is the IP
|
|
address of the remote tunnel gateway.<br>
|
|
<gateway zone>
|
|
Optional. A comma-separated list of zone names. If specified, the
|
|
remote gateway is to be considered part of these zones.</li>
|
|
<li>An 'arp_filter' option has been added to the
|
|
/etc/shorewall/interfaces file. This option causes
|
|
/proc/sys/net/ipv4/conf/<interface>/arp_filter to be set with the
|
|
result that this interface will only answer ARP 'who-has' requests from
|
|
hosts that are routed out through that interface. Setting this option
|
|
facilitates testing of your firewall where multiple firewall interfaces
|
|
are connected to the same HUB/Switch (all interfaces connected to the
|
|
single HUB/Switch should have this option specified). Note that using
|
|
such a configuration in a production environment is strongly
|
|
recommended against.<br>
|
|
</li>
|
|
</ol>
|
|
<p><b>8/5/2003 - Shorewall-1.4.6b</b><b> <img border="0"
|
|
src="images/new10.gif" width="28" height="12" alt="(New)"> <br>
|
|
</b></p>
|
|
<b>Problems Corrected since version 1.4.6:</b><br>
|
|
<ol>
|
|
<li>Previously, if TC_ENABLED is set to yes in shorewall.conf
|
|
then Shorewall would fail to start with the error "ERROR: Traffic
|
|
Control requires Mangle"; that problem has been corrected.</li>
|
|
<li>Corrected handling of MAC addresses in the SOURCE column of
|
|
the
|
|
tcrules file. Previously, these addresses resulted in an invalid
|
|
iptables
|
|
command.</li>
|
|
<li>The "shorewall stop" command is now disabled when
|
|
/etc/shorewall/startup_disabled
|
|
exists. This prevents people from shooting themselves in the foot prior
|
|
to
|
|
having configured Shorewall.</li>
|
|
<li>A change introduced in version 1.4.6 caused error messages
|
|
during
|
|
"shorewall [re]start" when ADD_IP_ALIASES=Yes and ip addresses were
|
|
being
|
|
added to a PPP interface; the addresses were successfully added in
|
|
spite
|
|
of the messages.<br>
|
|
<br>
|
|
The firewall script has been modified to eliminate the error messages.<br>
|
|
</li>
|
|
</ol>
|
|
<p><b></b></p>
|
|
<ol>
|
|
</ol>
|
|
<p><a href="News.htm">More News</a></p>
|
|
<p> <a href="http://leaf.sourceforge.net" target="_top"><img
|
|
border="0" src="images/leaflogo.gif" width="49" height="36"
|
|
alt="(Leaf Logo)"> </a>Jacques Nilo and Eric Wolzak have a LEAF
|
|
(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 Bering 1.2!!! </b><br>
|
|
<h2><a name="Donations"></a>Donations</h2>
|
|
</td>
|
|
<td width="88" bgcolor="#3366ff" valign="top" align="center">
|
|
<form method="post"
|
|
action="http://lists.shorewall.net/cgi-bin/htsearch"> <strong><br>
|
|
<font color="#ffffff"><b>Note: </b></font></strong><font
|
|
color="#ffffff">Search is unavailable Daily 0200-0330 GMT.</font><br>
|
|
<strong></strong>
|
|
<p><font color="#ffffff"><strong>Quick Search</strong></font><br>
|
|
<font face="Arial" size="-1"> <input type="text" name="words"
|
|
size="15"></font><font size="-1"> </font> <font face="Arial"
|
|
size="-1"> <input type="hidden" name="format" value="long"> <input
|
|
type="hidden" name="method" value="and"> <input type="hidden"
|
|
name="config" value="htdig"> <input type="submit" value="Search"></font>
|
|
</p>
|
|
<font face="Arial"> <input type="hidden" name="exclude"
|
|
value="[http://lists.shorewall.net/pipermail/*]"> </font> </form>
|
|
<p><font color="#ffffff"><b><a
|
|
href="http://lists.shorewall.net/htdig/search.html"><font
|
|
color="#ffffff">Extended Search</font></a></b></font></p>
|
|
<br>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</center>
|
|
</div>
|
|
<table border="0" cellpadding="5" cellspacing="0"
|
|
style="border-collapse: collapse;" width="100%" id="AutoNumber2"
|
|
bgcolor="#3366ff">
|
|
<tbody>
|
|
<tr>
|
|
<td width="100%" style="margin-top: 1px;" valign="middle">
|
|
<p align="center"><a href="http://www.starlight.org"> <img
|
|
border="4" src="images/newlog.gif" width="57" height="100" align="left"
|
|
hspace="10" alt="(Starlight Logo)"> </a></p>
|
|
<p align="center"><font size="4" color="#ffffff"><br>
|
|
<font size="+2"> Shorewall is free but if you try it and find it
|
|
useful, please consider making a donation to <a
|
|
href="http://www.starlight.org"><font color="#ffffff">Starlight
|
|
Children's Foundation.</font></a> Thanks!</font></font></p>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<p><font size="2">Updated 8/9/2003 - <a href="support.htm">Tom Eastep</a></font>
|
|
<br>
|
|
</p>
|
|
<br>
|
|
</body>
|
|
</html>
|