similar to: End of Support Life for Shorewall 1.4 will be February 1

Effective today, I will no longer offer support for Shorewall 1.4. Information on upgrading may be found at http://lists.shorewall.net/pipermail/shorewall-announce/2004-December/000451.html -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \

Just a reminder that I only support the last two major releases; so when Shorewall 2.0.0 is released, that will signal the end of support for Shorewall 1.3.x. Also, note that the 2.0.0 ''fallback.sh'' script will not work if you upgraded to 2.0.0 from a release earlier than 1.4.0. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta2 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta2 Problems Corrected: 1. The "shorewall check" command results in the (harmless) error message: /usr/share/shorewall/firewall: line 2753: check_dupliate_zones: command not found 2. The

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta2 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta2 Problems Corrected: 1. The "shorewall check" command results in the (harmless) error message: /usr/share/shorewall/firewall: line 2753: check_dupliate_zones: command not found 2. The

Shorewall 2.2.0 is expected to be released in the February/March timeframe so it is now time to begin thinking about preparing to upgrade. This is particularly important for those of you still running Shorewall 1.4 since support for that version will end with the release of 2.2. For those of you still running Shorewall 1.4, here are some things that you can do ahead of time to ease the upgrade to

I forgot to add the last new feature to the previous announcement. Shorewall 2.2.2 is now available. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.2 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.2 Problems Corrected: 1. The SOURCE column in the /etc/shorewall/tcrules file now correctly allows IP ranges (assuming that your iptables and kernel support ranges). 2.

FYI... ---------- Forwarded Message ---------- Subject: RE: [Shorewall-users] 2.6 kernel ipsec and shorewall Date: Thursday 23 September 2004 07:44 From: "Jonathan Schneider" <jon@clearconcepts.ca> To: "''Tom Eastep''" <teastep@shorewall.net> I must have been up too late working on this, looking at it the next day I noticed I completely forgot

Original was DOA. Updated MD5 sums are: ec30299a4c60f026838a02927b37cb71 releasenotes.txt 40017223e14f7b47a165eed599d13da6 shorewall-2.2.0-0Beta5.noarch.rpm c9ae4690d342c9602a696084d3f786a4 shorewall-2.2.0-Beta5.tgz 139703c7a28a32c9f2ad90548644a874 shorewall-docs-html-2.2.0-Beta5.tgz 8da4e53fbea986083483c878dca879f8 shorewall-docs-xml-2.2.0-Beta5.tgz 343d085a4fc8224bd105701717065f1f

Beginning with Shorewall 2.2.0, I am no longer going to maintain the Errata web page (http://shorewall.net/errata.htm). Rather, each version''s download directory will contain: a) A ''known_problems.txt'' file. This file will list all confirmed problems and any corrections or workarounds available. You will notice that the ''known problems'' file for the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''m hoping that this will be the last RC and that I can release 2.2.0 on February 1. I appreciate your help in testing this RC. http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC5 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC5 Problems Corrected: 1. The AllowTrcrt action has been changed to allow up to 30

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The first beta in the 2.2 series is now available. Download location is: http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta1 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta1 The features available in this release and the migration considerations are covered in the release notes. Highlights include: 1. The behavior

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta3 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta3 Problems Corrected: 1. Missing ''#'' in the rfc1918 file has been corrected. 2. The INSTALL file now includes special instructions for Slackware users. New Features: 1. In CLASSIFY rules

Hi I have 2nic firewall . I had to open some ranges of udp and tcp ports . I faced a problem that although all the ports are open Some functionality was not working . Any body used shorewall with H323 Voip traffic DNATed . Any help is appretiated . Thanks ----- Original Message ----- From: <shorewall-users-request@lists.shorewall.net> To: <shorewall-users@lists.shorewall.net> Sent:

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC4 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC4 New Features: 1. A listing of loaded iptables kernel modules is now included in the output of "shorewall status". Problems Corrected. 1. Several problems associated with processing the IPSEC column in /etc/shorewall/masq have been corrected. -Tom --

Shorewall 2.2.0 is now available from all download locations. Release notes may be found at: http://shorewall.net/pub/shorewall/2.2.shorewall-2.2.0/releasenotes.txt Be sure to pay careful attention to the section entitled "Issues when migrating from Shorewall 2.0 to Shorewall 2.2". I''ll continue to support Shorewall 1.4 for the next week or so after which time, support will

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta7 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta7 Problems Corrected: 1. The "shorewall add" and "shorewall delete" commands now work in a bridged environment. The syntax is: shorewall add <interface>[:<port>]:<address> <zone>

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta8 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta8 Problems Corrected: 1. A typo in the /etc/shorewall/interfaces file has been corrected. 2. Previously, the "add" and "delete" commands were generating incorrect policy matches when policy match support was available. New

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC2 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC2 New Features: 1. By popular demand, the default port for Open VPN has been changed to 1194 (the IANA-reserved port for Open VPN). -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta4 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta4 Problems Corrected: 1. A cut and paste error resulted in some nonsense in the description of the IPSEC column in /etc/shorewall/masq. 2. A typo in /etc/shorewall/rules has been corrected. 3. The bogons file has been updated. 4. The

My sincere apologies for the messed up 2.0.14. I didn''t realize that I had merged a change from 2.2.0 but hadn''t tested it. http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.15 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.15 1. The range of ports opened by the AllowTrcrt action has been expanded to 33434:33524 to allow for a maximum of 30 hops. 2. Code mis-ported