similar to: 1.4.0 PDFs are available

Displaying 20 results from an estimated 40000 matches similar to: "1.4.0 PDFs are available"

2003 Jun 20
0
PDFs for 1.4.5
The PDFs are available at: ftp://slovakia.shorewall.net/mirror/shorewall/pdf/ http://slovakia.shorewall.net/pub/shorewall/pdf/ rsync://slovakia.shorewall.net/shorewall/pdf/ -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net
2003 Mar 12
0
1.3.14a PDFs
Juraj Ontkanin has informed me that he has updated the PDF files for 1.3.14a. The PDFs are available at: ftp://slovakia.shorewall.net/mirror/shorewall/pdf/ http://slovakia.shorewall.net/pub/shorewall/pdf/ Also available (or will be shortly) at your favorite mirror in the contrib/pdf directory. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net
2005 Feb 15
0
Updated PDFs available
Thanks to Juraj Ontkanin, updated versions of the documentation in PDF format are now available at Juraj''s site: ftp://slovakia.shorewall.net/mirror/shorewall/pdf/ http://slovakia.shorewall.net/pub/shorewall/pdf/ rsync://slovakia.shorewall.net/shorewall/pdf/ -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net
2004 Jan 14
0
1.4.9 Documentation in PDF format
The .pdf is ready at: ftp://slovakia.shorewall.net/mirror/shorewall/pdf/ http://slovakia.shorewall.net/pub/shorewall/pdf/ -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net
2003 Mar 17
3
Shorewall 1.4.0
Shorewall 1.4.0 is released and is available at both SourceForge and at the mirror in Washington State. Other mirrors will be updated shortly. The content of 1.4.0 is the same as 1.4.0-RC3 with the exception of the updated version number. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.sf.net Washington USA \ teastep@shorewall.net
2007 Nov 28
2
[Fwd: Re: Port 3001 still have problem]
-----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
2004 Sep 23
0
Fwd: RE: 2.6 kernel ipsec and shorewall
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
2012 Dec 29
0
Shorewall Project Upgraded to Allura
The Shorewall project at sourceforge has been upgraded to Allura. If you have a copy of the git repository, you need to check out a fresh copy from the new locations: git clone ssh://teastep@git.code.sf.net/p/shorewall/code shorewall git clone ssh://teastep@git.code.sf.net/p/shorewall/release release git clone ssh://teastep@git.code.sf.net/p/shorewall/tools tools git clone
2004 Nov 02
3
Shorewall 2.2.0 Beta 2
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
2003 Mar 11
2
Shorewall 1.4.0 RC3
I anticipate that this will be the last RC unless problems are discovered. Changes since RC2 include: * The default route is now ignored when Shorewall is detecting masqueraded networks. A warning message is issued if the default route goes through the source interface (normally, the destination interface is the firewall''s external interface and therefore, the default route would go
2004 Sep 29
0
Re: Shorewall-users Digest, Vol 22, Issue 65
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:
2005 Sep 20
0
Fwd: [PATCH] Another iptables-save buglet
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
2004 Nov 02
0
Shorewall 2.2.0 Beta 2
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
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
2003 Aug 25
0
cant open port (fwd)
And Andrew -- PLEASE don''t reply off-list. I''m not a private help desk... -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net ---------- Forwarded message ---------- Date: Mon, 25 Aug 2003 19:01:34 -0700 (Pacific Daylight Time) From: Tom Eastep <teastep@shorewall.net> To: andrew
2003 Feb 21
0
Shorewall 1.4.0 Beta 1
The first 1.4.0 Beta is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4 behavior is the same as 1.3 with MERGE_HOSTS=Yes. 2. Interface names of the form
2003 Feb 19
0
Proposed Shorewall 1.4.0 Content
Here is the proposed content -- I''m looking for a Beta to start in the next week or so with release around the middle of next month. The main focus of 1.4 will be to provide external behavior similar to the upcoming 2.0 release. Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4
2003 Mar 05
3
Shorewall 1.4.0 RC1
The first release candidate is now available at: http://www.shorewall.net/pub/shorewall/Beta ftp://ftp.shorewall.net/pub/shorewall/Beta The only change between Beta 1 and RC1 is that the ''check'' command is back in RC1. Function from 1.3 that has been omitted from this version includes: 1) The MERGE_HOSTS variable in shorewall.conf is no longer supported. Shorewall 1.4
2007 Sep 21
1
Warning: Support for the 'detectnets' interface option to be removed from Shorewall-perl
The ''detectnets'' interface option has always been a rather silly feature. For incoming packets, it duplicates the function of the ''routefilter'' option. It provides no value on output since it enforces the same thing that the routing table does. In other words, if you set ''routefilter'' and ''log_martians'' you get the same
2003 Mar 07
0
Shorewall 1.4.0 RC2
Other than a couple of changes to comments in the config files and changes to the HTML documents, the only difference between RC1 and RC2 is that RC2 really does process the /etc/shorewall/params file first so that variables set there can be used in the /etc/shorewall/shorewall.conf file. As always, the release candidate may be downloaded from: http://www.shorewall.net/pub/shorewall/Beta