forked from extern/shorewall_code
Update version to 4.3.11
This commit is contained in:
parent
e1771ebead
commit
b0b47e7f30
@ -28,7 +28,7 @@
|
||||
# shown below. Simply run this script to revert to your prior version of
|
||||
# Shoreline Firewall.
|
||||
|
||||
VERSION=4.3.10
|
||||
VERSION=4.3.11
|
||||
|
||||
usage() # $1 = exit status
|
||||
{
|
||||
|
@ -22,7 +22,7 @@
|
||||
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
|
||||
#
|
||||
|
||||
VERSION=4.3.10
|
||||
VERSION=4.3.11
|
||||
|
||||
usage() # $1 = exit status
|
||||
{
|
||||
|
@ -1,5 +1,5 @@
|
||||
%define name shorewall-lite
|
||||
%define version 4.3.10
|
||||
%define version 4.3.11
|
||||
%define release 0base
|
||||
|
||||
Summary: Shoreline Firewall Lite is an iptables-based firewall for Linux systems.
|
||||
@ -98,6 +98,8 @@ fi
|
||||
%doc COPYING changelog.txt releasenotes.txt
|
||||
|
||||
%changelog
|
||||
* Sun May 10 2009 Tom Eastep tom@shorewall.net
|
||||
- Updated to 4.3.11-0base
|
||||
* Sun Apr 19 2009 Tom Eastep tom@shorewall.net
|
||||
- Updated to 4.3.10-0base
|
||||
* Sat Apr 11 2009 Tom Eastep tom@shorewall.net
|
||||
|
@ -26,7 +26,7 @@
|
||||
# You may only use this script to uninstall the version
|
||||
# shown below. Simply run this script to remove Shorewall Firewall
|
||||
|
||||
VERSION=4.3.10
|
||||
VERSION=4.3.11
|
||||
|
||||
usage() # $1 = exit status
|
||||
{
|
||||
|
@ -104,7 +104,7 @@ None.
|
||||
class. SFQ ensures that each 'flow' gets equal access to the
|
||||
interface.
|
||||
|
||||
The default definition of a 'flow' corresponds to a TCP
|
||||
The default definition of a 'flow' roughly corresponds to a TCP
|
||||
connection. So if one internal system is running BitTorrent, for
|
||||
example, it can have lots of 'flows' and can thus take up a larger
|
||||
share of the bandwidth than a system having only a single active
|
||||
@ -122,9 +122,16 @@ None.
|
||||
Shaping traffic bound for your
|
||||
local net flow=dst
|
||||
|
||||
These will cause a 'flow' to consists of the traffic to/from each
|
||||
These will cause a 'flow' to consist of the traffic to/from each
|
||||
internal system.
|
||||
|
||||
The possible keys can be learned using the command:
|
||||
|
||||
tc filter add flow help
|
||||
|
||||
When more than one key is specified, they must be enclosed in
|
||||
parentheses and separated by commas.
|
||||
|
||||
----------------------------------------------------------------------------
|
||||
N E W F E A T U R E S IN 4 . 3
|
||||
----------------------------------------------------------------------------
|
||||
|
Loading…
Reference in New Issue
Block a user