similar to: Shorewall 1.4.0 Alpha 1

The administrator of the main web/ftp site has informed me that the site is currently down. Until service is restored, you can use: http://www1.shorewall.net ftp://ftp1.shorewall.net Sorry for the inconvenience. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \

Attached please find updated build and publish scripts. They set the ''ulink.target'' parameter appropriately when converting docbook->HTML. I have always hacked my xhtml/params.xsl file to set this parameter; these updated scripts make that abomination unnecessary. Paul/Mike: It might be a good idea to add a CVS project for these scripts. -Tom -- Tom Eastep \ Nothing is

http://www1.shorewall.net/pub/shorewall/3.0/shorewall-3.0.6/ ftp://ftp1.shorewall.net/pub/shorewall/3.0/shorewall-3.0.6/ Coming soon to a Mirror near you. Problems corrected in 3.0.6 1) A typo in the output of "help drop" has been corrected. 2) Previously, ''shorewall start'' would fail in the presence of a network interface named ''inet''. 3)

Beta 1 is now available. http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta Contrary to my previous plan, Beta 1 uses the same file and directory names as the current Shorewall version so the Beta will not be able to co-exist with a Shorewall 1.4 installation. Before installing the Beta, please review the release notes carefully. Once you have installed the Beta,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, I will be rebuilding my server. I expect the project to take most of the day. I will begin around 7AM PST (-0800). The server hosts the following sites: www1.shorewall.net (a.k.a. shorewall.net) ftp1.shorewall.net lists.shorewall.net rsync.shorewall.net Sorry for the inconvenience. - -Tom - -- Tom Eastep \ Nothing is foolproof

While I rebuild my server, shorewall.net is running on an old slow system. This affects: lists.shorewall.net shorewall.net ftp1.shorewall.net www1.shorewall.net I encourage you to avoid these systems until the new server is ready. Thanks, -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

The following systems will be down this weekend for server rebuild: shorewall.net lists.shorewall.net www1.shorewall.net ftp1.shorewall.net rsync.shorewall.net cvs.shorewall.net This will affect: Shorewall site and archive search Mailing list archives Mailing lists CVS Primary DNS for shorewall.net I will start the rebuild on Saturday morning and hope to be done by Saturday

This release just rolls up the fixes for the few problems that have surfaced in the first two to three weeks of Shorewall 2.2 availability. If 2.2.0 is working ok for you, there is no reason to upgrade. So far I''ve been very pleased with the stability of the 2.2 release and attribute much of that to the new release model. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.1

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

I have just uploaded a new version of the 2.0.2b .lrp: http://shorewall.net/pub/shorewall/shorewall-2.0.2b/shorwall-2.0.2b.lrp ftp://shorewall.net/pub/shorewall/shorewall-2.0.2b/shorwall-2.0.2b.lrp This version already includes the normal LEAF changes that are present in the shorewall.lrp distributed with Bering and Bering-uClibc. Thanks to K.-P. Kirchdörfer, future versions of the .lrp will

Today I am having a new DSL line installed. Once the line is in and operational, I will be moving my local network from the old line to the new; I am expecting minimal down time (an hour or two) but as those of you who have been involved in such things know, there is no way of knowing what disasters are going to happen. Services impacted will be: http://shorewall.net (a.k.a.,

The 2.0.2 .lrp released yesterday contained the wrong version of /usr/share/shorewall/functions. I have updated the .lrp with the correct version of the functions file. [root@lists shorewall-2.0.2]# ls -l shorwall-2.0.2.lrp -rw-r--r-- 1 root ftp 78325 May 14 06:28 shorwall-2.0.2.lrp [root@lists shorewall-2.0.2]# grep shorwall 2.0.2.md5sums 3ae771fcbfe217006e88e69a597c6455

Content is the same as RC2. http://shorewall.net/pub/shorewall/shorewall-2.0.3 ftp://shorewall.net/pub/shorewall/shorewall-2.0.3 The release will be coming to a mirror near you shortly. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The packages that I uploaded earlier were unfortunately incorrect. I have uploaded the correct packages. The incorrect md5sums are: 14e8f2bfa08cc5ca2715c8b1179d5eb2 shorewall-2.0.10-1.noarch.rpm 54bcbb2216ad3db9870507cd9716fd99 shorewall-2.0.10.tgz c2fe0acc7f056acb56d089cf8dafa39a shorwall-2.0.10.lrp The correct md5sums are:

Thank you for your valuable help, Tom and sorry to ruin a Friday night, the 13th -:) It worked. And I must have been high last nite and done something wrong to shutdown VPN. Anyway I now have all my_files as I want and everything works perfectly. Cheers and have a very nice weekend. M Lu. >From: Tom Eastep <teastep@shorewall.net> >To: M Lu <mlu919@hotmail.com> >CC:

Shorewall 1.4.0 is released and is available at both SourceForge and at the mirror in Washington State. Other mirrors will be updated shortly. The content of 1.4.0 is the same as 1.4.0-RC3 with the exception of the updated version number. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.sf.net Washington USA \ teastep@shorewall.net

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

Rather than have lots of folks downloading a version with a broken ''check'' command, I''ve released 1.4.1a that corrects the problem. Sorry for the back-to-back releases today... -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.sf.net Washington USA \ teastep@shorewall.net

I anticipate that this will be the last RC unless problems are discovered. Changes since RC2 include: * The default route is now ignored when Shorewall is detecting masqueraded networks. A warning message is issued if the default route goes through the source interface (normally, the destination interface is the firewall''s external interface and therefore, the default route would go

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