extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-12-22 06:10:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

Apply patch from Fog_Watch

Browse Source
This commit is contained in:
Tom Eastep 2010-05-12 06:23:03 -07:00
parent a04d8126e1
commit a0a08c918d
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/traffic_shaping.xml
View File

@ -148,7 +148,7 @@
linkend="tcclasses">below</link>.</para>
<para>You can shape incoming traffic through use of an
<firstterm>Intermediate Frame Block</firstterm> (IFB) device. <link
<firstterm>Intermediate Functional Block</firstterm> (IFB) device. <link
linkend="IFB">See below</link>. <emphasis role="bold">But beware: using an
IFB can result in queues building up both at your ISPs router and at your
own.</emphasis></para>
@ -428,7 +428,7 @@
<listitem>
<para>REDIRECTED INTERFACES — Entries are appropriate in this column
only if the device in the INTERFACE column names a <link
linkend="IFB">Intermediate Frame Block (IFB)</link>. It lists the
linkend="IFB">Intermediate Functional Block (IFB)</link>. It lists the
physical interfaces that will have their input shaped using classes
defined on the IFB. Neither the IFB nor any of the interfaces listed
in this column may have an IN-BANDWIDTH specified. You may specify
@ -1783,7 +1783,7 @@ eth1 4 94mbit full 4 default #for
</section>
<section id="IFB">
<title>Intermediate Frame Block (IFB) Devices</title>
<title>Intermediate Functional Block (IFB) Devices</title>
<para>The principles behind an IFB is fairly simple:</para>