You're missing the point, add what you want to work to the list, do not add uTorrent. Try the new uTorrent version that is out, it may help with browsing while torrenting. Leaving the QoS list blank doesn't provide any benefit if your goal is to have applications you use run smoothly while also torrenting, adding only uTorrent to the QoS list(DON'T DO IT) even at lowest priority will make it highest priority over all other non specified traffic. ONLY add applications(NOT uTorrent) you want to run smoothly to the QoS list!
are you saying autoclass has only 8 ranks or is it really total 8 possible apps? if the latter is true then qos for B1 firmware has really been gutted, since A1 rev has unclassified traffic ranked at 128 out of 256 total with both ip and port ranges. assuming you shut off autoclass, which of course you would need to do if you want to handle the queue with custom settings. so anything 129 and above will get demoted, this is how my setup works since I need ranking in both directions, you should be able to see a ranking entry per connection in the logs.
it's also logically more efficient in this case, if torrent traffic is the only major factor of consumption, because it's easier to isolate. I wouldn't really consider relying on utp, especially when dealing with multiple clients, because it doesn't actually know what the limits are, and can only react to saturation after it's already affected your connection.
I have a 8Mbit/512Kbit cable modem connection. If I set uTorrent with no limit on upload speed I find that all my other activity slows down. If I limit the upload to 30 KByte/second it's fine. I know the downlink is not at fault because it never runs at capacity.
How do I configure the DIR-825 (Rev. B1 firmware 2.02NA) QoS Engine to prioritize the uTorrent upload activity to be the lowest?
All the torrent activity comes from one dedicated machine so I've set a QoS rule:
Local IP Range: 192.168.0.3 to 192.168.0.3
Remote IP Range: 0.0.0.0 to 255.255.255.255
This doesn't seem to have any effect. I've tried it with Automatic Classification on and off. And I've tried setting the Uplink Speed to my true speed (512) and even lower (384). None of these seem to do anything.
any particular reason you need to do it through the hardware instead of using the client limiter? it's much easier that way for a single client, there's really no point to it unless you need to delegate these resources among more than 2 clients or apps. turning off autoclass and setting an uplink speed is really all you should need to do besides the actual ranking, so it must be something else.
*unless you are totally getting shafted by your isp, because if you come anywhere near your cap it would of course cancel out your own queueing. you should try even lower than 384, start with 256 and work your way up. this is really sensitive to your global cap, that's just the way qos works.