What is the problem you're having? All these apps use port 80, 443 and many other ports. Usually, it's the VoIP and video conferencing ports that need to be prioritized over UDP. DSCP is the easiest way to insure that time sensitive packets aren't delayed or dropped (if DSCP is respected). You can also prioritize some ports. Finally, you can use L7 and TLS host to filter the traffic, which I do not recommend.

All these options require marking traffic with mangle and then prioritizing the packets via queues. There's a big thread regarding QoS in the forums and many tutorials on YT.

ROS has no way to identify application data, other than the workarounds I mentioned. The problem is that those workarounds are processor intensive and fiddly to setup even with tutorials.

So port based QoS is usually recommended as the easiest way to avoid congestion for critical applications. This is obviously not perfect, because many applications share the same ports (80, 443, 3478-3482, etc.). Someone kindly took a lot of time to post a very lengthy tutorial in the forums if you take the time to search for QoS. While I am not a fan of prioritizing everything because it degrades performance, it will get you started.

As for DSCP, you can search Google to learn about how it is used in packet headers for QoS with apps that support it. This is the easiest way to insure that proper priorities are respected.

A limit must be set globally somewhere for congestion in the queue structure to have control on which packets are prioritized, which are delayed, which are dropped first and to minimize bufferbloat. It's a trade-off for effective traffic shaping. If you do not set a limit, your ISP decides how to handle those extra packets once you max out your allotted bandwidth. But no, you don't need to set one for each port range or queue within a tree.

As Nate posted while I was typing, you can also use a single SFQ queue to provide a good user experience to all users. Fair queuing can also be mixed with traffic priorities and fasttrack. If one solution doesn't work for your needs, you try something else. However, there's no free lunch: Everything you add requires processing time, so less is always more.

Dynamic speed for each client? Schedulers and queues must have a limit somewhere that is smaller than the physical limit of the connection for QoS. If the connection is never congested (limitless bandwidth), then QoS is not required because any number of packets can be sent or received at the same time i.e. no packet will ever require priority as there are no delayed or dropped packets.

I ended up ditching Queue Tree/Advanced QoS like viewtopic.php?f=23&t=73214 completely.

I use Simple queues like the following:

Code: Select all

/queue simple
add bucket-size=0.01/0.01 burst-time=1s/1s dst=pppoe-out1 max-limit=205M/205M name=ISP1-QoS priority=1/1 queue=default/default target=""

End result is, I can download with 30 threads, watch 8K videos, call, game all simultaneously without any buffering/packet loss.

Borrowed the following from the above guide though:

Code: Select all

# default queue behavior
set default kind=sfq