The reason to keep the speed limit under the actual connection is more of a latency issue. The reason to do it is so you keep the queue on your server and thus can guarentee lower latency for certain things. From the sound of youe setup, a 2:1:1 ratio split, the latency thing isn't really an issue at all. I don't see why you couldn't just keep it as the actual connection bandwidth.
Please say what didn't work instead of just saying "didn't work as expected" or "No shaping." Give some detailed output that you're basing this statement on.
My best suggestion on the limited information would be to mabye set it up with a root class of 256kbit, then setup the child classes as 120-60-60 with borrowing. In my own usage, leaving some free bandwidth that every subclass has to borrow from seems to work better than assigning it all.
Also, are you basing the drop from 30KB/s to 26KB/s off measured transfers or just calculating the bandwidth. If you haven't tested your actual bandwidth without HTB active I'd suggest doing that.
- Jody Shumaker
On 11/2/05, Vlada Macek <tuttle@xxxxxxxxxxx> wrote:
One more to my previous posting:
What I want to get is to not let any of the three regions to dominate
the line and to maintain the 128-64-64 bandwidth ratio. I'm not
concerned in the ceil (limit the region's upload/download when the line
is free), I wish free borrowing.
Isn't there any other method instead of HTB, not suffering with the 15%
bandwidth loss, that would be capable of bringing me what I want?
Thanks,
VM
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
