Displaying 20 results from an estimated 4000 matches similar to: "ADD_IP_ALIASES"
2002 May 04
0
Shorewall 1.2.13 Available
In this release:
1. Whitelist support has been added.
2. Optional SYN Flood protection is now available.
3. Aliases added under ADD_IP_ALIASES and ADD_SNAT_ALIASES
now use the VLSM and broadcast address of the interface''s
primary address.
4. Port forwarding rules may now optionally override the
contents of the /etc/shorewall/nat file.
-Tom
--
Tom Eastep \ Shorewall -
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
2002 Dec 05
7
New in CVS
The ''firewall'' script currently in the /Shorewall CVS project:
a) Is approximately 15% faster starting/restarting on my configuration --
please report your experiences with it.
b) Reloads Traffic Control/Shaping as part of "shorewall refresh"
c) Turns off the shell trace after an error has occured (except when the
command being traced is "stop" or
2002 Apr 28
0
[Documentation] Re: [Shorewall-users] Logging is done to console (fwd)
This is becoming a FAQ and should probably be added to the docs.
Thanks,
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
---------- Forwarded message ----------
Date: Sun, 28 Apr 2002 16:09:01 -0700 (Pacific Daylight Time)
From: Tom Eastep <teastep@shorewall.net>
To: Carl Spelkens
2002 Mar 03
0
Fwd: Re: strange UDP scan results on a Shorewall firewall
---------- Forwarded Message ----------
Subject: Re: [Shorewall-users] strange UDP scan results on a Shorewall=20
firewall
Date: Sun, 3 Mar 2002 08:33:20 -0800
From: Tom Eastep <teastep@shorewall.net>
To: "Scott Duncan" <sduncan@cytechconsult.com>
On Saturday 02 March 2002 04:30 am, Scott Duncan wrote:
> Yes, the net->all policy is the same on all three (REJECT log
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
2002 Aug 22
3
Questions about NAT and MASQ and more
Hello,
I''m working on a Shorewall-1.2 setup on a _remote_ debian (woody)
firewall with several live web and mail servers behind it. I know doing
this remotely is a *really* bad idea, and I''d rather not be in this
situation, but so it goes... Worst case scenario, I lock myself out and
have to drive an hour to get physical access to the machine and restore
service. Anyhow,
2002 Nov 20
3
Spam vs. Viruses
I have purchased a license for Vexira MailArmor (an antivirus product) and
the good news is that it is installed and working at shorewall.net. The bad
news is that I have yet to get Vexira running together with SpamAssassin :-(
As things currently stand, list posts will be protected from viruses but
may contain Spam. I''ll continue to work to correct this situation.
-Tom
--
Tom Eastep
2002 May 14
2
Shorewall.net is back up
Let me know if there are any problems.
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 Dec 07
6
More speedups in CVS
The ''firewall'' and ''functions'' file in CVS together produce a 30%+ speedup
of ''shorewall restart'' on my firewall when compared to 1.3.11a.
Please test with these files -- I don''t anticipate making any more
performance changes for 1.3.12 and I want to be sure that I didn''t break
anything.
-Tom
--
Tom Eastep \ Shorewall
2002 May 15
4
Your opinion please
The 1.2 firewall contains messy logic to support the old sample
configurations in that any rule that contains "none" in any of its columns
is ignored.
I''m considering removing that messiness in 1.3 and seek the opinion of the
list.
Thanks,
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 Nov 12
3
''all'' in rules file
I have implemented the ability to specify ''all'' in the SOURCE and
DESTINATION columns of the rules file and I''m not sure I like the result.
The code is in CVS if any of you are interested in giving it a try. If you
do try it, please let me know what you think.
If you specify ''all'' in those columns it must not be qualified (may not be
followed by
2002 Jun 15
4
Serious Bug found in Shorewall 1.3.x
Rafa³ Dutko has just discovered a potentially serious bug in version 1.3.0
and 1.3.1. In both versions, where an interface option appears on multiple
interfaces, the option may only be applied to the first interface on which
it appears.
A corrected firewall script for 1.3.1 is available at:
http://www.shorewall.net/pub/shorewall/errata/1.3.1/firewall
and
2007 Apr 11
1
creating a path diagram in sem
Hello,
I finally run my measurement model in sem - successfully. Now, I am trying to print out the path diagram that is based on the results - but for some reason it's not working. Below is my script - but the problem is probably in my very last line:
# ANALYSIS OF ANXIETY, DEPRESSION, AND FEAR - LISREL P.31
library(sem)
# Creating the ANXIETY, DEPRESSION, AND FEAR intercorrelation matrix
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]-----------------------------------------------
2002 Apr 13
2
Shorewall 1.2.11 Available
In this release:
1. The ''try'' command now accepts an optional timeout. If the timeout is
given in the command, the standard configuration will automatically
be restarted after the new configuration has been running for that
length of time. This prevents a remote admin from being locked out
of the firewall in the case where the new configuration starts but
prevents
2002 Jun 02
1
CVS Web Access
There is now a link from the Shorewall home page to the CVS repository.
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 Jan 26
1
Shorewall 1.2.4 Beta
Shorewall 1.2.4 will have the following changes:
a) ''#'' comments now allowed at end-of-line in all config files.
b) Firewall zone may be renamed
c) Protection against concurrent state-changing operations (start, stop,
restart, refresh, clear)
d) ''shorewall start'' no longer fails if ''detect'' is specified for an
interface with netmask
2002 Aug 25
1
Shorewall 1.3.7a Debian Packages Available
Apt-get sources are listed at:
http://wecurity.dsi.unimi.it/~lorenzo/debian.html
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
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