similar to: More about Upgrade Issues

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

The current thread on the User''s List entitled "Multi-ISP in 2.4.0" includes the following tcrules file: ############################################################################ ## #MARK SOURCE DEST PROTO PORT(S) CLIENT USER TEST # PORT(S) 201:P eth2 ppp1

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

--On Friday, January 24, 2003 1:59 PM -0700 Steve Fink <stevef@netvantix.com> wrote: > On Fri, 2003-01-24 at 08:31, Tom Eastep wrote: >> >> >> --On Friday, January 24, 2003 8:20 AM -0700 Steve Fink >>> <stevef@netvantix.com> wrote: >>> >>> http://leaf.netvantix.com/012303/swstatus.txt >>> >> >> It looks like your

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

Shorewall 1.3.14 is now available. Thanks go to Francesca Smith for helping with updating the sample configurations. New in 1.3.14: 1) An OLD_PING_HANDLING option has been added to shorewall.conf. When set to Yes, Shorewall ping handling is as it has always been (see http://www.shorewall.net/ping.html). When OLD_PING_HANDLING=No, icmp echo (ping) is handled via rules and

Beta 1 is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta Features include: 1) An OLD_PING_HANDLING option has been added to shorewall.conf. When set to Yes, Shorewall ping handling is as it has always been (see http://www.shorewall.net/ping.html). When OLD_PING_HANDLING=No, icmp echo (ping) is handled via rules and

This morning as I was reviewing the changes occuring between 1.3.12 and 1.3.14, I noticed that I had neglected to document one new feature included in 1.3.14. In /etc/shorewall/tcrules, the MARK value may be optionally followed by ":" and either ''F'' or ''P'' to designate that the marking will occur in the FORWARD or PREROUTING chains respectively.

A new rfc1918 file that reflects the recent IANA allocation of 222/8 and 223/8 may be found at: http://www.shorwall.net/pub/shorewall/errata/1.3.14/rfc1918 ftp://ftp.shorewall.net/pub/shorewall/errata/1.3.14/rfc1918 -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net

--On Monday, February 24, 2003 11:55:48 AM -0700 Mike Robinson <miker@sundialservices.com> wrote: > > I''ll stick with my original suggestion, and consider it very important. > Even though users might say "why isn''t blah-blah in the services-file," > once the data was supplied in the file and distributed, no one would > have to repeat the

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:

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

The first 1.4.0 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 MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4 behavior is the same as 1.3 with MERGE_HOSTS=Yes. 2. Interface names of the form

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

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

FYI This bug will prevent ''shorewall restore'' from working if you have "!<single IP address>" in the ORIGINAL DEST column. -Tom ---------- Forwarded Message ---------- Subject: [PATCH] Another iptables-save buglet Date: Wednesday 14 September 2005 15:09 From: Tom Eastep <teastep@shorewall.net> To: netfilter-devel@lists.netfilter.org The conntrack

Hiya, My two cents here .. I use a locked down Linux Sendmail relay (use sendmail null-client feature on any spare old server or PC) in my DMZ to relay Mail to the exchange server in my local zone. Its sort of the moat you have to cross over to get at the castle walls and the hot oil dumped on your head approach. Francesca C. Smith Lady Linux Internet Services 1801 Bolton Street # 1 Baltimore,

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

Thanks to Francesca Smith, the sample configurations have been undated for 1.4.0 and are now available at: http://www.shorewall.net/pub/shorewall/Beta/Samples Thanks Francecsa!! -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net

And Andrew -- PLEASE don''t reply off-list. I''m not a private help desk... -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net ---------- Forwarded message ---------- Date: Mon, 25 Aug 2003 19:01:34 -0700 (Pacific Daylight Time) From: Tom Eastep <teastep@shorewall.net> To: andrew