mirror of
https://gitlab.com/shorewall/code.git
synced 2024-11-14 19:54:06 +01:00
Update 'flow=' description in the release notes
This commit is contained in:
parent
12279e57ed
commit
e18238c665
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user