<br><font size=2 face="sans-serif"><snip></font>
<br><font size=2><tt>I know that you can't really shape inbound traffic,
but I think the <br>
killer shaper would start delaying TCP traffic as soon as total incoming
<br>
bandwith utilization hits 75%. Unless somebody floods your link, it <br>
should work pretty effectively.<br>
</tt></font><font size=2 face="sans-serif"></snip></font>
<br>
<br><font size=2 face="sans-serif">Yeah that's what is going on in my scripts.
I sacrifice ~ 25% bandwidth in hopes of becoming in charge of the bulk
of queueing (instead of the ISP). It actually makes a big difference, in
my tests. I was able to soak upload and download and still run Citrix and
Video and VoIP smoothly. If I didn't back off the speed, it was horrible.
So IMO it is truly worth the sacrifice in bandwidth.</font>
<br>
<br><font size=2 face="sans-serif">-Ron</font>