From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wingtung.Leung s965817@uia.ua.ac.be
Date: Fri, 24 Nov 2000 21:37:23 +0000
Subject: SV: [LARTC] Bandwidth limiting
Message-Id: <marc-lartc-98373938216975@msgid-missing>
List-Id: <lartc.vger.kernel.org>
References: <marc-lartc-98373938216960@msgid-missing>
In-Reply-To: <marc-lartc-98373938216960@msgid-missing>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: lartc@vger.kernel.org

<PRE>On Fri, 24 Nov 2000, Thomas Habets wrote:
&gt;<i>
</I>&gt;<i> Why can't it just be like:
</I>&gt;<i> iptables -t shaper -A OUTPUT -s 1.2.3.0/24 --maxspeed8Kbit -j SHAPE
</I>&gt;<i>
</I>
Because iptables is used for firewalling (packet filtering) functions and
tc (and ip) handle queuing and routing.

There is an options for iptables to limit rate (check the man page), but
if you need &quot;the real stuff&quot;, I suppose tc is the way to go. It supports
more flexible setups. Too bad we are still missing a extensive reference
for tc, but Daniel is working on it.





</PRE>