[no subject]

> It is very versatile.
Yes, the rate limiting (frequently called "Traffic Shaping") is very
versatile.  One can specify what rule (shape or bandwidth) to apply to
any combination of source and destination IP/netmask, source and destination
protocol and port numbers.  I've used it rather successfully for clients.

> Dow
Bob


> Michael Still wrote:

> >On Wed, 8 Dec 2004 06:45:41 -0500, David Corbin <dcorbin at enttek.com> wrote:
> > 
> >
> >>I need a device that I can use to simulate low-bandwidth between two 
> >>ethernet
> >>machines.  Ideally,  the box would have some limited interface to enter 
> >>in  a
> >>desired bandwidth to simulate.  Something that works in increments of 
> >>64kbs
> >>would be fine.
> >>
> >>1) Is there a correct name for such a product.
> >>2) Any recommendations?
> >>
> >>   
> >>
> >You can do this with rate limiting between ethernet interfaces I
> >believe.  Here's an example you can play with:
> >
> >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.
> >_______________________________________________
> >Ale mailing list
> >Ale at ale.org
&gt; &gt;<a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
&gt; &gt;
&gt; &gt; 
&gt; &gt;
&gt; _______________________________________________
&gt; Ale mailing list
&gt; Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--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>
<li><strong><a name="00329" href="msg00329.html">[ale] Ethernet bandwidth choker</a></strong>
<ul><li><em>From:</em> stillwaxin at gmail.com (Michael Still)</li></ul></li>
<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-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00343.html">[ale] OT: replace your motherboard, buy XP again</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00345.html">[ale] ALE CENTRAL for 12/9/2004: A Polar Penguin Meltdown at	Melton's</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00340.html">[ale] Ethernet bandwidth choker</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00371.html">[ale] Ethernet bandwidth choker</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00344"><strong>Date</strong></a></li>
<li><a href="threads.html#00344"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

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