At the bottom of
http://wiki.shorewall.net/wiki/ContributingToDevelopment there is the
suggestion that you accept patches to the XML sources.
http://www.shorewall.net/traffic_shaping.htm makes reference to
"Intermediate Frame Block (IFB) Devices". My kernel 2.6.31.6 refers to
"Intermediate Functional Block support". That is, I think "Frame"
should be "Functional".
Regards
Fog_Watch.
Index: traffic_shaping.xml
===================================================================
--- traffic_shaping.xml (revision 10079)
+++ traffic_shaping.xml (working copy)
@@ -135,7 +135,7 @@
to make sure, that different data streams are handled equally.</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>
@@ -389,7 +389,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
@@ -1259,7 +1259,7 @@
</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>
------------------------------------------------------------------------------
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
