Remove anachronistic text from the tcinterfaces manpages.

Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2013-11-10 08:19:16 -08:00
parent 6741d087fb
commit 3b5c1ad601
2 changed files with 0 additions and 16 deletions

View File

@ -129,14 +129,6 @@
<emphasis role="bold">external</emphasis> (facing toward the <emphasis role="bold">external</emphasis> (facing toward the
Internet) or <emphasis role="bold">internal</emphasis> (facing Internet) or <emphasis role="bold">internal</emphasis> (facing
toward a local network) and enables SFQ flow classification.</para> toward a local network) and enables SFQ flow classification.</para>
<note>
<para>Simple traffic shaping is only useful on interfaces where
queuing occurs. As a consequence, internal interfaces seldom
benefit from simple traffic shaping. VPN interfaces are an
exception because the encapsulated packets are later transferred
over a slower external link.</para>
</note>
</listitem> </listitem>
</varlistentry> </varlistentry>

View File

@ -129,14 +129,6 @@
<emphasis role="bold">external</emphasis> (facing toward the <emphasis role="bold">external</emphasis> (facing toward the
Internet) or <emphasis role="bold">internal</emphasis> (facing Internet) or <emphasis role="bold">internal</emphasis> (facing
toward a local network) and enables SFQ flow classification.</para> toward a local network) and enables SFQ flow classification.</para>
<note>
<para>Simple traffic shaping is only useful on interfaces where
queuing occurs. As a consequence, internal interfaces seldom
benefit from simple traffic shaping. VPN interfaces are an
exception because the encapsulated packets are later transferred
over a slower external link.</para>
</note>
</listitem> </listitem>
</varlistentry> </varlistentry>