forked from extern/shorewall_code
74 lines
2.8 KiB
XML
74 lines
2.8 KiB
XML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
|
||
|
|
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
||
|
|
<article>
|
||
|
|
<articleinfo>
|
||
|
|
<title>Shorewall Requirements</title>
|
||
|
|
|
||
|
|
<author>
|
||
|
|
<firstname>Tom</firstname>
|
||
|
|
|
||
|
|
<surname>Eastep</surname>
|
||
|
|
</author>
|
||
|
|
|
||
|
|
<copyright>
|
||
|
|
<year>2001-2003</year>
|
||
|
|
|
||
|
|
<holder>Thomas M Eastep</holder>
|
||
|
|
</copyright>
|
||
|
|
|
||
|
|
<pubdate>2003-12-01</pubdate>
|
||
|
|
</articleinfo>
|
||
|
|
|
||
|
|
<sect1>
|
||
|
|
<title>Shorewall Requires:</title>
|
||
|
|
|
||
|
|
<itemizedlist>
|
||
|
|
<listitem>
|
||
|
|
<para>A kernel that supports netfilter. I've tested with 2.4.2 -
|
||
|
|
2.4.23. With current releases of Shorewall, Traffic Shaping/Control
|
||
|
|
requires at least 2.4.18. Check <ulink url="kernel.htm">here</ulink>
|
||
|
|
for kernel configuration information. If you are looking for a
|
||
|
|
firewall for use with 2.2 kernels, see <ulink
|
||
|
|
url="http://seawall.sourceforge.net">the Seattle Firewall site</ulink>.</para>
|
||
|
|
</listitem>
|
||
|
|
|
||
|
|
<listitem>
|
||
|
|
<para>iptables 1.2 or later but beware version 1.2.3 -- see the <ulink
|
||
|
|
url="errata.htm">Errata</ulink>. <emphasis role="bold">WARNING</emphasis>:
|
||
|
|
The buggy iptables version 1.2.3 is included in RedHat 7.2 and you
|
||
|
|
should upgrade to iptables 1.2.4 prior to installing Shorewall.
|
||
|
|
Version 1.2.4 is available <ulink
|
||
|
|
url="http://www.redhat.com/support/errata/RHSA-2001-144.html">from
|
||
|
|
RedHat</ulink> and in the <ulink url="errata.htm">Shorewall Errata</ulink>.</para>
|
||
|
|
</listitem>
|
||
|
|
|
||
|
|
<listitem>
|
||
|
|
<para>Iproute ("ip" utility). The iproute package is included
|
||
|
|
with most distributions but may not be installed by default. The
|
||
|
|
official download site is <ulink target="_top"
|
||
|
|
url="ftp://ftp.inr.ac.ru/ip-routing">ftp://ftp.inr.ac.ru/ip-routing</ulink>.</para>
|
||
|
|
</listitem>
|
||
|
|
|
||
|
|
<listitem>
|
||
|
|
<para>A Bourne shell or derivative such as bash or ash. This shell
|
||
|
|
must have correct support for variable expansion formats ${<emphasis>variable%pattern</emphasis>},
|
||
|
|
${<emphasis>variable%%pattern</emphasis>}, ${<emphasis>variable#pattern</emphasis>}
|
||
|
|
and ${<emphasis>variable##pattern</emphasis>}.</para>
|
||
|
|
</listitem>
|
||
|
|
|
||
|
|
<listitem>
|
||
|
|
<para>Your shell must produce a sensible result when a number n (128
|
||
|
|
<= n <= 255) is left shifted by 24 bits. You can check this at
|
||
|
|
a shell prompt by:<itemizedlist><listitem><para>echo $((128 <<
|
||
|
|
24))</para></listitem><listitem><para>The result must be either
|
||
|
|
2147483648 or -2147483648.</para></listitem></itemizedlist></para>
|
||
|
|
</listitem>
|
||
|
|
|
||
|
|
<listitem>
|
||
|
|
<para>The firewall monitoring display is greatly improved if you have
|
||
|
|
awk (gawk) installed.</para>
|
||
|
|
</listitem>
|
||
|
|
</itemizedlist>
|
||
|
|
</sect1>
|
||
|
|
</article>
|