QOS Classification Issues with Tomato

Discussion in 'Tomato Firmware' started by TheReck, May 8, 2013.

  1. TheReck

    TheReck Reformed Router Member

    Hi Everyone,

    I've been running Tomato 1.23 for several years now on an Linksys WRT54G. I'm now needing to setup QOS due to the kids are starting to use ALOT of bandwith. I've read alot about this and feel I have a pretty firm grip, but I'm having issues with ports not being classified as I have requested. For example, some of my Port 80's are classified properly and others are listed as "Unclassified" in the "View Details" QOS menu.

    Any thoughts on this?
  2. Marcel Tunks

    Marcel Tunks Networkin' Nut Member

    Recent builds have improved QoS. Reasonable settings are pre-configured in Toastman and Shibby flavors of Tomato, just fill in the bandwidth data and click "enable".
  3. Monk E. Boy

    Monk E. Boy Network Guru Member

    Yes, I would definitely give a newer version of Tomato a shot, 1.23 is really quite old. Even when I was running Tomato on a WRT54GL I was using 1.28. Even when I was really evangelizing WRT54GLs and getting a lot of people over to them I was using 1.26 and 1.27. There are some bugs and quirks in earlier versions, plus some exploitable vulnerabilities (some rather serious).

    You will need to long erase NVRAM & setup the router from scratch though, doubly so if you upgrade to something newer like Toastman or Shibby. I create a simple text file that walks me through each and every page, based on what I had set on that page before flashing the router. After flashing, and after long erasing NVRAM, I simply walk through the text file from the top down and put everything back to how it was. It sounds like a major pain but really it only takes about 15-20 minutes to create the file and less than 5 minutes to put it back in. You can use copy & paste for anything exotic like Advanced DNS/DHCP or Scripts or, really, almost anything.

    All that being said, the unclassified port 80 traffic should be connections from your system to the web server on the router. All connections from clients to services running on the router are unclassified and not subject to QoS. If you intercept DNS traffic (highly recommended) then you'll see unclassified port 53 connections as well.
  4. TheReck

    TheReck Reformed Router Member

    Yes, I suspected an upgrade was in order. As I said, I've been running Tomato for a while. Monkey E. Boy, I need a little clarification on the unclassified traffic. Can you explain in more detail what you mean by a Webserver on the router? I didn't realize that there were services that were directed only to the router, not the internet. I guess I could see where DNS would be a service directed only to the router, but why port 80?

    My goal is to try and get control of my son's Steam downloads that appear to me to be port 80 services. I've got control of the TCP/UDP ports that Steam uses, but that appears not to be where the actual download traffic is occurring. My best guess right now is either port 80 or the DNS port 53 (P2P). The thought is that if I put a limit on the access of these ports when they reach above 512KBS I'll be able to throttle the bandwidth...
  5. Toastman

    Toastman Super Moderator Staff Member Member

    One obvious cause - when you connect to the router's GUI (webserver) on port 80 you will usually see about 20 unclassified connections show up. Other things perhaps running on the router - ftp/samba/ssl etc ... depending on how you have it set up.
  6. Monk E. Boy

    Monk E. Boy Network Guru Member

    Yup. You literally viewing the website on Tomato to look at QoS, etc. is opening port 80 connections to the router, which then show up as unclassified connections.
  7. TheReck

    TheReck Reformed Router Member

    OK, guess you should have said - Duh,

    Have you had any luck with the classification changing once the data transfer goes above a certain value? This is the main key to my strategy to get a hold of Steam. On the version of Tomato (1.23) I'm running, it doesn't seem to work. I've set TCP/UDP Port: 80,443 changing classification when Transferred: 513KB+. But it doesn't ever change classification. Also, what triggers the classification to change back when the data transfer goes below 513? This seems unlikely to me..
  8. Monk E. Boy

    Monk E. Boy Network Guru Member

    It might be a bug in 1.23, I have stuff jump between classifications all the time.
  9. Porter

    Porter LI Guru Member

  10. Toastman

    Toastman Super Moderator Staff Member Member

    You do know the classification change you want to happen when you enter a limit, applies to "OUTGOING" data, not incoming? And it doesn't change back, once it's sent that data and iot exceeds what you enetered, the class will change.
  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