Displaying 20 results from an estimated 40000 matches similar to: "Shorewall 1.4.5"
2003 Feb 21
0
Shorewall 1.4.0 Beta 1
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
2003 Feb 19
0
Proposed Shorewall 1.4.0 Content
Here is the proposed content -- I''m looking for a Beta to start in the
next week or so with release around the middle of next month. The main
focus of 1.4 will be to provide external behavior similar to the
upcoming 2.0 release.
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
2003 Mar 05
3
Shorewall 1.4.0 RC1
The first release candidate is now available at:
http://www.shorewall.net/pub/shorewall/Beta
ftp://ftp.shorewall.net/pub/shorewall/Beta
The only change between Beta 1 and RC1 is that the ''check'' command is back
in RC1.
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
2005 Mar 15
2
New feature for Shorewall 2.2.3
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
2003 Aug 25
5
Shorewall 1.4.7 Beta 1
http://shorewall.net/pub/shorewall/Beta
ftp://shorewall.net/pub/shorewall/Beta
Problems Corrected since version 1.4.6:
1) Corrected problem in 1.4.6 where the MANGLE_ENABLED variable was
being tested before it was set.
2) Corrected handling of MAC addresses in the SOURCE column of the
tcrules file. Previously, these addresses resulted in an invalid
iptables command.
3) The
2004 Sep 29
0
Re: Shorewall-users Digest, Vol 22, Issue 65
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:
2003 Oct 06
2
Shorewall 1.4.7
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
2002 Jul 16
1
Shorewall 1.3.4
Shorewall 1.3.4 is available:
1. A new /etc/shorewall/routestopped file has been added. This file is
intended to eventually replace the routestopped option in the
/etc/shorewall/interface and /etc/ shorewall/hosts files. This new
file makes remote firewall administration easier by allowing any IP
or subnet to be enabled while Shorewall is stopped.
2. An /etc/shorewall/stopped
2003 Aug 22
0
Snapshot 20030821
http://shorewall.net/pub/shorewall/Snapshots
ftp://shorewall.net/pub/shorewall/Snapshots
Problems Corrected since version 1.4.6:
1) Corrected problem in 1.4.6 where the MANGLE_ENABLED variable was
being tested before it was set.
2) Corrected handling of MAC addresses in the SOURCE column of the
tcrules file. Previously, these addresses resulted in an invalid
iptables command.
3) The
2003 Jan 14
3
Shorewall-1.3.13
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
2003 Aug 13
0
Snapshot 1.4.6 20030813
http://shorewall.net/pub/shorewall/Snapshots
ftp://shorewall.net/pub/shorewall/Snapshots
Release Notes are attached
Changes since last Snapshot:
a) The per-interface dynamic blacklisting chains are now displayed by
"shorewall monitor"
b) IP Traffic Accounting support has been added.
c) Rules may now be rate-limited.
d) Bridge interfaces (br[0-9]) may now appear in entries in the
2004 Nov 04
0
Preparing for Shorewall 2.2
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
2005 Apr 07
4
Shorewall 2.2.3
http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.3
ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.3
Problems Corrected:
1) If a zone is defined in /etc/shorewall/hosts using
<interface>:!<network> in the HOSTS column then startup errors occur
on "shorewall [re]start".
2) Previously, if "shorewall status" was run on a system whose kernel
lacked
2004 Oct 03
1
RE: Shorewall-users Digest, Vol 23, Issue 4
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)
2003 Jan 29
0
Thoughts on Shorewall 2.0
I''ve begun to think about 2.0. I would like to hear any ideas about what
you would like to see included. Before I decide what new things will be
implemented though, I want to nail down what WON''T be included. Here is my
list:
a) Old Ping Handling. There won''t be any ''noping'' or ''forwardping''
interface options and there
2004 Oct 04
1
Shorewall-users Digest, Vol 23, Issue 4
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
2004 Dec 26
1
Preparing for Shorewall 2.2 -- End of Support for Shorewall 1.4 is near!
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
2004 Sep 16
0
Shorewall-2.1.9
-----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
2002 Dec 20
0
Another Beta Patch
--==========1809029384==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
This corrects a more serious problem -- the ''find_hosts_by_option'' routine
was broken which means that ''routestopped'' and ''maclist'' were also broken.
-Tom
--
Tom Eastep \ Shorewall -
2003 Jul 04
3
Shorewall 1.4.6 Beta 1
Beta 1 is now available at:
http://shorewall.net/pub/shorewall/testing
ftp://shorewall.net/pub/shorewall/testing
This is a minor release of Shorewall.
Problems Corrected:
1) A problem seen on RH7.3 systems where Shorewall encountered start
errors when started using the "service" mechanism has been worked
around.
2) Where a list of IP addresses appears in the DEST column of a