Update 'flow=' description in the TC doc

This commit is contained in:
Tom Eastep 2009-12-05 08:07:34 -08:00
parent e18238c665
commit acc985a290

View File

@ -606,25 +606,26 @@ ppp0 6000kbit 500kbit</programlisting>
<listitem> <listitem>
<para>flow=<emphasis>keys</emphasis> - Shorewall attaches an SFQ <para>flow=<emphasis>keys</emphasis> - Shorewall attaches an SFQ
queuing discipline to each leaf HTB class. SFQ ensures that each queuing discipline to each leaf HTB and HFSC class. SFQ ensures
<firstterm>flow</firstterm> gets equal access to the interface. that each <firstterm>flow</firstterm> gets equal access to the
The default definition of a flow corresponds roughly to a interface. The default definition of a flow corresponds roughly
Netfilter connection. So if one internal system is running to a Netfilter connection. So if one internal system is running
BitTorrent, for example, it can have lots of 'flows' and can BitTorrent, for example, it can have lots of 'flows' and can
thus take up a larger share of the bandwidth than a system thus take up a larger share of the bandwidth than a system
having only a single active connection. The having only a single active connection. The
<option>flow</option> classifier (module cls_flow) works around <option>flow</option> classifier (module cls_flow) works around
this by letting you define what a 'flow' is. The clasifier must this by letting you define what a 'flow' is. The clasifier must
be used carefully or it can block off all traffic on an be used carefully or it can block off all traffic on an
interface! The flow option can be specified for an HTB leaf interface! The flow option can be specified for an HTB or HFSC
class (one that has no sub-classes). We recommend that you use leaf class (one that has no sub-classes). We recommend that you
the following:</para> use the following:</para>
<simplelist> <simplelist>
<member>Shaping internet-bound traffic: flow=nfct-src</member> <member>Shaping internet-bound traffic: <emphasis
role="bold">flow=nfct-src</emphasis></member>
<member>Shaping traffic bound for your local net: <member>Shaping traffic bound for your local net: <emphasis
flow=dst</member> role="bold">flow=dst</emphasis></member>
</simplelist> </simplelist>
<para>These will cause a 'flow' to consists of the traffic <para>These will cause a 'flow' to consists of the traffic