similar to: Shorewall 2.0.2 Beta2

Shoot! Sorry Tom. I thought I replaced your e-mail address with the shorewall list address. I got it working!!! I finally figured out what I was doing wrong. Pays to write down what I want to accomplish versus flying by the seat mof my pants. The ACCEPT+ is G R E A T! Took care of some of my issues along with removing the redirect rule (yeah, yeah...I should have thought it over more

Shorewall 4.0.15 is now available from shorewall.net, SourceForge and Debian Sid. Additionally, I have updated my Debian Etch repository with 4.0.15 packages. Problems Corrected in Shorewall 4.0.15. 1) Beginning with iptables version 1.4.1, the syntax for commands using the conntrack module has changed. Shorewall now detects if the installed version of iptables requires the new

http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta Please read the release notes carefully -- there are significant differences between Beta1 and Beta2. If you are running Beta1, you will need to remove the INCLUDE from your /etc/shorewall/actions file (that I instructed you to add last time -- I know; I lied). -Tom -- Tom Eastep \ Nothing is foolproof to a

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:

Shorewall 2.2.0 is expected to be released in the February/March timeframe so it is now time to begin thinking about preparing to upgrade. This is particularly important for those of you still running Shorewall 1.4 since support for that version will end with the release of 2.2. For those of you still running Shorewall 1.4, here are some things that you can do ahead of time to ease the upgrade to

This update is only of interest to those of you using Dynamic Zones. Previously, the source interface was not included in the ''nat'' table rule generated from DNAT rules when the rule was applied. The bug usually didn''t have any observable effect other than to slow down all connection requests in the case where Dynamic zones are used with DNAT rules. -Tom -- Tom

Shorewall 2.0.0 is now in Beta so this is a good time to begin thinking about preparing to migrate to the 2.0 Shorewall series. Shorewall 2.0 makes a number of incompatible changes in the configuration files. Luckily, you will be able to make changes ahead of time to your 1.4 configuration that will ease the migration when the time comes. a) Shorewall 2.0 doesn''t allow you to specify

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

Shorewall 2.2.0 is expected to be released in the February/March timeframe so it is now time to begin thinking about preparing to upgrade. This is particularly important for those of you still running Shorewall 1.4 since support for that version will end with the release of 2.2. For those of you still running Shorewall 1.4, here are some things that you can do ahead of time to ease the upgrade to

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

Yes thank you for answering so fast ! I have corrected it, here the new diagram and the new routing table. But it still doesn''t work. >From the router i can access to 192.168.11.254 I have add the rules : DNAT loc priv:192.168.11.254:22 tcp 22 But i can''t connect to 192.168.11.254 from LAN The DNAT fonction doesn''t work, but i can DROP packet arriving on eth0 (loc)

Sorry some email problem, i have change it for more reliable one. I have try this morning to netmasq 192.168.11.0 (eth1) to 192.168.1.0 (eth0), but it is a mistake. Yes thank you for answering so fast ! I have corrected it, here the new diagram and the new routing table. But it still doesn''t work. From the router i can access to 192.168.11.254 I have add the rules : DNAT loc

"Dark Ryder" has reported a bug in Shorewall 1.4.7; this bug is also present in Shorewall 1.4.8. The effect of the bug is that in DNAT rules that specify SNAT, the SNAT address can be effectively ignored in some cases. I have created corrected versions of the ''firewall'' script for both 1.4.7 (based on 1.4.7c) and 1.4.8; these corrections may be downloaded from the

http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta This is Beta 1 with the following Changes: a) The fix for SNAT in DNAT rules has been included. b) An updated rfc1918 file is included. c) The documentation is no longer part of the base release. Stay tuned for announcements on how the documentation is going to be released. -Tom -- Tom Eastep \ Nothing is

http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.4 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.4 Problems Corrected: 1. The error message: Error: No appropriate chain for zone <z1> to zone <z2> has been changed to one that is more self-explanatory: Error: No policy defined for zone <z1> to zone <z2> 2. When only an

Shorewall 2.0.2 is now available at: http://shorewall.net/pub/shorewall/shorewall-2.0.2 ftp://shorewall.net/pub/shorewall/shorewall.2.0.2 -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

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 \

On Tue, 2003-10-28 at 13:41, AdStar wrote: > Hi Tom, > > I''ve upgraded my firewall to 1.4.7c (and copied the firewall/functions from > the CVS over for the accounting names) > > I still get this reject in my logs. > Oct 29 08:35:08 pyro Shorewall:FORWARD:REJECT: IN=eth1 OUT=eth1 > MAC=00:02:b3:61:64:6e:00:02:b3:5f:c3:5c:08:00 SRC=10.0.100.11 DST=10.0.100.10 >

Shorewall 1.4.7 is now available at: http://shorewall.net/pub/shorewall/shorewall-1.4.7 ftp://shorewall.net/pub/shorewall/shorewall-1.4.7 It will be available at your favorite mirror shortly. The release notes are attached. As always, many thanks go to Francesca Smith for updating the sample configurations for this release. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently