search for: monkeynoodle

Displaying 20 results from an estimated 44 matches for "monkeynoodle".

2004 Dec 30
4
Shorewall 2.2.0 RC3
http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC3 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC3 Just a few bug fixes: * The following error message could appear during "shorewall stop" clear": local: lo:: bad variable name * * The rate limiting example in /etc/shorewall/rules has been changed to use the RATE
2004 Dec 06
3
OT Linux/Gateway alternative for WAN compression/accelerator
I''m building a 10 branch/1 headquarter network with Shorewall/Linux as gateway on all locations. The TI guy asked me if there is a way to ''cache'' TCP/UDP traffic between them. I crawled on Internet and I only find very expensive solutions for this. Some of them appeared in this comparison article: http://www.networkcomputing.com/showitem.jhtml?docid=1524f5 Does anyone
2005 Jan 07
1
Shorewall 2.2.0 RC4
http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC4 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC4 New Features: 1. A listing of loaded iptables kernel modules is now included in the output of "shorewall status". Problems Corrected. 1. Several problems associated with processing the IPSEC column in /etc/shorewall/masq have been corrected. -Tom --
2004 Oct 23
3
New Contribution
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adem has contributed a nice IP Subnet chart which I''ve placed at http://shorewall.net/pub/shorewall/contrib/IPSubNetMask.html Thanks Adem! - -Tom - -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \
2004 Aug 10
2
[OT] Bandwidth reporting tool recommendations
Hi, Also, does anyone have a recommendation for a reporting tool that shows bandwidth use, for each IP and each interface on a Shorewall FW? Tried BandwidthD, but couldn''t get it to compile on Mandrake10... NAAT might fit the bill - if it doesn''t mess-up my shorewall setup... Thanks for any suggestions, Richard.
2005 May 02
4
streaming from the sound card
...;1</consolelog> <stream> <metadata> <name>Radio Waves</name> <genre>Any</genre> <description>The real radio</description> <url>http://www.monkeynoodle.org</url> </metadata> <input> <module>alsa</module> <param name="rate">44100</param> <param name="channels">2</param> &...
2005 Feb 05
9
Hot Fallover
Hello List: Recently our shorewall FW server went dead (PS failure) & brought the entire system down. Luckily we are testing the FW and other servers, so we did not loose anything. Now we have decided to setup two Shorewall FW servers with a primary & another fallover FW server. I have done some research cruised the Internet and found that a product ''UCARP''
2005 Jun 05
1
Shorewall 2.4.0
Note: Because of the short time that has elapsed since the release of Shorewall 2.2.0, Shorewall 2.0 will be supported until 1 December 2005 or until the release of Shorewall 2.6.0, whichever occurs first. http://shorewall.net/pub/shorewall/2.4/shorewall-2.4.0 ftp://shorewall.net/pub/shorewall/2.4/shorewall-2.4.0 -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
2005 May 20
1
Shorewall 2.2.5
This will be my last 2.2 release. It contains a couple of small bug fixes that I had laying around. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.5 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.5 1) Previously, if PKTTYPE=No in shorewall.conf then pkttype match would still be used if the kernel supported it. 2) A typo in the ''tunnel'' script has been corrected
2005 Feb 02
1
Shorewall 2.0.16
This release back-ports the DROPINVALID shorewall.conf option from 2.2.0. 1) Recent 2.6 kernels include code that evaluates TCP packets based on TCP Window analysis. This can cause packets that were previously classified as NEW or ESTABLISHED to be classified as INVALID. The new kernel code can be disabled by including this command in your /etc/shorewall/init file: echo 1
2005 Feb 16
1
Shorewall 2.2.1
This release just rolls up the fixes for the few problems that have surfaced in the first two to three weeks of Shorewall 2.2 availability. If 2.2.0 is working ok for you, there is no reason to upgrade. So far I''ve been very pleased with the stability of the 2.2 release and attribute much of that to the new release model. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.1
2005 Jan 12
1
Shorewall 2.0.15
My sincere apologies for the messed up 2.0.14. I didn''t realize that I had merged a change from 2.2.0 but hadn''t tested it. http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.15 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.15 1. The range of ports opened by the AllowTrcrt action has been expanded to 33434:33524 to allow for a maximum of 30 hops. 2. Code mis-ported
2005 Jan 17
1
Shorewall 2.2.0 RC5
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''m hoping that this will be the last RC and that I can release 2.2.0 on February 1. I appreciate your help in testing this RC. http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC5 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-RC5 Problems Corrected: 1. The AllowTrcrt action has been changed to allow up to 30
2005 Apr 02
0
shorewall 2.0.17 mandrake rpms
shorewall 2.0.17 mandrake rpms are up at http://www.monkeynoodle.org/comp/net/shorewall/ -- Jack at Monkeynoodle dot Org: It''s a Scientific Venture... Riding the Emergency Third Rail Power Trip since 1996!
2005 Jan 03
3
Shorewall 2.0.14
http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.14 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.14 New Features: 1. Previously, when rate-limiting was specified in /etc/shorewall/policy (LIMIT:BURST column), any traffic which exceeded the specified rate was silently dropped. Now, if a log level is given in the entry (LEVEL column) then drops are logged
2005 Mar 12
1
Shorewall 2.2.2 (Corrected)
I forgot to add the last new feature to the previous announcement. Shorewall 2.2.2 is now available. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.2 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.2 Problems Corrected: 1. The SOURCE column in the /etc/shorewall/tcrules file now correctly allows IP ranges (assuming that your iptables and kernel support ranges). 2.
2005 Mar 09
20
WebGUI Scripts announcement
Dear Shorewall Users, having noticed that the request for a WebGUI is growing, after a very short conversation I''ve had with Tom, I''d like to let you all evaluate the Web interface to Shorewall I''ve written, integrating the original weblet package made available for the LRP project. ---------------------------------------------------------------------------- Preamble
2005 May 02
1
Shorewall 2.2.4
http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.4 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.4 Problems Corrected: 1. The error message: Error: No appropriate chain for zone <z1> to zone <z2> has been changed to one that is more self-explanatory: Error: No policy defined for zone <z1> to zone <z2> 2. When only an
2005 Apr 07
4
Shorewall 2.2.3
http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.3 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.3 Problems Corrected: 1) If a zone is defined in /etc/shorewall/hosts using <interface>:!<network> in the HOSTS column then startup errors occur on "shorewall [re]start". 2) Previously, if "shorewall status" was run on a system whose kernel lacked
2004 Dec 29
5
newnotsyn question
...LOGNEWNOTSYN=debug /etc/shorewall/shorewall.conf:435:NEWNOTSYN=No These three interfaces are the "inside" zone, eth0 is the Internet. I haven''t found anything relevant by searching the shorewall.net documentation, but I could certainly take a STFW pointer. thanks, -- Jack at Monkeynoodle dot Org: It''s a Scientific Venture... Riding the Emergency Third Rail Power Trip since 1996!