QoS + Download Manager question

Discussion in 'Tomato Firmware' started by robst3r, Mar 10, 2010.

  1. robst3r

    robst3r Addicted to LI Member

    Hi all,

    I have nearly got my QoS set up and performing how i want it to apart from one thing which is driving me nuts. I have traffic up to 196kb set up for ports 80,443 in a high browsing class, and traffic +196kb set to drop to a lower class to avoid taking up too much browsing bandwidth.

    After testing the setup i found that after the 196kb threshold is reached, QoS throttles back the connection and changes class which is obviously correct whilst using the Firefox default built in download utility. I have noticed that when using a download manager, the class does not switch down and ends up staying in the browsing class which impacts other services. I have checked the destination ports in use on the graphs, and port 80 is being used in exactly the same way.

    I also use Miro (for mac), and i can download content using this fine and it switches classes correctly. Does QoS handle download managers differently than normal http traffic? and if so how do i configure QoS to switch this traffic into a lower class if the bandwidth threshold is reached?

    Many Thanks
  2. Toastman

    Toastman Super Moderator Staff Member Member

    I think this is what is happening. The QOS counts traffic per outgoing connection to determine when to switch to the lower class. but when you use a traffic manager, it may open, for example, 10 connections with the server to download the file. Now each connection has to reach 196k before switching. The download may be over before this happens.
  3. robst3r

    robst3r Addicted to LI Member

    Hi Toastman, thanks for the info. I had a feeling that it would be something to do with the amount of connections the dl manager used (just wasn't sure how qos would handle it), so after reading your post i lowered the kb transferred threshold by quite a bit, and it now works:thumbup:

    Many Thanks
  4. Porter

    Porter LI Guru Member


    I have a somehow similar Problem with QoS and my downloads. To keep things and connections simple, I used normal one connection Firefox-DLs for my experiment. For some reason the first http-DL I start ends up in the correct class, but the second http-DL needs to see several MB of data before the classification actually works. The classification rule is the standard http-DL rule, only that I decreased the matching size from 512KB to 256KB.


    Any suggestions?

    The second problem I encountered was the rather inaccurate inbound limit. My connection delivers 4500Kbit, so I thought, I should probably put it on 4000Kb to be on the save side. This didn't work, only setting the inbound Limit to 3000Kb worked to see good ping times. On the other hand classification of P2P traffic is quite accurate. Why is the inbound limit so inaccurate then? Please don't just tell me, that this ist how inaccurate inbound QoS generally is. I had a Linux-Router on a real PC for a few years, that used MasterShaper: http://www.mastershaper.org/index.php/MasterShaper which gave me considerably better results.


    Is there some way of watching every iptables and tc command Tomato issues to do QoS? I'm certainly not an expert when it somes to using tc, but I coulnd't find any tc rules for the inbound interface eth0. Knowing them I could check how my old trafficshaping rules differ from the ones Tomato uses.

    Thanks for your help,
  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