similar to: Thank You

I have been overwhelmed today with well-wishing posts. I began by trying to answering each and every one but I soon realized that there were going to be too many. So I want to thank each of you who offered me your best wishes -- I fully appreciate every post. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \

The Shorewall support page advocates including the output of "shorewall status" with problem reports that involve some sort of connection problem. I suspect that the number of people who feel comfortable analyzing problems through use this output is small. To help, I''ve created http://shorewall.net/AnalyzingShorewallStatus.html I suspect that the document isn''t

Hi, thanks for a great piece of software! ...at the moment I have a commercial VPN box, which also acts as our firewall. I wish to replace this firewall functionality with a decicated Shorewall firewall, and use the VPN box only for VPN traffic. At the moment, this VPN/Firewall box is at an internet visible address, x.x.x.85 I wish to make the new Shorewall fireall x.x.x.85 and move the VPN to

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

It is my plan that the upcoming release of Shorewall (1.3.14) will definitely be the last of the 1.3.x releases and will very probably be the last release of Shorewall 1.x.x. I will continue to support Shorewall 1.3 but will be making no more enhancements to it. I will be devoting my time to Shorewall 2. If anyone is interested in taking over the development of Shorewall 1, please let me

Just some stuff that was laying around in CVS: 1. Added ''DNAT-'' target. 2. Print policies in ''check'' command. 3. Added CLEAR_TC option. 4. Added SHARED_DIR option. [teastep@wookie Shorewall]$ cat releasenotes.txt This is a minor release of Shorewall that has a couple of new features. New features include: 1) A new ''DNAT-'' action has been

Dear Shorewall developers, Thanks very much for shorewall! I''ve been using Shorewall as distributed with Debian GNU/Linux (Woody) for a while on a few firewalls I manage and found it extremely easy to install, setup and use. I liked the nice and easy to understand design of the whole package, the documentation, well documented config files and how well it runs. I just thought

Tom, I am NOT subscribed (yet). I dropped SuSeFirewall2 in favor of shorewall to get past the configuration hurdles I as experiencing. At the moment, when my SuSe 9.1 starts up, I can see shorewall processing the rules, policies, etc. and I see no errors and then moves on with the rest of the SuSe boot process . However, no traffic passes through using the rules. I run an iptables -L and I

The kernel module loading fix included in Shorewall 2.0.2d fails to load modules when MODULE_SUFFIX is not set in shorewall.conf. There are three possible ways to avoid this problem: a) Set MODULE_SUFFIX="o gz ko o.gz ko.gz" is shorewall.conf. b) Install the ''firewall'' script from the 2.0.2 errata: http://shorewall.net/pub/shorewall/errata/2.0.2/firewall

Hi Tom, Many thanks for that, that''s really helped. Netfilter is indeed dropping the packets as invalid. Thanks and regards, Frances -----Original Message----- From: Tom Eastep [mailto:teastep@shorewall.net] Sent: 23 March 2007 18:05 To: Shorewall Users Subject: Re: [Shorewall-users] Expected handling of [SYN] when expecting[SYN, ACK]? Frances Flood wrote: > Basically, if the

John, I''m taking the liberty of copying the Shorwall Development list since I believe that these issues will be of interest. On Tue, 6 Aug 2002, Links at Momsview wrote: > Tom, > I''m not sure if you ever saw this document but it describes some of the > reasons you are seeing strange packets > after setting up NEW not SYN >

I''ve established a web site (http://wookie.shorewall.net) where you can see the changes that I''m making to the documentation for the upcoming release (currently 1.3.4). Since Ron has been tied up with other projects, I''ve taken a hack at rewriting the Quick Start Guide. It''s been broken into three separate guides as several people suggested and the two- and

As most of you already know, I have decided to terminate my involvement with the Shorewall project. Many of you have written to me expressing concern about the future of Shorewall and some of you have offered to help in various ways. I''m sending this post to assure you that Shorewall is not going away and that capable people are commited to ensuring that Shorewall continues. Paul Gear

Please subscribe to the development list or to the leaf development list . That way, all interested parties will know what is happening. Thanks to you all for the offers of help, -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

Hi all, I''m working on a patch for shorewall to make it run with a Crossbeam X40 machine (www.crossbeamsystems.com) and I would like to know where to send it, is this list the correct location?. The patch is necesary because of Crossbeam X series running mode: when you make a shorewall start, restart or clear, there are a packet dropping until shorewall is Started or cleaned. At

http://www.shorewall.net/pub/shorewall/Beta ftp://www.shorewall.net/pub/shorewall/Beta Thanks to Lorenzo Martignoni, there is a .deb in this Beta (I''m running it here!) RC1 will be next... -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Hi Folks, I''m a new user to Shorewall, it came installed on the redWall firewall that I am using and I''m really happy with both projects! Thanks for all your work on it! I have a question about tcrules and $FW. I''m doing source policy routing and need to be able to add an output rule to the mangle chain with a source that is specific network, not 0.0.0.0/0. It

Hi all, I some vlan routing problem, I''m using a linux box with an 8021q kernel. I have connect eth2 ethernet controller from linux box to a switch port that carry for vlan tagged as 2 3 4 5, I''m able to connect to the internet from vlan but not to route traffic between vlan, this is the output of ifconfig -a: eth0 Link encap:Ethernet HWaddr 00:A0:24:50:E5:B2

http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta Problems corrected since RC1: 1) The documentation of the USERSETS column in the rules file has been corrected. 2) If there is no policy defined for the zones specified in a rule, the firewall script previously encountered a shell syntax error: [: NONE: unexpected operator Now, the absence of a

Until further notice, I will not be involved in Shorewall development or support. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.sf.net Washington USA \ teastep@shorewall.net