[no subject]

tc qdisc add dev eth0 root handle 1: cbq avpkt 1000 bandwidth 100mbit

tc class add dev eth0 parent 1: classid 1:1 cbq rate 64kbit allot 1500
prio 5 bounded isolated

tc filter add dev eth0 parent 1: protocol ip prio 16 u32 match ip dst
0.0.0.0/0 flowid 1:1

It has been my experience that the limiting is not exactly at 64kbits
(or it might be a problem at higher limits) so you might have to
change it to get it to work at the right speed.  Once you do find the
right limit, it does stay under it.  Also this only affects outbound
traffic, but you can make it affect inbound with more tc filter rules.
If the interface on the sending side is rate limited though, then I
wouldn't mess with the inbound limit.


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00340" href="msg00340.html">[ale] Ethernet bandwidth choker</a></strong>
<ul><li><em>From:</em> Dow.Hurst at mindspring.com (Dow Hurst)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00327" href="msg00327.html">[ale] Ethernet bandwidth choker</a></strong>
<ul><li><em>From:</em> dcorbin at enttek.com (David Corbin)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00328.html">[ale] Ethernet bandwidth choker</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00330.html">[ale] [OT] Voicepulse question</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00328.html">[ale] Ethernet bandwidth choker</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00340.html">[ale] Ethernet bandwidth choker</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00329"><strong>Date</strong></a></li>
<li><a href="threads.html#00329"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>