QOS restricting overall speed

Discussion in 'Tomato Firmware' started by Vchat20, Apr 28, 2014.

  1. Vchat20

    Vchat20 Reformed Router Member

    Been trying lately to tackle this little issue I have been having and cannot figure out. Also please bare with me as I try to explain what is going on.

    20/2 cable connection. QOS and other loads off, speed tests from multiple sites are solid and even slightly over provisioned usually around 21/2.5. Did the expected and set both up and down limits to 90% of the rated 20/2 and not the speed test ratings to be safe. Everything else is default. The main case I have seen crop up is if I run a torrent or two, QOS picks it up properly as P2P but despite what else is using the connection, the torrent speed is drastically limited. Sometimes down to 50KB/s on well seeded torrents. Second I turn off QOS it picks back up and saturates the connection. This is with no other connection load. With QOS on and this issue occuring my bandwidth graph barely breaks 5mbit/s down. Turn off QOS and I see it jump again to near full speed.

    Tenda N60 router, tried both bwq518's Shibby fork and Shibby's own firmwares to the same effect. CPU load even with torrents and QOS going is really low, within .10-.15. 64MB ram with consistently about 40MB free. From a resource standpoint it seems to be humming along beautifully. And other than an odd VLAN configuration issue on clean nvram that is easily fixed, I haven't had any bugs to speak of.

    Is there anything else I am missing that could cause this? Is it supposed to work like this? Other QOS implementations I have run into all assume under normal conditions even P2P/Bulk class data can saturate a connection if nothing else is using it. Once something else takes priority like web, voip, or video, P2P/Bulk data backs off just enough for those applications to function.
  2. Porter

    Porter LI Guru Member

    Thanks for the detailed report!

    The first thing I can think of is whether the class your p2p traffic gets into has enough bandwidth. On the QoS/Basic-page each class has a left an a right bandwidth percentage. Look at the right value and make sure your p2p class is allowed to use enough bandwidth, maybe around 80%.

    If this doesn't help, please post some screenshots of QoS/Basic and Classification so that we can rule out a configuration issue.
  3. Vchat20

    Vchat20 Reformed Router Member

    Thanks. It's really odd. I bumped up the right side bandwidth limit for P2P on both in and out to 90% and am still getting the crawling speed when QOS is turned on. I've attached a couple extra screenshots. It seems to be accurately marking P2P in the right classification which should be wide open.

    Screenshot (2).png Screenshot (3).png

    This particular go-round with QOS off I had one torrent running somewhat slowly but was pulling in about 250KB/s inbound. Second I turned on QOS it dropped to about 10KB/s.
  4. Porter

    Porter LI Guru Member

    You forgot to include a screenshot of QoS/Basic. :/

    So far it looks pretty normal, but the last filter could be the cause of your problems. Depending on which bittorrent client you use uTP is being used, which is UDP traffic. If your Crawl class only has a few percents of bandwidth, as it probably has in the default settings, this might be the cause of your low speeds. Just guessing, because the screenshot is missing. The option you need to change is on QoS/Basic and called "No Ingress QOS for UDP". Untick the box and see how it works.
  5. Andy_113

    Andy_113 Networkin' Nut Member

    Not sure if changing "No Ingress QOS for UDP" setting will change anything, i've got a similar setup udp isn't used for most of the torrent transfers if i remember correctly. Maybe wrong ofcrouse.
  6. Porter

    Porter LI Guru Member

    As I already mentioned this depends on you bittorrent client. Uttorrent makes heavy use of UDP.
  7. Andy_113

    Andy_113 Networkin' Nut Member

    sorry, You're correct, just took another look at my settings. utorrent is the client used, but i have manual port-forwards and QOS rules for both tcp and udp in the QOS Classifications page.

    which would explain why "no Ingress QOS for UDP" setting wouldn't make much difference.
  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