Displaying 20 results from an estimated 20000 matches similar to: "Shorewall.net Downtime this evening"
2002 Mar 18
0
Shorewall.net downtime this evening
I need to replace one of the firewall''s NICs so I''ll be taking shorewall.net
down for maintenance this evening.
I''m planning to start around 4PM PST (Midnight GMT) -- shouldn''t take more
than half an hour.
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 Jun 08
0
Shorewall.net Downtime
shorewall.net will be down for maintenance this evening beginning at 22:00
GMT. The downtime should be 15 minutes or less.
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
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 Jun 08
1
Shorewall.net back on line
The maintenance (adding RAM) took a little longer than I planned:
1) Shutdown - 1 minute
2) Open Case - 30 seconds
At this point, I emember that I can''t add RAM to this box without removing
the Mother Board (hinge-mounted in case) - slap forehead.
3) Remove cables, PCI NIC & MB - 2 minutes
4) Add RAM - 1 Minute
5) Get the %$#@ MB back in the case and aligned -- 15 Minutes
6)
2002 Aug 26
0
"shorewall refresh" bug in Shorewall 1.3.7a
"shorewall refresh" is not handling FORWARDPING=Yes properly in 1.3.7a. After
a refresh, the configuration is the same as it would be with FORWARDPING=No.
There''s a corrected firewall script available from
http://www.shorewall.net/errata.htm.
Sorry for the inconvenience...
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ:
2002 Mar 19
0
Shorewall.net is back online
I''ve completed the maintenance and everything seems to be back up now.
Sorry for any inconvenience,
-Tom
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
2002 Feb 23
0
Shorewall 1.2.8
1.2.8 is now available for download from my site and from Sourceforge.
If you have installed 1.2.7 then before trying to restart under 1.2.8:
a) Look at your /etc/shorewall/shorewall.conf file and note the directory=
=20
in the STATEDIR variable. If that variable is empty, assume
/var/state/shorewall
b) Remove the file ''lock'' in the directory determined in step a.
You
2004 Jun 01
3
Shorewall.net Downtime this Weekend
The following systems will be down this weekend for server rebuild:
shorewall.net
lists.shorewall.net
www1.shorewall.net
ftp1.shorewall.net
rsync.shorewall.net
cvs.shorewall.net
This will affect:
Shorewall site and archive search
Mailing list archives
Mailing lists
CVS
Primary DNS for shorewall.net
I will start the rebuild on Saturday morning and hope to be done by
Saturday
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 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
2004 Nov 11
0
Shorewall.net downtime again this weekend
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday, I will be rebuilding my server. I expect the project to
take most of the day. I will begin around 7AM PST (-0800).
The server hosts the following sites:
www1.shorewall.net (a.k.a. shorewall.net)
ftp1.shorewall.net
lists.shorewall.net
rsync.shorewall.net
Sorry for the inconvenience.
- -Tom
- --
Tom Eastep \ Nothing is foolproof
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
2002 Apr 16
1
Shorewall Debian News
Lorenzo Marignoni reports that:
o Shorewall 1.2.10 is in the Debian Testing Branch
o Shorewall 1.2.11 is in the Debian Unstable Branch
Thanks, Lorenzo!
--
Tom Eastep \ Shorewall - iptables made easy
AIM: tmeastep \ http://www.shorewall.net
ICQ: #60745924 \ teastep@shorewall.net
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
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 Mar 20
3
Shorewall 1.2.10
This is a minor release of Shorewall.
In this release:
1. A "shorewall try" command has been added. This command attempts to
restart Shorewall using an alternate configuration and if that
attempt fails, Shorewall is automatically started with the default
configuration. This is useful for remote administration where a
failed restart of Shorewall can leave you isolated from
2002 Sep 16
3
Shorewall 1.3.8
This is a minor release of Shorewall which rolls up a number of bug
fixes.
New features include:
1. A NEWNOTSYN option has been added to shorewall.conf. This option
determines whether Shorewall accepts TCP packets which are not part
of an established connection and that are not ''SYN'' packets (SYN
flag on and ACK flag off).
2. The need for the