I've been setting up QOS (shibby 128 on an RT-AC68U), and I started by deleting a bunch of the default rules, then putting IP-based rules in the first several rule slots:
From 192.168.0.66 TCP/UDP VOIP/Game phone 1 From 192.168.0.67 TCP/UDP VOIP/Game tablet 2 From 192.168.0.69 TCP/UDP Media lenovo 3 From 192.168.0.68 TCP/UDP Remote htpc 4
Basically, I'm saying that my phone and tablet will never be doing anything that hogs bandwidth, and will often be doing something (VOIP) that is important. My laptop is next most important, and my htpc is next. Then at the very bottom, underneath the collection of default rules that I did keep (stuff like mail, SSH, etc.) I put in a rule for my home server, which is the only machine that's involved in P2P:
From 192.168.0.50 TCP/UDP P2P/Bulk server 35
If I'm understanding correctly, the results should be that the first four machines named will have ALL of their traffic prioritized by the first four rules. Anything involving the server will first run through the default rules to pick out particular services, and then anything that's left from the server will get a low priority.
However, what I'm seeing in QOS Details is that only Rules 1-5 fire. (Rule #5 is DNS, port 53). From Rule 6 (Time, port 37) onward, none of the rules fires, including the IP-based rule #35 for my server. All of my server traffic except DNS ends up Unclassified. Also, there are many Unclassified connections involving the other machines, many of which seem to be to ports in the 7000 range on the router itself (destination 192.168.0.1), but many others as well.
I could delete all of the rules and start adding them back one at a time, but I thought I'd post this first to make sure my understanding of how this is supposed to work is sound. QOS should be starting with Rule 1 for each packet, and going downward until something fires or it falls off the end of the list (Unclassified), correct?
Related question: how can I specify IP ranges? For instance, if I want to de-prioritize any guests that are connected in my DHCP range.