Displaying 20 results from an estimated 20000 matches similar to: "Re: Shorewall in print"
2005 Aug 15
0
[Fwd: Shorewall in (IN)SECURE Magazine]
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
2004 Sep 23
0
Fwd: RE: 2.6 kernel ipsec and shorewall
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
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:
2004 Nov 02
0
Shorewall 2.2.0 Beta 2
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
2004 Nov 02
3
Shorewall 2.2.0 Beta 2
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
2005 Jan 03
1
RE: Outlook Web Access behind shorewall firewalldoesn''t work
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
2005 Mar 30
1
RE: Shorewall and an inline IDS(snort-inlineorhogwash)
Plus I would like to let you know that it works like a charm.
Snort can now see those packets.
-----Original Message-----
From: shorewall-users-bounces@lists.shorewall.net
[mailto:shorewall-users-bounces@lists.shorewall.net] On Behalf Of
Thibodeau, Jamie L.
Sent: Wednesday, March 30, 2005 9:25 AM
To: Mailing List for Shorewall Users
Subject: RE: [Shorewall-users] Shorewall and an inline
2003 Feb 24
0
RE: Shorewall-users Digest, Vol 3, Issue 64
Did I just read completely past this or is this an undocumented feature?
Either way, thanks.
BTW for my first attempt at a Linux firewall, this proved to be a challenge,
but worth it. And most of the problems I''ve had are I/O (idiot operator)
errors. Keep up the good work.
Kev
---
Message: 10
Date: Mon, 24 Feb 2003 06:20:00 -0800
From: Tom Eastep <teastep@shorewall.net>
Subject:
2003 Jan 29
0
shorewall on gibraltar (fwd)
------------ Forwarded Message ------------
Date: Wednesday, January 29, 2003 9:27 AM +0100
From: Matthias Klose <doko@cs.tu-berlin.de>
To: Tom Eastep <teastep@shorewall.net>
Subject: shorewall on gibraltar
Just a note, that gibraltar (www.gibraltar.at) now includes shorewall
as an option (currently an 1.3.12 version).
Gibraltar is a project that aims to produce a Debian
2012 Dec 29
0
Shorewall Project Upgraded to Allura
The Shorewall project at sourceforge has been upgraded to Allura.
If you have a copy of the git repository, you need to check out a fresh
copy from the new locations:
git clone ssh://teastep@git.code.sf.net/p/shorewall/code shorewall
git clone ssh://teastep@git.code.sf.net/p/shorewall/release release
git clone ssh://teastep@git.code.sf.net/p/shorewall/tools tools
git clone
2005 Mar 30
1
RE: Shorewall and an inline IDS (snort-inlineorhogwash)
You are awesome!!!!
-----Original Message-----
From: shorewall-users-bounces@lists.shorewall.net
[mailto:shorewall-users-bounces@lists.shorewall.net] On Behalf Of Tom
Eastep
Sent: Wednesday, March 30, 2005 9:11 AM
To: Mailing List for Shorewall Users
Subject: Re: [Shorewall-users] Shorewall and an inline IDS
(snort-inlineorhogwash)
Tom Eastep wrote:
> Thibodeau, Jamie L. wrote:
>
2005 Mar 14
0
New Home for www.shorewall.net/ftp.shorewall.net
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
2005 Mar 22
0
Re: [Shorewall-devel] Shorewall
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
2007 May 16
1
www.shorewall.net/ftp.shorewall.net is down
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 \
2004 Dec 05
0
Shorewall 2.2.0 Beta 7
http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta7
ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta7
Problems Corrected:
1. The "shorewall add" and "shorewall delete" commands now work in
a bridged environment. The syntax is:
shorewall add <interface>[:<port>]:<address> <zone>
2005 Mar 12
0
Shorewall 2.2.2
Shorewall 2.2.2 is now available.
http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.2
ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.2
Problems Corrected:
1. The SOURCE column in the /etc/shorewall/tcrules file now correctly
allows IP ranges (assuming that your iptables and kernel support
ranges).
2. If A is a user-defined action and you have file /etc/shorewall/A
2004 Dec 01
0
Shorewall 2.0.12
This update will be of interest to you if you use dynamic zones or if
you have an /etc/shorewall/start file and use the ''save'' command.
http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.12
ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.12
Problems Corrected:
1. A typo in shorewall.conf (NETNOTSYN) has been corrected.
2. The "shorewall add" and
2005 Jan 15
2
Re: Shorewall - Bridging with Gentoo
Joshua Schmidlkofer wrote:
> Tom Eastep wrote:
>
>> Joshua Schmidlkofer wrote:
>>
>>> Tom,
>>>
>>> Here is the setup method w/ Bridging on Gentoo.
>>>
>>
>> Thanks, Joshua
>>
>> -Tom
>
>
> Off topic - Has anyone cooked up a good web front end? I am messing w/
> IPCop, because one of my clients uses it.
2006 Dec 28
0
Shorewall 3.4.0 Beta 1
I''m pleased to announce that Shorewall 3.4.0 Beta 1 is available at
ftp://shorewall.net/pub/shorewall/development/3.4/shorewall-3.4.0-Beta1 and at
mirror sites world wide.
The release notes can be viewed at
ftp://shorewall.net/pub/shorewall/development/3.4/shorewall-3.4.0-Beta1/releasenotes.txt
Release Highlights
1) Shorewall can now be taylored to reduce its footprint on embedded
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