holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Shorewall 2.0.4

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1454 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-07-06 18:18:08 +00:00
parent b5d7c70310
commit aed68c56e5
3 changed files with 28 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Shorewall-docs2/ReleaseModel.xml
View File

@ -135,7 +135,8 @@
<listitem> <listitem>
<para>New functionality was added in minor releases of the current <para>New functionality was added in minor releases of the current
major release.</para> major release. There was no concept of Stable vs Development major
releases.</para>
</listitem> </listitem>
<listitem> <listitem>

20
Shorewall-docs2/errata.xml
View File

@ -13,7 +13,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2004-07-02</pubdate> <pubdate>2004-07-06</pubdate>
<copyright> <copyright>
<year>2001-2004</year> <year>2001-2004</year>
@ -87,6 +87,22 @@
<section> <section>
<title>Problems in Version 2.0</title> <title>Problems in Version 2.0</title>
<section>
<title>Shorewall 2.0.2 and all Shorewall 2.0.3 Releases.</title>
<itemizedlist>
<listitem>
<para>DNAT rules with <emphasis role="bold">fw</emphasis> as the
source zone and that specify logging cause <command>shorewall start</command>
to fail with an iptables error. The problem is corrected for
Shorewall 2.0.3 users in <ulink
url="http://shorewall.net/pub/shorewall/errata/2.0.3/firewall">this
firewall script</ulink> which may be installed in
/usr/share/shorewall/firewall as described above.</para>
</listitem>
</itemizedlist>
</section>
<section> <section>
<title>Shorewall 2.0.3a and 2.0.3b</title> <title>Shorewall 2.0.3a and 2.0.3b</title>
@ -103,7 +119,7 @@
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para>These problems are corrected in Shorewall version 2.0.3c.</para> <para>The above problems are corrected in Shorewall version 2.0.3c.</para>
</section> </section>
<section> <section>

16
Shorewall-docs2/myfiles.xml
View File

@ -15,7 +15,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2004-06-25</pubdate> <pubdate>2004-07-04</pubdate>
<copyright> <copyright>
<year>2001-2004</year> <year>2001-2004</year>
@ -42,12 +42,12 @@
address. If you have just a single public IP address, most of what you address. If you have just a single public IP address, most of what you
see here won&#39;t apply to your setup so beware of copying parts of see here won&#39;t apply to your setup so beware of copying parts of
this configuration and expecting them to work for you. What you copy may this configuration and expecting them to work for you. What you copy may
or may not work in your configuration.</para> or may not work for you.</para>
</caution> </caution>
<caution> <caution>
<para>The configuration shown here corresponds to Shorewall version <para>The configuration shown here corresponds to Shorewall version
2.0.1. My configuration uses features not available in earlier Shorewall 2.0.3. My configuration uses features not available in earlier Shorewall
releases.</para> releases.</para>
</caution> </caution>
@ -69,7 +69,7 @@
<listitem> <listitem>
<para>I use one-to-one NAT for EastepLaptop (My work system -- Windows <para>I use one-to-one NAT for EastepLaptop (My work system -- Windows
XP SP2). Internal address 192.168.1.7 and external address XP SP1). Internal address 192.168.1.7 and external address
206.124.146.180.</para> 206.124.146.180.</para>
</listitem> </listitem>
@ -99,7 +99,7 @@
<para>The firewall runs on a 256MB PII/233 with Debian Sarge (Testing).</para> <para>The firewall runs on a 256MB PII/233 with Debian Sarge (Testing).</para>
<para>Wookie and Ursa run Samba and the Wookie acts as a WINS server.</para> <para>Wookie and Ursa run Samba and Wookie acts as a WINS server.</para>
<para>The wireless network connects to Wookie&#39;s eth2 via a LinkSys <para>The wireless network connects to Wookie&#39;s eth2 via a LinkSys
WAP11.&#x00A0; In additional to using the rather weak WEP 40-bit WAP11.&#x00A0; In additional to using the rather weak WEP 40-bit
@ -124,7 +124,7 @@
desktop environment installed and that desktop environment is available desktop environment installed and that desktop environment is available
via XDMCP from the local zone. For the most part though, X tunneled via XDMCP from the local zone. For the most part though, X tunneled
through SSH is used for server administration and the server runs at run through SSH is used for server administration and the server runs at run
level 3 (multi-user console mode on RedHat).</para> level 3 (multi-user console mode on Fedora).</para>
<para>I run an SNMP server on my firewall to serve <ulink <para>I run an SNMP server on my firewall to serve <ulink
url="http://www.ee.ethz.ch/~oetiker/webtools/mrtg/">MRTG</ulink> running url="http://www.ee.ethz.ch/~oetiker/webtools/mrtg/">MRTG</ulink> running
@ -190,7 +190,7 @@ TCP_FLAGS_DISPOSITION=DROP
<blockquote> <blockquote>
<para><programlisting>MIRRORS=&#60;list of shorewall mirror ip addresses&#62; <para><programlisting>MIRRORS=&#60;list of shorewall mirror ip addresses&#62;
NTPSERVERS=&#60;list of the NTP servers I sync with&#62; NTPSERVERS=&#60;list of the NTP servers I sync with&#62;
TEXAS=&#60;ip address of gateway in Dallas&#62; TEXAS=&#60;ip address of gateway in Plano&#62;
LOG=info</programlisting></para> LOG=info</programlisting></para>
</blockquote> </blockquote>
</section> </section>
@ -203,7 +203,7 @@ LOG=info</programlisting></para>
net Internet Internet net Internet Internet
dmz DMZ Demilitarized zone dmz DMZ Demilitarized zone
loc Local Local networks loc Local Local networks
tx Texas Peer Network in Dallas tx Texas Peer Network in Plano
#LAST LINE -- ADD YOUR ENTRIES ABOVE THIS ONE - DO NOT REMOVE</programlisting> #LAST LINE -- ADD YOUR ENTRIES ABOVE THIS ONE - DO NOT REMOVE</programlisting>
</blockquote> </blockquote>
</section> </section>