similar to: Re: Shorewall / Mandriva

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

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

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:

Hi Tom and folks, Mandriva is shipping shorewall in its main distribution for some time now. It is built on a custom .spec, but I keep it in sync with latest versions of shorewall package. I heard that there were some issues with Mandriva''s package of shorewall, but it was before I started working on it, and the guys that were maintaining it before are no longer working on it.

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

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

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 \

Magnus Hyllander wrote: > > I guess what I''m wondering is, how does Shorewall (netfilter) know which > zone a certain road warrior belongs to? I''ve just completed getting dynamic zones working with ipsec again. A dynamic IPSEC zone is defined in /etc/shorewall/zones by following the short name (first column) with ":ipsec". The code is in CVS. There are a

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

I''ve opened the Shorewall 2.3 thread in the Shorewall2/ CVS project. The config files all show version 2.4 -- that saves me having to edit each one of them again when I move from 2.3->2.4. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \

http://shorewall.net/pub/shorewall/2.4/shorewall-2.4.0-RC2 ftp://shorewall.net/pub/shorewall/2.4/shorewall-2.4.0-RC2 The release notes are in the download directory. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key

The following is taken from the Release notes for 2.2.3 (which will be released in a month or so). 2) There has been ongoing confusion about how the /etc/shorewall/routestopped file works. People understand how it works with the ''shorewall stop'' command but when they read that ''shorewall restart'' is logically equivalent to ''shorewall

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

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