similar to: CVS pserver unavailable

I''ve built and installed 1.11.15-5 from the Fedora updates. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

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

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

The Shorewall CVS repository is now safely ensconced at Sourceforge. http://sourceforge.net/cvs/?group_id=22587 Please note that unlike with the old repository here at shorewall.net, at Sourceforge there is a delay in updating the ViewCVS (web) copy of the repository. As a consequence, developer commits are not immediately available for browsing with ViewCVS

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

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:

I have just updated the ''makeshorewall'' script to use CVS at sourceforge. Note that anonymous pserver access still suffers the five hour update delay that is also seen in the Web interface. Once the changes to the Sourceforge infrastructure that Mike posted are complete, this delay will be eliminated. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool

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

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

The Shorewall CVS repository is now hosted on Sourceforge at http://sourceforge.net/cvs/?group_id=22587. Please note that unlike with the old repository here at shorewall.net, at Sourceforge there is a delay in updating the ViewCVS (web) copy of the repository. As a consequence, developer commits are not immediately available for browsing with ViewCVS

If you are willing to patch your iptables and kernel to support the ROUTE target, the code in CVS project Shorewall2/ now supports very flexible routing. As an example, I run Squid in my DMZ for transparent proxy. Rather than the complex routing setup described in http://shorewall.net/Shorewall_Squid_Usage.html, I now use this single entry in /etc/shorewall/routes to route all HTTP requests from

In the Shorewall/ CVS project: Problems Corrected: 1) There has been a low continuing level of confusion over the terms "Source NAT" (SNAT) and "Static NAT". To avoid future confusion, all instances of "Static NAT" have been replaced with "One-to-one NAT" in the documentation and configuration files. 2) The description of NEWNOTSYN in

The Shorewall2/ project in CVS contains my initial attempt to establish correct routing for traffic forwarded from two different ISPs to internal servers. >From the release notes: Shorewall 2.3.2 includes support for multiple Internet interfaces to different ISPs. This feature is enabled by setting the "default" option for each Internet interface in

In case any of you are interested, I''ve placed my script for building an entire Shorewall release from CVS into ftp://shorewall.net/pub/shorewall/contrib/makeshorewall.sh. The script assumes that the appropriate CVS project has already been updated with the current version number. There is currently no mechanism for re-building old releases. -Tom -- Tom Eastep \ Nothing is

On Thu, 2003-12-04 at 14:14, Alex Martin wrote: > > I will start posting this type of discussion to shorewall-devel, so that others > might help. > > Just let me know what you think. > I just checked in a few minor changes to the Docs -- I''ll try to keep my hands off of them while others are working on them. -Tom -- Tom Eastep \ Nothing is foolproof to a

I''ve moved the remaining HTML files (including those that Mike and Paul are working on) to a new project named Shorewall-Website. This will segregate the Docbook documentation from the Website-only HTML files. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

I believe that the code now works with nested actions -- the previous code that I had checked in didn''t come close :-) -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Thanks for such a quick reply Tom! Any suggestions then as to what I might do other than putting a second nic in the SBS and opening it up for web access? I don''t like the idea, but since MS SBS includes fireall that is actually what MS suggests. Boyd -----Original Message----- From: Tom Eastep [mailto:teastep@shorewall.net] Sent: January 3, 2005 3:05 PM To: Shorewall Users Cc: Boyd

Plus I would like to let you know that it works like a charm. Snort can now see those packets. -----Original Message----- From: shorewall-users-bounces@lists.shorewall.net [mailto:shorewall-users-bounces@lists.shorewall.net] On Behalf Of Thibodeau, Jamie L. Sent: Wednesday, March 30, 2005 9:25 AM To: Mailing List for Shorewall Users Subject: RE: [Shorewall-users] Shorewall and an inline