1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

QOS Bug in Tomato 1.13?

Discussion in 'Tomato Firmware' started by jbaker6953, Jan 24, 2008.

  1. jbaker6953

    jbaker6953 LI Guru Member

    I have set up the following QOS rules:
    Code:
    TCP/UDP, any address, any port, 0 - 512k HIGHEST
    TCP/UDP, any address, any port, 512k+    E
    Class E has an inbound limit of 4% of a 3Mbit connection. No matter what size file I download, the download continues full bore the entire time. If I get rid of the size and just make one rule to match everything to class E, the download is indeed slow as expected. It just appears that QOS isn't paying attention to the size setting. Am I missing something?
     
  2. jbaker6953

    jbaker6953 LI Guru Member

    I see the problem. It only measures outgoing bytes. I can't make a rule that applies after X incoming bytes. The rules really shouldn't say "transferred" because what they really mean is "uploaded." Downloaded bytes are also part of "transferred."
     
  3. jbaker6953

    jbaker6953 LI Guru Member

    I am using SSH to proxy HTTP requests. I have a QOS rule that limits the speed of HTTP downloads at the bottom of the QOS rules. Above that I have my computer as an exception, which works well. I cannot figure out how to make an exception for connections the router initiates to Web sites while acting as a proxy for the SSH client. I tried using the source MAC of the WAN, LAN, and WiFi interface, the LAN IP address. None of them work. If I use the WAN IP address, the exception works. Why does Tomato ignore the source MAC, but not the source IP of the router?
     
  4. siimo

    siimo LI Guru Member

    Uncheck prioritize ACK on the QoS page.
     
  5. jbaker6953

    jbaker6953 LI Guru Member

    That has always been unchecked. I'm not sure though how that will allow QOS to identify outgoing connections based on the WRT54's MAC address.
     
  6. Tremelune

    Tremelune LI Guru Member

    From what I've read, incoming QoS doesn't do what you want because it doesn't limit the amount of data traveling down the pipe, it drops some of it when it gets to the router. You drop packets after it gets through the bottleneck (net connection). In other words, If someone is trying to download a huge file, they'll still be pulling down tons of data, even if they're throttled in Tomato to only receive a fraction of that data at a time...

    It may make things worse, because the user will just request the same data over and over until it eventually gets through.

    Someone please correct me if this is inaccurate.
     
  7. mstombs

    mstombs Network Guru Member

    I'm sure you are correct Tremelune, but by controlling the "acks" you can pace the incoming data - in cable connections this is often done by the cable modem - the data comes in fast bursts.

    There is Linux software "rshaper" to rate limit downloads per IP

    http://freshmeat.net/projects/rshaper/

    This is available via the web gui in Acorp ADSL routers and by kernel module add on in Routertech firmware. Only issue I can see for Routertech is how it would integrate into the existing QOS scheme.
     

Share This Page