similar to: Shorewall 1.4.3a

This is a minor release of Shorewall. Problems Corrected: 1) TCP connection requests rejected out of the common chain are now properly rejected with TCP RST; previously, some of these requests were rejeced with an ICMP port-unreachable response. 2) ''traceroute -I'' from behind the firewall previously timed out on the first hop (e.g., to the firewall). This has been

Anyone, willing to take a lead on this one, since Tom is taking a rest: " I am hosting all servers by myself. I have five static IP addreses with a DSL line. My DSL router from the ISP provider is configured as bridge, so no traffic is filtered. I checked the logs and getting: Jan 5 23:05:12 gw1 kernel: Shorewall:all2all:REJECT:IN= OUT=eth0 SRC=66.58.99.86 DST=216.35.73.164 LEN=68

The first release candidate is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta The only change between Beta 1 and RC1 is that the ''check'' command is back in RC1. Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4

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

Currently at: http://shorewall.net/pub/shorewall/shorewall-1.4.8 ftp://shorewall.net/pub/shorewall/shorewall-1.4.8 Coming soon to a mirror near you. This is a minor release of Shorewall. Problems Corrected since version 1.4.7: 1) Tuomo Soini has supplied a correction to a problem that occurs using some versions of ''ash''. The symptom is that "shorewall start"

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

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

The second Beta is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta Function from 1.3 that has been omitted from this version includes: 1) The ''check'' command is no longer supported. 2) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4 behavior is the same as 1.3 with MERGE_HOSTS=Yes.

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

Ok -- I''m wearing the brown bag tonight (I''ve airmailed one to Tuomas as well :-) ). The IPTABLES patch had some problems when IPTABLES was not set in /etc/shorewall/shorewall.conf. Beta 6 fixes those (I hope) and also corrects a rather obscure problem with "shorewall add" when the "mss" option appears in /etc/shorewall/ipsec. -Tom -- Tom Eastep \

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

This morning I discovered a problem in the build of 2.0.5 -- the version number in the install.sh, uninstall.sh and fallback.sh script were not updated properly. The result is that "shorewall version" returns "2.0.4" rather than "2.0.5". This problem is present in the .tgz and .rpm files. I''ve replaced the original .tgz and .rpm files with corrected

This version: a) Corrects a missing "#" in the rules file. b) Corrects problems in both "shorewall add" and "shorewall delete". Thanks to Stijn Jonker for finding these problems. c) Provides a way to install on Slackware. Thanks to David Fletcher for his help. http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta -Tom -- Tom Eastep \

I''ve decided to make a late addition to 1.4.0. A number of you have encountered a problem whereby TCP connections could not be established to certain sites. The solution was to turn of Explicit Congestion Notification (ECN -- RFC 3168). I have added a facility whereby ECN may be turned off on a host or network basis. A new /etc/shorewall/ecn file (format is the same as

http://www.shorewall.net/pub/shorewall/3.2/shorewall-3.2.3 ftp://ftp.shorewall.net/pub/shorewall/3.2/shorewall-3.2.3 I''m releasing this now because it corrects a number of important problems. See the attached release notes (both the Shorewall and Shorewall Lite notes are attached). Note: The release notes are compressed so that my total post size is under the list-servers''s

http://www.shorewall.net/pub/shorewall/shorewall-1.4.10d ftp://www.shorewall.net/pub/shorewall/shorewall-1.4.10d This release corrects the problem whereby rules involving user-defined actions often produce a warning. Note that the documentation packages have not been updated for this bugfix release. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \

Srikrishnan, In the future, please post your questions to the mailing list. I''m copying the list with my response so that will appear in the archives. On 5 Apr 2002, Srikrishnan Chitoor wrote: > Hi: > > > I have a setup wherein the main server is running Shorewall and PPTP > Server. The local network is 192.168.1.* and it connects to Internet > using a Static IP

The version of Shorewall in the \Shorewall CVS project has my next attempt at Fireparse integration. a) The LOGMARKER variable is gone and is replaced with LOGFORMAT b) LOGFORMAT contains a printf (1) formatting template that accepts three arguments: 1) The Chain Name 2) The Logging Rule Number within Chain 3) The disposition of the packet (DROP,REJECT,ACCEPT) c) To use Shorewall with

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.1/shorewall-2.1.11 ftp://shorewall.net/pub/shorewall/2.1/shorewall-2.1.11 In addition to correcting several bugs, this version adds the following features: 1) The default Drop and Reject actions now invoke the new standard action ''AllowICMPs''. This new action accepts critical ICMP types:

If you encounter strange problems with 2.1.2 and are using a shell other than bash, you might try installing the ''functions'' file from CVS Shorewall2/. It corrects a problem that I ran into with ''ash''. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net