similar to: Web site search fixed

I''ve determined the problem with the Archives Search. I installed mod_throttle on my Web Server last week and htdig (the search tool that I use) is giving up the first time that it is actively throttled :-( I''m currently rebuilding the search index and hope to have it available soon and I have updated the nightly index build script to disable throttling while the script is

The search capability at http://www.shorewall.net has been improved. - The quick search on the main page no longer includes the mailing list archives. - The extended search page (http://www.shorewall.net/htdig/search.html) allows you to search: a) the entire site (including the archives); b) the site excluding the archivesj; or, c) just the archives. - The mailing list information page

The volume of traffic at here at shorewall.net has reached the point where response time is beginning to suffer. I have therefore decided to move the main web site back to SourceForge at http://shorewall.sf.net. shorewall.net will continue to host the main FTP site along with the mailing list archives. http://www.shorewall.net will also continue to hosts the Shorewall 1.2 web site and will

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

---------- 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

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

"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:

Shorewall.net will be unavailable for approximately two hours this evening beginning at 23:00 GMT (16:00 PDT) for installation of RH7.3. The http and ftp mirrors will still be available and mail will be queued in the backup MX. The mailing list archives and site/archive search will not be available. Apologies for any inconvenience this may cause. -Tom -- Tom Eastep \ Shorewall - iptables

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

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

On Wed, 5 Jun 2002, Ron Shannon wrote: > Bummer. Will the robots.txt handle it? (http://httpd.apache.org/docs/misc/howto.html#stoprob) > Nope -- most of the offending bots just ignore robots.txt. The CVS interface is still available at: http://www.shorewall.net/cgi-bin/cvsweb.cgi There is just no link to it from the index. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM:

I''ve removed the link from the index to the CVS WEB interface until I can figure out how to stop the %$#@s who are running HTTrack, WebStripper, etc. against it. In the mean time, all sites having in-progress sessions using these tools have been blacklisted. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \

This is a cryptographically signed message in MIME format. --------------ms020506080905040804000001 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit And will be unavailable until further notice. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

-- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

-- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

I regret to announce that effective immediatly, CVS Web access will be by password only. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

Hmm--either the indexing process is still running, or it''s broken again. It''s 0443 GMT, and I can''t get the search engine to find anything on the mailing list or the web site (I used ''dns'' as my search term). It''s not that big of an inconvenience, though--Googling for ''site:shorewall.net dns'' does pretty much the same thing.

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

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

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