dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
75

random
@teksavvy.com

random to Cloneman

Anon

to Cloneman

Re: Tomato QoS major bug (all versions, incl toastman, shibby)

You have a case for #1.

Highest should not be 10% to 100%. The amount should be a small percentage of total upload available. It should be only the most important. e.g. VoIP. The amount is reserved EVEN when it is not being used at the moment, so it is not available for everything else. So if you take off 100kbps, then all you have left is 900kbps for everything else.

Then you work you way down the priority. I hope your numbers add up.

There are FAQ and long discussions on the official sites specifically talking about this.
Cloneman
join:2002-08-29
Montreal

Cloneman

Member

said by random :

There are FAQ and long discussions on the official sites specifically talking about this.

And all of them are wrong, including you. Here are new settings that would adhere to your requirements, and they would not work either.



only 13% is reserved in this scenario, the others are maximums.

Gone
Premium Member
join:2011-01-24
Fort Erie, ON

Gone

Premium Member

You have your outbound limit set to 1000kbit/s. You are aware that it should only be set to 80-90% of your upstream limit, right? This means your actual upstream is 1100-1200kbit/s? That doesn't sound right. Not limiting the upstream correctly can produce results exactly like what you described.

If you're talking incoming traffic, forget about QoS. It's just not worth the time.