Guys,
I have a weird problem with queuing.
Here is a brief description:
- Media server is downloading torrents and connected to bridge interface (home-bridge)
- Laptops are connected to bridge via wifi
- RB model is RB951Ghnd
I need quite a basic setup:
- If no clients are utilizing channel than give all the bandwidth to media server, which is downloading torrents
- If there are clients downloading something from the internet, than give them priority.
I’ve faced unexpected results.
what i actually see:
![]()
Thus server-down has lower priority, it actually utilizes channel more all the time. If I stop server download laptops immediately utilizes all the channel taken by the server downlink.
As far as I understand:
- if a leaf reaches CIR, it should become yellow.
- Leafs with higher priority (e.g. 4) should have a chance to satisfy their maximum rate before leafs with lower priority (e.g. 7).
I suppose this screenshot show the opposite.
Is there something I misunderstand?
I think the yellow / red behavior relates to % of max-limit, not “above CIR” (but I could be wrong there).
I think the torrents are just “pushing harder” since it’s a lot of streams combining to reach that amount of transfer, while the other machines are doing less threading, so they’re just not jumping into the queue as fast - down at the “micro/quantum” level . . .
Basically, even though the queue will service the higher priority queue first, there are just that many more packets coming along to fill the lower priority queue. (the priority determines what order the queues have packets inserted into them, not what priority they have being de-queued… if that makes any sense)
That’s my theory - because I agree with you that the laptops-down queue should be able to run wild once the other two queues have reached their CIR.
I would just try raise the CIR of the laptop-down queue - to something like 60M, since that’s really what you want to do anyway, right?
Also - there’s the possibility that using PCQ type queues on the parent is harming things…