Displaying 20 results from an estimated 20000 matches similar to: "Re: shorewall.conf note"
2003 Jul 21
0
Shorewall 1.4.6
Shorewall 1.4.6 is now available. Thanks to Francesca Smith, the 1.4.6
Sample configurations are also available.
The release is currently available at:
http://shorewall.net/pub/shorewall
ftp://shorewall.net/pub/shorewall
It will be available at the other mirrors shortly.
This is a minor release of Shorewall.
Problems Corrected:
1) A problem seen on RH7.3 systems where Shorewall encountered
2002 May 14
3
[Shorewall-users] Redirect loc::80 to fw::3128 not work (fwd)
I''m beginning to believe that the use of the last column in the rules file
to designate redirection/forwarding is too subtle for many users. For 1.3,
I think I''ll do something like the following:
Current rule:
ACCEPT net loc:192.168.1.3 tcp 80 - all
New rule:
FORWARD net loc:192.168.1.3 tcp 80
Current rule:
ACCEPT net fw::3128 tcp 80 - all
New rule:
REDIRECT net
2003 Aug 05
4
Shorewall 1.4.6b
This is a bug-fix roll-up.
Problems corrected since 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 "shorewall stop" command is now disabled when
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
2004 Sep 20
3
Possible bug in shorewall 2.0.8
Hello,
I believe there may be a bug in shorewall version 2.0.8. I''ve been using
shorewall for years without problems (last installed version was 1.4.6b-1).
I''ve posted previously with the subject line "After upgrade people can no
longer connect" dated on Sunday, September 19, 2004 which contains all the
information for the upgrade.
Today I uninstalled shorewall
2004 Dec 15
3
Newbie: Problem with two-interface setup
Hi
I have a problem with Shorewall on my two-interface connection. I run
Debian unstable. The setup looks like this:
Internet -------- router ------- server
213.237.12.137 192.168.1.3 192.168.1.2
192.168.0.7 --- local net
192.168.0.{...}
I can ping the server from the local net, and the local net from the
2004 Apr 16
0
Shorewall 2.0 French Language Guides available
Thanks to Fabien Demassieux, French Language versions of the QuickStart
Guides and the Setup Guide are now available:
http://shorewall.net/shorewall_quickstart_guide.htm
http://shorewall.sf.net/shorewall_quickstart_guide.htm
These guides will be available shortly on the other Shorwall Mirrors
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \
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
2002 May 14
4
Redirect loc::80 to fw::3128 not work
The rule:
ACCEPT loc $FW::3128 tcp www
doesn''t work propertly, the http access does not redirect
to squid but directly exit.
what''s wrong?
Thanks
-------
Dario Lesca (d.lesca@ivrea.osra.it)
--------------------------------------
@@@@@@@ this is my shorewall-1.2.13 config:
#[/etc/shorewall/common.def]-----------------------------------------------
2003 Jul 31
0
Snapshot 1.4.6_20030731
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.
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
2002 Sep 29
3
Shorewall 1.3.9
Shorewall 1.3.9 is available.
In this release:
1. DNS Names are now allowed in Shorewall config files (I still recommend
against using them however).
2. The connection SOURCE may now be qualified by both interface
and IP address in a Shorewall rule.
3. Shorewall startup is now disabled after initial installation until
the file /etc/shorewall/startup_disabled is removed.
4. The
2004 Aug 28
0
Shorewall 2.1.7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In this release:
1) Dynamic Ipsec Zones now work.
2) Output Traffic Accounting by user/group is supported (thanks to
Tuomas Jormola).
3) The following negative test options are added in /etc/shorewall/ipsec
and /etc/shorewall/masq:
reqid!=<number>
spi!=<number>
proto!=esp|ah|ipcomp
mode!=tunnel|transport
2003 Aug 09
0
Snapshot 20030809
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)
2003 Feb 12
0
[Fwd: Re: Shorewall and webmin, partialy solved !]
> One thing : the shorewall is not starting at boot, how to do it ?
Did you remove the "startup_disabled" file from the /etc/shorewall
directory?
yes, thsi file was removed ...
F?bio Rabelo
2004 Oct 25
0
Shorewall 2.0.10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.10
ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.10
Nothing Earth-shattering here and there is no reason to upgrade if you
are not seeing one of the corrected problems.
- -----------------------------------------------------------------------
Problems corrected in version 2.0.10
1) The
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 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
2003 Jan 15
2
pppoe and /etc/shorewall/interfaces
I am a newbie to linux and shorewall. I am reading the shoreall
quickstart guides. I am a bit confused about the following statement:
----------- quote --------------
The firewall has two network interfaces. Where Internet connectivity
is through a cable or DSL "Modem", the External Interface will be the
ethernet adapter that is connected to that "Modem" (e.g., eth0)
unless you
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