Look what I found, maybe @miau1 is right about his settings, maybe it's the best you can get using traditional QoS and you made fun of them and him, despising that boy just because he has few posts.
When I look at the @miau1 settings, for me they look like Adaptive QoS the truth, you who have never used Adaptive QoS or the @FreshJR script do not know what I'm talking about and more with the explanation he has in post #6, just that Adaptive QoS without @FreshJR script is broken...
If you have not committed sin, then throw the first stone.
When I look at the @miau1 settings, for me they look like Adaptive QoS the truth, you who have never used Adaptive QoS or the @FreshJR script do not know what I'm talking about and more with the explanation he has in post #6, just that Adaptive QoS without @FreshJR script is broken...
If you have not committed sin, then throw the first stone.
QoS
Just a quick warning about something that caught me out. I noticed that I was getting DNS timeouts while browsing whenever my wife was using Netflix. I've never had DNS timeouts before.
This morning "the penny dropped" and I realised that one my QoS rules was now no longer correct since I was using DoT. DNS should have been getting the Highest priority, but as DoT doesn't use port 53 it was defaulting to Low priority (which was below HTTP/S streaming).
Obvious when you think about it . Anyway, here's my updated QoS rule.
Last edited: