similar to: Shorewall 2.0.8 (Stable Release)

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.1/shorewall-2.1.10 ftp://shorewall.net/pub/shorewall/2.1/shorewall-2.1.10 New Features: 1) Using the default LOGFORMAT, chain names longer than 11 characters (such as in user-defined actions) may result in log prefix truncation. A new shorewall.conf action LOGTAGONLY has been added to deal with this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.1/shorewall-2.1.8 ftp://shorewall.net/pub/shorewall/2.1/shorewall-2.1.8 New in this release: 1) Shorewall now verifies that your kernel and iptables have physdev ~ match support if BRIDGING=Yes in shorewall.conf. 2) Beginning with this release, if your kernel and iptables have ~ iprange match support

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.1/shorewall-2.1.9 ftp://shorewall.net/pub/shorewall/2.1/shorewall-2.1.9 Problems Corrected: 1) IP ranges in the routestopped and tunnels files now work. 2) Rules where an IP range appears in both the source and destination ~ now work correctly. 3) With complex proxy arp configurations involving two or

-----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.0/shorewall-2.0.10 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.10 Nothing Earth-shattering here and there is no reason to upgrade if you are not seeing one of the corrected problems. - ----------------------------------------------------------------------- Problems corrected in version 2.0.10 1) The

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Problems Corrected in version 2.0.9 1) Previously, an empty PROTO column or a value of "all" in that column would cause errors when processing the /etc/shorewall/tcrules file. New Features in version 2.0.9 1) The "shorewall status" command now includes the output of "brctl show" if the bridge tools are installed.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.1/shorewall-2.1.5 ftp://shorewall.net/pub/shorewall/2.1/shorewall-2.1.5 This completes the implementation of Kernel 2.6 IPSEC support in Shorewall. Documentation is still minimal -- see the releasenotes and http://shorewall.net/IPSEC-2.6.html - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 An updated bogons file is available at: http://shorewall.net/pub/shorewall/errata/2.0.8/bogons ftp://shorewall.net/pub/shorewall/errata/2.0.8/bogons Thanks to Lorenzo Martignoni for bringing the resent IANA allocations to my attention. - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The initial file that I uploaded was incorrect. If you downloaded a file that still contains 72.0.0.0/8 then please download again. Sorry for the confusion. An updated bogons file is available at: http://shorewall.net/pub/shorewall/errata/2.0.8/bogons ftp://shorewall.net/pub/shorewall/errata/2.0.8/bogons Thanks to Lorenzo Martignoni for bringing

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.1/shorewall-2.1.4 ftp://shorewall.net/pub/shorewall/2.1/shorewall-2.1.4 Contains improvements to the support for kernel 2.6 IPSEC. Warning: The Netfilter IPSEC changes that this version of Shorewall depends on do not appear to work properly with bridging. I therefore recommend that you not try ipsec to/from a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://shorewall.net/pub/shorewall/2.1/shorewall-2.1.6 ftp://shorewall.net/pub/shorewall/2.1/shorewall-2.1.6 I discovered that some of the policy options such as ''spi'' and ''tunnel-src/dst'' must be specified separately for input and output. I''ve added a couple of more columns to /etc/shorewall/masq. - -Tom

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:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am forwarding your post to the Debian Shorewall maintainer -- none of the code involved in Shorewall startup under Debian is part of the standard Shorewall distribution. - -Tom - -------- Original Message -------- Subject: [Shorewall-users] Problems with Firewall start at Boot time Date: Mon, 06 Sep 2004 16:48:16 -0400 From: Stewart Outram

Thanks for such a quick reply Tom! Any suggestions then as to what I might do other than putting a second nic in the SBS and opening it up for web access? I don''t like the idea, but since MS SBS includes fireall that is actually what MS suggests. Boyd -----Original Message----- From: Tom Eastep [mailto:teastep@shorewall.net] Sent: January 3, 2005 3:05 PM To: Shorewall Users Cc: Boyd

FYI -- A small blurb on page 45. -------- Original Message -------- Subject: Shorewall in (IN)SECURE Magazine Date: Tue, 16 Aug 2005 00:10:51 +0200 From: Mirko Zorz <mirko.zorz@net-security.org> To: teastep@shorewall.net Hello Tom, I thought you would be interested to know that Shorewall has been featured in the Software Spotlight section of the third issue of (IN)SECURE, a free security

Alex Martin has completed installation of a new server in the San Jose area and we''ve switched the DNS CNAME records for www.shorewall.net and ftp.shorewall.net to point to that new server. Please let us know if there are problems. My personal thanks go to Alex for his continuing contribution to Shorewall. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool

Carl Raeside wrote: > Tom, > > How is it going? Quick questions. > > 1. the link to the Mandrake rpms seems to not have the shorewall rpm in > it. http://www.monkeynoodle.org/comp/net/shorewall/ > > 2. this link seems to be dead any other sources ? Iproute ? > > Iproute ("ip" utility). The iproute package is included with most > distributions