similar to: Shorewall 4.5.14 RC 1

RC 1 is now available for testing. Problems corrected: 1) All sample .conf files have been changed to specify FORWARD_CLEAR_MARK= rather than FORWARD_CLEAR_MARK=Yes That way, systems without MARK support will still be able to install the sample configurations and FORWARD_CLEAR_MARK will default to Yes on systems with MARK support. 2) The install scripts in the

RC 1 is now available for testing. Problems corrected: 1) All sample .conf files have been changed to specify FORWARD_CLEAR_MARK= rather than FORWARD_CLEAR_MARK=Yes That way, systems without MARK support will still be able to install the sample configurations and FORWARD_CLEAR_MARK will default to Yes on systems with MARK support. 2) The install scripts in the

Togan Muftuoglu has just informed me that Shorewall is now available in the following repositories: <http://download.opensuse.org/repositories/security:/netfilter/openSUSE_11.2> <http://download.opensuse.org/repositories/security:/netfilter/openSUSE_11.3> <http://download.opensuse.org/repositories/security:/netfilter/openSUSE_Factory> Thanks Togan!! -Tom -- Tom Eastep

Beta 2 is now available for testing. ---------------------------------------------------------------------------- I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E ---------------------------------------------------------------------------- 1) This release includes all defect repair from Shorewall 4.5.17.1. 2) The following warning message could be emitted

Beta 1 is now available for testing. New Features: 1) AUTOMAKE=Yes now causes all directories on the CONFIG_PATH to be searched for files newer than the script that last started/restarted the firewall. 2) FORMAT-2 actions may now specify default parameter values using the DEFAULTS directive. DEFAULTS <def1>,<def2>,... Where <def1> is the default

Beta 1 is now available for testing. New Features: 1) AUTOMAKE=Yes now causes all directories on the CONFIG_PATH to be searched for files newer than the script that last started/restarted the firewall. 2) FORMAT-2 actions may now specify default parameter values using the DEFAULTS directive. DEFAULTS <def1>,<def2>,... Where <def1> is the default

In kernel 2.6.31, the handling of the rp_filter interface option was changed incompatibly. Previously, the effective value was determined by the setting of net.ipv4.config.dev.proxy_arp logically ANDed with the setting of net.ipv4.config.all.proxy_arp. Beginning with kernel 2.6.31, the value is the arithmetic MAX of those two values. Additionally, a ''loose'' routefiltering

Do those of you who are testing 4.4.16 RC 1 plan to do additional testing or can we consider 4.4.16 ready for release? Please let me know by close of business on Tuesday, Jan 11 if you plan additional testing. Thank you for helping with the testing effort, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not

Do those of you who are testing 4.4.16 RC 1 plan to do additional testing or can we consider 4.4.16 ready for release? Please let me know by close of business on Tuesday, Jan 11 if you plan additional testing. Thank you for helping with the testing effort, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not

RC 2 is now available for testing (Early RC1 testing on a RedHat-based system with dynamic provider gateways uncovered a couple of debilitating defects in the enable/disable logic). Thank you for testing, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in

RC 2 is now available for testing (Early RC1 testing on a RedHat-based system with dynamic provider gateways uncovered a couple of debilitating defects in the enable/disable logic). Thank you for testing, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in

Shorewall 4.5.6 RC 1 is now available for testing. Problems corrected since Beta 4: 1) In the generated script, the logic for handling wildcard interfaces with the ''wait=n'' option was incorrect. For each matching interface, the script would check its readiness n times in rapid succession. The script now sleeps 1 second between checks. 2) Previously, the tcrules

Shorewall 4.5.6 RC 1 is now available for testing. Problems corrected since Beta 4: 1) In the generated script, the logic for handling wildcard interfaces with the ''wait=n'' option was incorrect. For each matching interface, the script would check its readiness n times in rapid succession. The script now sleeps 1 second between checks. 2) Previously, the tcrules

Shorewall 4.4.19.4 is now available. Problems corrected in this update: 1) Previously, the compiler would allow a degenerate entry (only the BAND specified) in /etc/shorewall/tcpri. Such an entry now raises a compilation error. 2) Previously, it was possible to specify tcfilters and tcrules that classified traffic with the class-id of a non-leaf HFSC class. Such classes are

RC 1 is now available for testing. This version corrects several problems in Beta 3: 1) Release notes now correctly refer to FORWARD_CLEAR_MARK rather than CLEAR_FORWARD_MARK. 2) The NET3 column in /etc/shorewall/netmap now works correctly. 3) A missing closing quote in the generated script when using REQUIRE_INTERFACE=Yes has been corrected. 4) The compiler now correctly detects the

RC 1 is now available for testing. This version corrects several problems in Beta 3: 1) Release notes now correctly refer to FORWARD_CLEAR_MARK rather than CLEAR_FORWARD_MARK. 2) The NET3 column in /etc/shorewall/netmap now works correctly. 3) A missing closing quote in the generated script when using REQUIRE_INTERFACE=Yes has been corrected. 4) The compiler now correctly detects the

Beta 4 is now ready for testing. http://www.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta4/ ftp://ftp.shorewall.net/pub/shorewall/development/4.4/shorewall-4.4.0-Beta4/ ---------------------------------------------------------------------------- P R O B L E M S C O R R E C T E D I N 4 . 4 . 0 Beta 4

RC 2 is ready for testing. Problems corrected: 1) The 4.5.1 Shorewall Lite and Shorewall6 Lite installers install the wrong SysV init script on Debian and derivatives. That has been corrected. 2) The getparams program now reads the installed shorewallrc file rather than ~/.shorewallrc. 3) The ''load'' and ''reload'' now copy the

RC 2 is ready for testing. Problems corrected: 1) The 4.5.1 Shorewall Lite and Shorewall6 Lite installers install the wrong SysV init script on Debian and derivatives. That has been corrected. 2) The getparams program now reads the installed shorewallrc file rather than ~/.shorewallrc. 3) The ''load'' and ''reload'' now copy the

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