I don’t think that makes any sense. The Gaming Rule is meant to be used to include the local IP of the gaming device. I don’t know how you’ve decided all these odd modifications to it. Maybe a fellow gamer will come to your aid soon.
I don’t think that makes any sense. The Gaming Rule is meant to be used to include the local IP of the gaming device. I don’t know how you’ve decided all these odd modifications to it. Maybe a fellow gamer will come to your aid soon.
That’s fine, working as designed. As defined in your screenshot, the Gaming Rule takes Untracked traffic (mark 000000) that is not http/https traffic (ports 80,443) and puts it in Gaming. Traffic that is already classified by Adaptive QoS (e.g. Sony PlayStation) is unaffected by the Gaming Rule.Gaming rule is just a classification right?
Also the exclusion rule for !80,443 is not working as I see port 443 in the gaming traffic
Would putting the packets net control change anytning? Would that be first in the queu?That’s fine, working as designed. As defined in your screenshot, the Gaming Rule takes Untracked traffic (mark 000000) that is not http/https traffic (ports 80,443) and puts it in Gaming. Traffic that is already classified by Adaptive QoS (e.g. Sony PlayStation) is unaffected by the Gaming Rule.
I allocated 90% bandwidth to gaming however, should I be leaving net control with any?That’s fine, working as designed. As defined in your screenshot, the Gaming Rule takes Untracked traffic (mark 000000) that is not http/https traffic (ports 80,443) and puts it in Gaming. Traffic that is already classified by Adaptive QoS (e.g. Sony PlayStation) is unaffected by the Gaming Rule.
Yes, Net Control is always the top priority.Would putting the packets net control change anytning? Would that be first in the queu?
I don’t think Gaming needs that much absolute bandwidth. What is you upload / download?I allocated 90% bandwidth to gaming however, should I be leaving net control with any?
The game plays better IMO when allocated more bandwidth .Yes, Net Control is always the top priority.
I don’t think Gaming needs that much absolute bandwidth. What is you upload / download?
How do you identify/ isolate the traffic in the connection list?Question - since call of duty is pulling 443, and obviously for gaming we don’t want 80 or 443, can I reclassify the call of duty traffic?
Not if you have no way to identify it as Call of Duty traffic. In your earlier screenshot, is it all the Sony PlayStation traffic on port 443 that you’re referring to as this Call of Duty traffic? You could add the Game Downloads rule to take Gaming traffic on ports 80 and 443 and move it to File Downloads or whatever class you choose. But it depends how it is identified currently in the list.Nvm ur right…. Any way to make “call of duty” not be prioritized when it’s using port 80 or 443?
So identify it in the iptables for both 80,443 as games downloads.Not if you have no way to identify it as Call of Duty traffic. In your earlier screenshot, is it all the Sony PlayStation traffic on port 443 that you’re referring to as this Call of Duty traffic? You could add the Game Downloads rule to take Gaming traffic on ports 80 and 443 and move it to File Downloads or whatever class you choose. But it depends how it is identified currently in the list.
I’m suggesting to add back the Game Downloads rule from the Well-Known rules list. I don’t know if you’ve done that or not. There would be nothing to do in the AppDB section.So identify it in the iptables for both 80,443 as games downloads.
rhen what do I do in the app section?
Unless you are having incredible lag issues (or you are maxing your upload or download while gaming) not much of any of this will make a difference. And unless you are a professional (in which case you’d be using a pc) then the difference won’t do much for you, and even as a pro it may not.So identify it in the iptables for both 80,443 as games downloads.
rhen what do I do in the app section?
Upload traffic through the VPN will be classified in one Class (File Downloads by default). Download traffic will be classified correctly because it happens at br0.what happens if you run FlexQoS + a VPN by default? Does it break things like with cake
Not sure I follow, but since you have a wildly fluctuating ISP bandwidth, you really need to keep the QoS bandwidth tightly aligned with your actual bandwidth in order to control the bottleneck.It might be better for me to set bandwidth per application in an absolute sense rather than as a percentage of a global unknown bandwidth. Could I do that by setting global bandwidth to 100Mbit/s and then setting maximums? Or would that not work?
I don’t think you’re going to find a good answer to your issues. Your network is built on quicksand, and you can’t reliably control bufferbloat and latency via your router if you can’t reasonably predict your ISP bandwidth.Is FlexQoS a good fit in my circumstances? I'd value your thoughts and any suggestions for how to implement / experiment if it might be a good fit.
Not to my knowledge.It would be great to have QoS kick in @ 30Mbit/s only when Teams or Zoom traffic is detected, since I can live with the bufferbloat otherwise. Would that be feasible?
current configurationI’m suggesting to add back the Game Downloads rule from the Well-Known rules list. I don’t know if you’ve done that or not. There would be nothing to do in the AppDB section.
If you want any further help, you need to start providing more details about your tracked connections. I’m tired of guessing your situation. It’s all coming back to me now…
Does that give you the results you want?current configuration
I don’t want game downloads to be prioritized as it’s not optimal for gameplay.Does that give you the results you want?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!