holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Update 'flow=' description in the release notes

Browse Source
This commit is contained in:
Tom Eastep 2009-12-05 08:05:20 -08:00
parent 12279e57ed
commit e18238c665
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Shorewall/releasenotes.txt
View File

@ -885,10 +885,10 @@ None.
used.
28) A 'flow=<keys>' option has been added to the
/etc/shorewall/tcclasses.
/etc/shorewall/tcclasses OPTIONS column.
Shorewall attaches an SFQ queuing discipline to each leaf HTB
class. SFQ ensures that each flow gets equal access to the
and HFSC class. SFQ ensures that each flow gets equal access to the
interface. The default definition of a flow corresponds roughly to
a Netfilter connection. So if one internal system is running
BitTorrent, for example, it can have lots of 'flows' and can thus
@ -899,8 +899,8 @@ None.
The clasifier must be used carefully or it can block off all
traffic on an interface!
The flow option can be specified for an HTB leaf class (one that
has no sub-classes). We recommend that you use the following:
The flow option can be specified for an HTB or HFSC leaf class (one
that has no sub-classes). We recommend that you use the following:
Shaping internet-bound traffic: flow=nfct-src
Shaping traffic bound for your local net: flow=dst