QoS: Usenet Download To Have Lowest Priority - Not Working?

Discussion in 'Tomato Firmware' started by EViS, Aug 1, 2011.

  1. EViS

    EViS Networkin' Nut Member

    I am using Tomato v 1.28. My basic settings and classifications are as per Toastman's recommended settings with a couple of modifications (screenshots attached).

    I have an issue with the Download rule. Whether it is set at 80% (as recommend by Toastman) or 100% (my preference to maximise bandwidth), and someone wants to play a Youtube video, the video keeps buffering every 20 seconds and the bandwidth available to the download does not decrease.

    Looking at the graphs, the download and video stream falls within the correct classification. Any idea why QoS may not be working here (i.e. slowing the download to provide more bandwidth for the flash video to play smoothly)?

    Attached Files:

  2. Toastman

    Toastman Super Moderator Staff Member Member

    You might find the latest QOS rule examples would be easier to modify for your needs. (Similar but split into more rules).

    Note - the inbound classes have individual limits. There is no overall limit (the max bandwidth setting is only used to calculate percentages for the individual classes.

    Therefore it is possible for the sum of all the classes to exceed the maximum available incoming bandwidth. Could be that's what is happening here.

    Read through this thread for ideas. The QOS could be improved ... But basically, you can't have your cake and eat it, you trade bandwidth for stability.

  3. EViS

    EViS Networkin' Nut Member

    As I have the Download class set at 100%, I guess that is true, if I lowered this to 40%, then as the Media class is set at 60%, I wouldn't suffer from any problems as described. But as you say, the bandwidth available to the Download class is severely limited. Would this be the only solution though (i.e. setting Download at 40% to make sure 60% is always available to Media)?

    Also, where are these "latest QoS rule examples"?
  4. Toastman

    Toastman Super Moderator Staff Member Member

    There is one thing you might try. Use the BW Limiter to provide the missing overall limit on incoming data.

    Enable the limiter, just use the "default .... for unlisted IP's" - enter the max incoming and outgoing bandwidth - probably best for both rate and ceiling. My experiments were not conclusive but it may help.

    Try setting the limit on incoming bandwidth to say 85% of max.

    This isn't a full ingress solution as there is no priority system to say which classes should be slowed down first ... but it should help stop congestion.

    Be interested to see what it does for you.

    Latest rule examples - they are installed by default after an nvram erase.

    If you do an erase, you'll lose your setup. But read this first:

  5. EViS

    EViS Networkin' Nut Member

    I shall give that a try. Would I keep the Download inbound class at 100%? I'm not sure what you are referring to be set at 85%?

    I did an NVRAM erase (from the tomato settings GUI as opposed to pushing the button the router) before installing your tomato version. I thought the rules were a little limited compared to what was in your example in the QoS thread. Maybe I didn't look at the properly?
  6. Toastman

    Toastman Super Moderator Staff Member Member

    The limits for the default for unlisted IP's...

    Perhaps you are using an old version of the firmware. If you are using a newer router, there are more frequent updates. Get the latest one which will be pushed to the download site in an hour or so - 1.28. Maybe you're using an older GL ... whatever :confused:
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice