forked from extern/shorewall_code
Update for Shorewall 2.0.3a
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1417 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
fbd45622c5
commit
37f7b9fc27
@ -15,7 +15,7 @@
|
||||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>2004-06-11</pubdate>
|
||||
<pubdate>2004-06-25</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>2001</year>
|
||||
@ -65,15 +65,6 @@
|
||||
your own.</para>
|
||||
</important>
|
||||
|
||||
<warning>
|
||||
<para>If you have RedHat 7.2 and are running iptables version 1.2.3 (at
|
||||
a shell prompt, type <quote>/sbin/iptables --version</quote>), you must
|
||||
upgrade to version 1.2.4 either from the <ulink
|
||||
url="http://www.redhat.com/support/errata/RHSA-2001-144.html">RedHat
|
||||
update site</ulink> or from the <ulink url="errata.htm">Shorewall Errata
|
||||
page</ulink> before attempting to start Shorewall.</para>
|
||||
</warning>
|
||||
|
||||
<para>To install Shorewall using the RPM:</para>
|
||||
|
||||
<orderedlist>
|
||||
|
@ -13,7 +13,7 @@
|
||||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>2004-06-03</pubdate>
|
||||
<pubdate>2004-06-28</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>2001-2004</year>
|
||||
@ -87,6 +87,30 @@
|
||||
<section>
|
||||
<title>Problems in Version 2.0</title>
|
||||
|
||||
<section>
|
||||
<title>Shorewall 2.0.3</title>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>A non-empty entry in the DEST column of /etc/shorewall/tcrules
|
||||
will result in an error message and Shorewall fails to start. This
|
||||
problem may be corrected by installing <ulink
|
||||
url="http://shorewall.net/pub/shorewall/errata/2.0.3/firewall">this
|
||||
firewall script</ulink> in /usr/share/shorewall/firewall as
|
||||
described above. This problem is also fixed in Shorewall version
|
||||
2.0.3a.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>A potentially exploitable vulnerability in the way that
|
||||
Shorewall handles temporary files and directories has been found by
|
||||
Javier Fernández-Sanguino Peña. This vulnerability is corrected in
|
||||
Shorewall 2.0.3a. All Shorewall 2.0.x users are urged to upgrade to
|
||||
2.0.3a.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<title>Shorewall 2.0.2</title>
|
||||
|
||||
|
@ -15,7 +15,7 @@
|
||||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>2004-06-23</pubdate>
|
||||
<pubdate>2004-06-25</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>2001-2004</year>
|
||||
@ -75,9 +75,10 @@
|
||||
|
||||
<listitem>
|
||||
<para>I use SNAT through 206.124.146.179 for  my SuSE 9.0 Linux
|
||||
system (Wookie), my Wife's Windows XP system (Tarry), and
|
||||
our  Windows XP laptop (Tipper) which connects through the
|
||||
Wireless Access Point (wap) via a Wireless Bridge (wet).<note><para>While
|
||||
system <quote>Wookie</quote>, my Wife's Windows XP system
|
||||
<quote>Tarry</quote>, and our  dual-booting (Windows
|
||||
XP/Mandrake 10.0 Official) laptop <quote>Tipper</quote> which connects
|
||||
through the Wireless Access Point (wap) via a Wireless Bridge (wet).<note><para>While
|
||||
the distance between the WAP and where I usually use the laptop
|
||||
isn't very far (25 feet or so), using a WAC11 (CardBus wireless
|
||||
card) has proved very unsatisfactory (lots of lost connections). By
|
||||
|
@ -15,7 +15,7 @@
|
||||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>2004-02-11</pubdate>
|
||||
<pubdate>2004-06-23</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>2001-2004</year>
|
||||
@ -36,12 +36,14 @@
|
||||
<section>
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>Shorewall has limited support for traffic shaping/control. In order
|
||||
to use traffic shaping under Shorewall, it is essential that you get a
|
||||
copy of the <ulink url="http://ds9a.nl/lartc">Linux Advanced Routing and
|
||||
Shaping HOWTO</ulink>, version 0.3.0 or later. It is also necessary to be
|
||||
running Linux Kernel 2.4.18 or later. Shorewall traffic shaping support
|
||||
consists of the following:</para>
|
||||
<para>Shorewall does not do any type of Traffic Shaping/Bandwidth
|
||||
management itself but it does contain some facilities to intergrate with
|
||||
traffic shaping/control solutions. In order to use traffic shaping with
|
||||
Shorewall, it is essential that you get a copy of the <ulink
|
||||
url="http://ds9a.nl/lartc">Linux Advanced Routing and Shaping HOWTO</ulink>,
|
||||
version 0.3.0 or later. It is also necessary to be running Linux Kernel
|
||||
2.4.18 or later. Shorewall traffic shaping support consists of the
|
||||
following:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
Loading…
Reference in New Issue
Block a user