similar to: Shorewall 2.2.1

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC3 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC3 Just a few bug fixes: * The following error message could appear during "shorewall stop" clear": local: lo:: bad variable name * * The rate limiting example in /etc/shorewall/rules has been changed to use the RATE

http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.3 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.3 Problems Corrected: 1) If a zone is defined in /etc/shorewall/hosts using <interface>:!<network> in the HOSTS column then startup errors occur on "shorewall [re]start". 2) Previously, if "shorewall status" was run on a system whose kernel lacked

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 --

This release back-ports the DROPINVALID shorewall.conf option from 2.2.0. 1) 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. The new kernel code can be disabled by including this command in your /etc/shorewall/init file: echo 1

Note: Because of the short time that has elapsed since the release of Shorewall 2.2.0, Shorewall 2.0 will be supported until 1 December 2005 or until the release of Shorewall 2.6.0, whichever occurs first. http://shorewall.net/pub/shorewall/2.4/shorewall-2.4.0 ftp://shorewall.net/pub/shorewall/2.4/shorewall-2.4.0 -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool

This will be my last 2.2 release. It contains a couple of small bug fixes that I had laying around. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.5 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.5 1) Previously, if PKTTYPE=No in shorewall.conf then pkttype match would still be used if the kernel supported it. 2) A typo in the ''tunnel'' script has been corrected

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

-----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

http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.14 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.14 New Features: 1. Previously, when rate-limiting was specified in /etc/shorewall/policy (LIMIT:BURST column), any traffic which exceeded the specified rate was silently dropped. Now, if a log level is given in the entry (LEVEL column) then drops are logged

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.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adem has contributed a nice IP Subnet chart which I''ve placed at http://shorewall.net/pub/shorewall/contrib/IPSubNetMask.html Thanks Adem! - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \

Dear Shorewall Users, having noticed that the request for a WebGUI is growing, after a very short conversation I''ve had with Tom, I''d like to let you all evaluate the Web interface to Shorewall I''ve written, integrating the original weblet package made available for the LRP project. ---------------------------------------------------------------------------- Preamble

http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.4 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.4 Problems Corrected: 1. The error message: Error: No appropriate chain for zone <z1> to zone <z2> has been changed to one that is more self-explanatory: Error: No policy defined for zone <z1> to zone <z2> 2. When only an

On Tue, 2004-11-30 at 12:17 +0700, Matthew Hodgett wrote: > > As for the 169.254 issue I tried to search the archives but got nothing. > I then tried to search on generic words, nothing. I then tried some > really common words like ''help'', ''initiated'', ''masq'' - nothing. I think > the index might be corrupt because I get no

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

This minor release includes some bugfix back-ports from 2.2. 1) Invoking the ''rejNotSyn'' action results in an error at startup. 2) The UDP and TCP port numbers in /usr/share/shorewall/action.AllowPCA were reversed. 3) If a zone is defined in /etc/shorewall/hosts using <interface>:!<network> in the HOSTS column then startup errors occur on "shorewall

http://shorewall.net/pub/shorewall/2.3/shorewall-2.3.0 ftp://shorewall.net/pub/shorewall/2.3/shorewall-2.3.0 WARNING: This is a development release and may be unstable New Features in version 2.3.0 1) Shorewall 2.3.0 supports the ''cmd-owner'' option of the owner match facility in Netfilter. Like all owner match options, ''cmd-owner'' may only be applied to

--On Wednesday, January 15, 2003 8:57 AM +0000 Julian Church <jc@ljchurch.co.uk> wrote: > Tom > > There''s no reason you should let a complete stranger question your better > judgement, but weren''t you supposed to be taking a break from all of this? > The problem I am having is "Now what do I do with myself in the early mornings and evenings?":

On Tue, 2004-11-30 at 12:17 +0700, Matthew Hodgett wrote: > > As for the 169.254 issue I tried to search the archives but got nothing. > I then tried to search on generic words, nothing. I then tried some > really common words like ''help'', ''initiated'', ''masq'' - nothing. I think > the index might be corrupt because I get no

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,