TomatoUSB

I've noticed an issue with my QoS leaving connections "unclassified".

Earlier today, my phone was sending a 10mb email rather slowly, when I noticed in tomato (1.28 shibby running on asus ac68) the qos was mysteriously allocating the connection to class 10 (default class) via the outbound connections qos graph. However, when I clicked to view the class 10 detail, the phone's traffic wasn't actually shown. It's neither in class 5 (where it should be). When I clicked transfer rates I could see my phone uploading at ~100KBps to the hotmail server (class 10 cap), but when I clicked view details I could see the connection unclassified.

I have included pics of my settings and the detail. The upload was being sent to port 443, which should hit class 5 as its set to include any traffic >512kb with dst ports 80,8080, & 443. If it is lower than 512kb it should hit class 2. I also noted a laptop uploading to dropbox encountered the exact same problem.

Can anyone help me figure out why this traffic is defaulting to class 10 yet showing as unclassified? I would like this upload traffic properly classified to class 5 as to allow a more gentle cap. The default class is meant to catch torrents. Link to pics imgur .com/a/AGV52

Thanks,

Could your upload be using UDP ? Your rules specify only TCP.
Since both rules contain 512kb you might want to change the high end rule to 513kb+ instead of 512kb+
Maybe the router gets to 512kb and has an "Oh Shit" moment when two different rules are simultaneously matched.

http://imgur.com/a/AGV52#vykRXAI

I switched the rule to 513+ and udp/tcp, but after rebooting the router and testing with an upload to hotmail I received the same results as before. Also, in the very last picture I had attached, it shows the router identifying the connection as TCP - so I'm not sure how much the protocol is to blame.

Any other suggestions? I think I will revert the rule back to 512kb+ as I've seen a lot of setups using the same number as max and min for different rules.

Thanks,

Also, in the very last picture I had attached, it shows the router identifying the connection as TCP

I see only two screen shots in your link. The third only shows an IP address in giant font. The protocol is not the issue as you have shown.

I happen to use QOS quite a lot and since my first quantity based rule ( 8 or 9 years ago ? ) have always modified the tiers to touch, not overlap. Seems more logical to me, and has always worked.

There have been some recent QOS functionality snags with the newer hardware and firmware releases. I do not posess any of the models in question so have not followed the story very close. I do recall seeing some comments that the snags have been remedied in the newest releases.

You may want to research the current status of your hardware / firmware to be sure it is indeed functional. Sorry I'm so thin on details. For now you can apply conventional trouble shooting techniques. I would start with a fresh NVRam clear and a very basic config with just one single rule to match your test packets. If you can get the stream to match the rule then add other rules until you are back to where you want to be. I'm afraid tax season is eating into my play time, but if you are still stuck in a day or two from now I'd love to help you tackle it.