Displaying 20 results from an estimated 10000 matches similar to: "Shorewall 2.0.1"
2004 Mar 19
0
Shorewall 2.0.1 Beta 2
http://shorewall.net/pub/shorewall/Beta
ftp://shorewall.net/pub/shorewall/Beta
Fixes a couple of serious bugs in Beta 1 and adds NETMAP support.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
2004 Mar 18
5
Shorewall 2.0.1 Beta 1
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
2005 May 16
1
Interface Broadcast
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I''ve a problem on the broadcast it is adding some additional route to
the router which caused me some problem...
Below is my /etc/shorewall/interface
swtmng1 eth0.1 202.73.10.127 norfc1918
apmng1 eth0.10 202.73.8.7 norfc1918
dist1 eth0.1000 202.73.11.255 norfc1918,nobogons
idc1 eth2.50
2005 May 31
11
More Tests for 2.4.0-RC2 - strange behaviour
Hi all,
I was trying to test ROUTE specific code with a multi-isp serviced box.
There is a bug somewhere, but I''m not able to understand what the real
problem is:
when I issue a "shorewall show capabilities" I get:
Loading /usr/share/shorewall/functions...
Processing /etc/shorewall/params ...
Processing /etc/shorewall/shorewall.conf...
Loading Modules...
Shorewall has
2004 Sep 08
0
Shorewall-2.1.8
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
http://shorewall.net/pub/shorewall/2.1/shorewall-2.1.8
ftp://shorewall.net/pub/shorewall/2.1/shorewall-2.1.8
New in this release:
1) Shorewall now verifies that your kernel and iptables have physdev
~ match support if BRIDGING=Yes in shorewall.conf.
2) Beginning with this release, if your kernel and iptables have
~ iprange match support
2004 Dec 29
1
2 net connections confusion
I''ve been digging around the documentation and seem to have just
confused myself.
Here is what I have on a fedora core 3 machine with 4 network cards (the
built in is dead)
eth2 - connects to the web via dsl-line-1
eth4 - connects to the web via dsl-line-2
eth2 is the route the local network addresses 10.1.x.x connected via
eth0 go out on
eth4 is the route the dmz network addresses
2004 Mar 19
6
Anyone want to test NETMAP?
If you are interested in helping with testing new features, please look
at http://shorewall.net/netmap.html. If you have a need for this type of
network-level address mapping and/or are in a position to test it please
let me know.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
2004 Aug 12
1
SMTP, IP, WHM news problems....
Hi,
I install shorewall firewall on my server and after that I have big
problem with SMTP, I can send messages with outlook to server but that
messages don`t go out from server (Currently I have over 800 messages
in the mail queue)
My server is on WHM/cPanel and EXIM....
When I click on "Delivery Now" for some message in WHM I get error:
Message 1BtoLi-00033G-RN is not frozen
LOG: MAIN
2003 Dec 08
0
Shorewall 1.4.9 Beta1
http://shorewall.net/pub/shorewall/Beta
ftp://shorewall.net/pub/shorewall/Beta
Problems Corrected since version 1.4.8:
1) There has been a low continuing level of confusion over the terms
"Source NAT" (SNAT) and "Static NAT". To avoid future confusion, all
instances of "Static NAT" have been replaced with "One-to-one NAT"
in the documentation and
2004 Jan 15
2
Crypto API and Shorewall
A number of you are flailing around trying to get the subject combination to
work.
You should all be aware that there are parts of this that don''t currently work
and that won''t work well until there are enhancements made to Shorewall (and
probably to Netfilter).
I. There is no clean way currently to support Road Warriors from a
Masquerading Netfilter firewall/gateway. As
2005 Mar 12
1
Shorewall 2.2.2 (Corrected)
I forgot to add the last new feature to the previous announcement.
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.
2004 Apr 02
0
Shorewall 2.0.1-RC5
And the bugs just keep appearing...
FWIW, the changes from 2.0.0 to 2.0.1 are more extensive and more
complex than those between 1.4.10 and 2.0.0.
This RC corrects two problems:
a) The ''routeback'' option in the /etc/shorewall/hosts file had been broken.
b) When two bridge ports were assigned to the same zone, Shorewall did
not create a rule to allow traffic between the
2004 Mar 25
2
Shorewall 2.0.1 RC1
Release candidate 1 is available at:
http://shorewall.net/pub/shorewall/Beta
ftp://shorewall.net/pub/shorewall/Beta
The ''releasenotes.txt'' file tells you about the release.
-Tom
PS to those of you on the Shorewall Announcement List:
Feedback to this point is overwelmingly in favor of keeping Beta and
Release Candidate announcements on this list.
I have configured the list
2006 Apr 02
1
Two ISP
Hello all.
First of all, please be a bit indulgent to my poor English :-).
Second, this message is "kinda" BIG, so if you don''t like BIG
messages, simply don''t read it :-).
I''ve read http://shorewall.net/2.0/Shorewall_and_Routing.html
and http://shorewall.net/MultiISP.html, however I still a bit confused how
to organize what I need :-).
I''ve a
2003 Oct 28
0
Re: Problems with rules since upgrading to 1.4.7b
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
>
2002 Jan 03
2
error starting shorewall
hi,
i installed and configured the shorewall-2.0.9 for standalone user
interface in fc2,then removed the stop ,stopped and the routestopped
files from the /etc/shorewall directory,and run the ''shorewall start''
command,at boot time the messages showing that it is not started,this is
the /var/log/messages output fore shorewall:
Jan 3 04:13:27 localhost netfs: Mounting other
2004 Apr 01
0
Shorewall 2.0.1 RC4
This is a one-line change to the ''firewall'' script to restore the
''routeback'' interface option to health.
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
2004 Mar 25
0
Shorewall 2.0.1 RC1 Withdrawn
I''m withdrawing RC1. When the problems have been resolved, I will
release RC2.
Sorry for the mess....
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
2004 Mar 26
3
Shorewall 2.0.1 RC2
RC2 is available -- hopefully I got it right this time.
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
2004 Mar 29
2
Shorewall-2.0.1-RC3
This should be it. Thanks to Francesca Smith, this RC also includes samples.
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