Displaying 20 results from an estimated 20000 matches similar to: "If you have downloaded 1.3.0..."
2002 May 29
0
Shorewall 1.3.0 Released
1.3.0 is available from the main site -- mirrors will syncronize in 6-12
hours.
Features include:
1. The rules syntax for port forwarding and port redirection has been
simplified.
2. Compatibility has been maintained with version 1.2 configurations so
that users may migrate their configuration at their convenience.
WARNING: Compatibility has NOT been maintained with the parameterized
2002 Apr 28
0
[Documentation] Re: [Shorewall-users] Logging is done to console (fwd)
This is becoming a FAQ and should probably be added to the docs.
Thanks,
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
---------- Forwarded message ----------
Date: Sun, 28 Apr 2002 16:09:01 -0700 (Pacific Daylight Time)
From: Tom Eastep <teastep@shorewall.net>
To: Carl Spelkens
2002 Mar 03
0
Fwd: Re: strange UDP scan results on a Shorewall firewall
---------- Forwarded Message ----------
Subject: Re: [Shorewall-users] strange UDP scan results on a Shorewall=20
firewall
Date: Sun, 3 Mar 2002 08:33:20 -0800
From: Tom Eastep <teastep@shorewall.net>
To: "Scott Duncan" <sduncan@cytechconsult.com>
On Saturday 02 March 2002 04:30 am, Scott Duncan wrote:
> Yes, the net->all policy is the same on all three (REJECT log
2002 Jul 06
0
Shorewall 1.3.3
Shorewall 1.3.3 is now available for download.
In this release:
1. Entries in /etc/shorewall/interface that use the wildcard character
("+") now have the "multi" option assumed.
2. The ''rfc1918'' chain in the mangle table has been renamed ''man1918''
to make log messages generated from that chain distinguishable from
those generated
2002 Jul 25
5
Shorewall 1.3.5
This will be the last Shorewall release for a while as I''m going to be
focusing on Documentation.
In this release:
1. Empty and invalid source and destination qualifiers are now detected
in the rules file. It is a good idea to use the ''shorewall check''
command before you issue a ''shorewall restart'' command be be sure
that you don''t
2002 May 10
0
Re: [Shorewall-users] (no subject)
On Sat, 11 May 2002, Peter Käll wrote:
> Hi!
>
> Thanks for the very fast help. Now it works.
>
> I downloaded the 1.2.13 version and the two interfaces example. The example
> includes a common file without UPNP dropping.
>
> In the begining of the common file in the example it says "Shorewall 1.2".
> the common.def files that comes the 1.2.13 version
2002 Jun 15
4
Serious Bug found in Shorewall 1.3.x
Rafa³ Dutko has just discovered a potentially serious bug in version 1.3.0
and 1.3.1. In both versions, where an interface option appears on multiple
interfaces, the option may only be applied to the first interface on which
it appears.
A corrected firewall script for 1.3.1 is available at:
http://www.shorewall.net/pub/shorewall/errata/1.3.1/firewall
and
2002 May 18
0
Shorewall 1.3 Beta 2
o There are lots of changes in the firewall structure -- beware if you use
/etc/shorewall/start to insert rules into the Shorewall-generated ruleset.
o Sub-zones may now be excluded from DNAT and REDIRECT rules.
o The names of the columns in a number of configuration files have been
changed to be more consistent and self-explanatory.
o The sample configuration files have been updated for 1.3.
2002 Sep 29
3
Shorewall 1.3.9
Shorewall 1.3.9 is available.
In this release:
1. DNS Names are now allowed in Shorewall config files (I still recommend
against using them however).
2. The connection SOURCE may now be qualified by both interface
and IP address in a Shorewall rule.
3. Shorewall startup is now disabled after initial installation until
the file /etc/shorewall/startup_disabled is removed.
4. The
2002 May 04
0
Shorewall 1.2.13 Available
In this release:
1. Whitelist support has been added.
2. Optional SYN Flood protection is now available.
3. Aliases added under ADD_IP_ALIASES and ADD_SNAT_ALIASES
now use the VLSM and broadcast address of the interface''s
primary address.
4. Port forwarding rules may now optionally override the
contents of the /etc/shorewall/nat file.
-Tom
--
Tom Eastep \ Shorewall -
2002 May 07
0
Shorewall-1.2.13 .deb is now in Debian Unstable
Thanks, Lorenzo!
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 May 14
3
[Shorewall-users] Redirect loc::80 to fw::3128 not work (fwd)
I''m beginning to believe that the use of the last column in the rules file
to designate redirection/forwarding is too subtle for many users. For 1.3,
I think I''ll do something like the following:
Current rule:
ACCEPT net loc:192.168.1.3 tcp 80 - all
New rule:
FORWARD net loc:192.168.1.3 tcp 80
Current rule:
ACCEPT net fw::3128 tcp 80 - all
New rule:
REDIRECT net
2002 May 14
2
Shorewall.net is back up
Let me know if there are any problems.
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 Jul 16
1
Shorewall 1.3.4
Shorewall 1.3.4 is available:
1. A new /etc/shorewall/routestopped file has been added. This file is
intended to eventually replace the routestopped option in the
/etc/shorewall/interface and /etc/ shorewall/hosts files. This new
file makes remote firewall administration easier by allowing any IP
or subnet to be enabled while Shorewall is stopped.
2. An /etc/shorewall/stopped
2002 Nov 20
3
Spam vs. Viruses
I have purchased a license for Vexira MailArmor (an antivirus product) and
the good news is that it is installed and working at shorewall.net. The bad
news is that I have yet to get Vexira running together with SpamAssassin :-(
As things currently stand, list posts will be protected from viruses but
may contain Spam. I''ll continue to work to correct this situation.
-Tom
--
Tom Eastep
2002 Jan 26
1
Shorewall 1.2.4 Beta
Shorewall 1.2.4 will have the following changes:
a) ''#'' comments now allowed at end-of-line in all config files.
b) Firewall zone may be renamed
c) Protection against concurrent state-changing operations (start, stop,
restart, refresh, clear)
d) ''shorewall start'' no longer fails if ''detect'' is specified for an
interface with netmask
2002 Apr 16
1
SuSE RPM Available
Thanks to Stefan Mohr, a Shorewall 1.2.11 RPM package for SuSE is now
available. See http://www.shorewall.net.
Thanks Stefan!!
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 Apr 16
1
Shorewall Debian News
Lorenzo Marignoni reports that:
o Shorewall 1.2.10 is in the Debian Testing Branch
o Shorewall 1.2.11 is in the Debian Unstable Branch
Thanks, Lorenzo!
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 May 15
4
Your opinion please
The 1.2 firewall contains messy logic to support the old sample
configurations in that any rule that contains "none" in any of its columns
is ignored.
I''m considering removing that messiness in 1.3 and seek the opinion of the
list.
Thanks,
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 Nov 12
3
''all'' in rules file
I have implemented the ability to specify ''all'' in the SOURCE and
DESTINATION columns of the rules file and I''m not sure I like the result.
The code is in CVS if any of you are interested in giving it a try. If you
do try it, please let me know what you think.
If you specify ''all'' in those columns it must not be qualified (may not be
followed by