mirror of
https://gitlab.com/shorewall/code.git
synced 2024-11-14 19:54:06 +01:00
Update Website
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1943 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep
parent
9ef7109da9
commit
1e5b2870a0
@ -22,7 +22,7 @@ Texts. A copy of the license is included in the section entitled “<span
|
||||
class="quote"><a href="GnuCopyright.htm" target="_self">GNU Free
|
||||
Documentation License</a></span>”.<br>
|
||||
</p>
|
||||
<p>2005-01-26<br>
|
||||
<p>2005-02-03<br>
|
||||
</p>
|
||||
<hr style="width: 100%; height: 2px;">
|
||||
<p><b>I strongly urge you to read and print a copy of the <a
|
||||
@ -102,9 +102,95 @@ Unstable Branch</a>.</li>
|
||||
</ul>
|
||||
<p>You will probably also want to download the HTML version of the
|
||||
documentation for easy reference.</p>
|
||||
<p>Please check the <font color="#ff0000"> <a href="errata.htm">
|
||||
errata</a></font> to see if there are updates that apply to the version
|
||||
that you have downloaded.</p>
|
||||
<p>Beginning with Shorewall 2.2.0, you will find a file named
|
||||
known_problems.txt in the download directory. This file lists the known
|
||||
problems with that version of Shorewall. If corrections are available,
|
||||
they will be listed in the known problems and you can download them
|
||||
from the 'errata' subdirectory.<br>
|
||||
</p>
|
||||
<p>Example:<br>
|
||||
</p>
|
||||
<p style="margin-left: 40px;"><span style="font-family: monospace;">ftp>
|
||||
cd
|
||||
pub/shorewall/2.2/shorewall-2.2.0</span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">250 OK. Current directory is
|
||||
/pub/shorewall/2.2/shorewall-2.2.0</span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">ftp> ls</span><span
|
||||
style="font-family: monospace;"></span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">227 Entering Passive Mode
|
||||
(206,124,146,177,35,91)</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">150 Accepted data connection</span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">drwxr-sr-x 3
|
||||
0
|
||||
0
|
||||
4096 Feb 1 09:52 .</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">drwxr-sr-x 3
|
||||
0
|
||||
0
|
||||
4096 Jan 28 14:28 ..</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">-rw-r--r-- 1
|
||||
0
|
||||
0
|
||||
500 Jan 28 14:27 2.2.0.md5sums</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace; color: rgb(204, 0, 0);">drwxr-sr-x
|
||||
2 0
|
||||
0
|
||||
4096 Feb 1 09:51
|
||||
errata
|
||||
<=== (1)</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace; color: rgb(204, 0, 0);">-rw-r--r--
|
||||
1 0
|
||||
0
|
||||
156 Feb 1 09:52 known_problems.txt <=== (2)</span><span
|
||||
style="font-family: monospace;"></span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">-rw-r--r-- 1
|
||||
0
|
||||
0 16059 Jan
|
||||
24 16:13 patch-2.2.0</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">-rwxr-xr-x 1
|
||||
0
|
||||
0 22963 Jan
|
||||
24 16:10 releasenotes.txt</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">-rw-r--r-- 1
|
||||
0
|
||||
0 100232 Jan 25
|
||||
15:58 shorewall-2.2.0-1.noarch.rpm</span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">-rw-r--r-- 1
|
||||
0
|
||||
0 122161 Jan 25
|
||||
15:58 shorewall-2.2.0.tgz</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">-rw-r--r-- 1
|
||||
0
|
||||
0 2534077 Jan 28 13:29
|
||||
shorewall-docs-html-2.2.0.tgz</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">-rw-r--r-- 1
|
||||
0
|
||||
0 4481205 Jan 28 13:29
|
||||
shorewall-docs-xml-2.2.0.tgz</span><br style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">-rw-r--r-- 1
|
||||
0
|
||||
0 93905 Jan
|
||||
25 15:58 shorewall-lrp-2.2.0.tgz</span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">226-Options: -a -l</span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">226 13 matches total</span><br
|
||||
style="font-family: monospace;">
|
||||
<span style="font-family: monospace;">ftp><br>
|
||||
</span></p>
|
||||
<p style="margin-left: 40px;"><span style="font-family: monospace;"><span
|
||||
style="color: rgb(204, 0, 0);">(1) Directory contraining updates.</span><br
|
||||
style="color: rgb(204, 0, 0);">
|
||||
<span style="color: rgb(204, 0, 0);">(2) List of known problems,
|
||||
workarounds and updates. </span>
|
||||
</span><br>
|
||||
</p>
|
||||
<p><b></b></p>
|
||||
<p><b>Download Sites:<br>
|
||||
</b></p>
|
||||
|
||||
@ -32,7 +32,8 @@ to 2.x releases of Shorewall. For older versions:</p>
|
||||
href="http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.0/releasenotes.txt">release
|
||||
notes</a> and here are the <a
|
||||
href="http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.0/known_problems.txt">known
|
||||
problems</a>.<br>
|
||||
problems</a> and <a
|
||||
href="http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.0/errata/">updates</a>.<br>
|
||||
</p>
|
||||
<p><a
|
||||
href="http://lists.shorewall.net/pipermail/shorewall-announce/2004-December/000451.html"><span
|
||||
@ -47,7 +48,7 @@ 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 href="GnuCopyright.htm" target="_self">GNU
|
||||
Free Documentation License</a>”.</p>
|
||||
<p>2005-02-01</p>
|
||||
<p>2005-02-05</p>
|
||||
<hr>
|
||||
<h3>Table of Contents</h3>
|
||||
<p style="margin-left: 0.42in; margin-bottom: 0in;"><a href="#Intro">Introduction
|
||||
@ -63,7 +64,9 @@ Shorewall on Mandrake® with a two-interface setup?</a><br>
|
||||
<a href="#License">License</a></p>
|
||||
<p style="margin-bottom: 0in; margin-left: 40px;"><a href="#2_0_10">News</a></p>
|
||||
<p style="margin-left: 0.83in; margin-bottom: 0in;"><span
|
||||
style="text-decoration: underline;"></span><a href="#2_2_0">Shorewall
|
||||
style="text-decoration: underline;"></span><a href="#2_0_16">Shorewall
|
||||
2.0.16</a><br>
|
||||
<a href="#2_2_0">Shorewall
|
||||
2.2.0</a><br>
|
||||
<br>
|
||||
</p>
|
||||
@ -158,6 +161,34 @@ of the license is included in the section entitled "GNU Free
|
||||
Documentation License". </p>
|
||||
<hr>
|
||||
<h2><a name="News"></a>News</h2>
|
||||
<span style="font-weight: bold;"><a name="2_0_16"></a>02/01/2005
|
||||
Shorewall 2.0.16<br>
|
||||
</span><br>
|
||||
This release back-ports the DROPINVALID shorewall.conf option from
|
||||
2.2.0.<br>
|
||||
<ol>
|
||||
<li>Recent 2.6 kernels include code that evaluates TCP packets based
|
||||
on TCP Window analysis. This can cause packets that were previously
|
||||
classified as NEW or ESTABLISHED to be classified as INVALID.<br>
|
||||
<br>
|
||||
The new kernel code can be disabled by including this command in your
|
||||
/etc/shorewall/init file:<br>
|
||||
<br>
|
||||
echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal<br>
|
||||
<br>
|
||||
Additional kernel logging about INVALID TCP packets may be obtained by
|
||||
adding this command to /etc/shorewall/init:<br>
|
||||
<br>
|
||||
echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_log_invalid<br>
|
||||
<br>
|
||||
Traditionally, Shorewall has dropped INVALID TCP packets early. The new
|
||||
DROPINVALID option allows INVALID packets to be passed through the
|
||||
normal rules chains by setting DROPINVALID=No.<br>
|
||||
<br>
|
||||
If not specified or if specified as empty (e.g., DROPINVALID="") then
|
||||
DROPINVALID=Yes is assumed.<br>
|
||||
</li>
|
||||
</ol>
|
||||
<span style="font-weight: bold;"><a name="2_2_0"></a>02/01/2005
|
||||
Shorewall 2.2.0<br>
|
||||
<br>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user