similar to: Mailing List Archive Search

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.

Sorry for the inconvenience. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net

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 \

I have been separating the content of my site into mailing list and other content with an eye toward moving the main site to another system. In that process, I managed to break the search function. I believe that I have everything put back together now -- please let me know if you find any problems. Again, I apologize for the inconvenience. -Tom -- Tom Eastep \ Shorewall - iptables made

Because certain large European ISPs can''t get their act together WRT SPF, I''ve turned on masquerading of lists.shorewall.net. This means that list postings will now have "shorewall.net" sender addresses rather than "lists.shorewall.net". Sorry for the inconvenience but a lot of email is currently bouncing. -Tom -- Tom Eastep \ Nothing is foolproof to a

Tomorrow morning, the following systems will be unavailable while I upgrade the OS on my firewall: a) shorewall.net b) lists.shorewall.net c) cvs.shorewall.net d) rsync.shorewall.net The upgrade will begin around 0700 PST (-0800) and will like take two hours or so. Sorry for the inconvenience. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \

I''m working on it. Word of advice -- if you are ever tempted to install ''htdig'', don''t! -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As I pointed out to Wilson in a private message, this appears to show that no other connection requests (other than port 3000) are being sent from the client to the server (or at least no other connection requests are being received by the Shorewall box). Wilson: Are you sure that the client is supposed to open port 3001 on the server and not the

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

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

Prodded by a comment from Florin Angelescu that he couldn''t find ''blacklist'' information searching the Shorewall archives, I began to investigate and discovered a problem from the server migration. Only the posts from December 2003 were being searched by any of the Internet Search Engines or by Htdig (the search engine I use on the Shorewall Site). I have (finally)

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:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The list server at shorewall.net is seeing a small but steady stream of quaranteened messages from anti-spam software that is asking the list server to respond and thus register itself as a legitimate source of email. I also receive these requests personally. Here''s an example: -

I have created the shorewall-newbies@lists.shorewall.net mailing list and am now soliciting volunteers to be moderators. Please CC me as I am currently not subscribed to shorewall-users. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

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

FYI This bug will prevent ''shorewall restore'' from working if you have "!<single IP address>" in the ORIGINAL DEST column. -Tom ---------- Forwarded Message ---------- Subject: [PATCH] Another iptables-save buglet Date: Wednesday 14 September 2005 15:09 From: Tom Eastep <teastep@shorewall.net> To: netfilter-devel@lists.netfilter.org The conntrack

List traffic since Nov 21 has been missing from the archives -- I believe that I have corrected the problem. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key

The current CVS version (/Shorewall project) contains a redesigned IP accounting facility. The new facility is: a) Much simpler. :-) b) More flexible. :-) c) Compatible with bw-acct. :-) c) Incompatible with the previous implementation :-( There''s a new Accounting Page available at: http://shorewall.net/AccountingNew.html On top of Snapshot 20030813: a) Move the

This morning, I have added a TEST column to /etc/shorewall/routes to allow routing to be dependent on packet/connection marks. I have placed the TEST column _before_ the INTERFACE column which means that this change is not upwardly compatible. If you already have entries in /etc/shorewall/routes, you will need to change them when you install the latest version. Sorry for the inconvenience but

In preparation for splitting the list server off from my mail server, I have updated all of the mailing lists. The list addresses are: Users: shorewall-users@lists.shorewall.net Announce: shorewall-users@lists.shorewall.net Devel: shorewall-devel@lists.shorewall.net The old addresses will continue to work for a while but I urge you to update your address book now as the old addresses will