FQ_Codel Limit and Steam Downloads
-
Hi,
I'm having a problem with my limiter not keeping my latency at bay when downloading on Steam. My understanding is that Steam downloads are very network heavy, using a lot of threads to download. I have attached my settings.
I've tried tweaking with the settings, including the default settings. Nothing seems to help. I've tried lowering the bandwidth thinking I set it too high, and that didn't help either. This is even happening when I limit my steam download speed way below my connection speed, so I don't think its a bandwidth issue. Does anyone have any insight? I've attached my limiter IN queue/ floating rule setup.
-
I think you have the upload and download queue the wrong way round in the floating rule. Put the download queue where you have the upload queue and the upload queue where you have download.
Am not expert, so would love to hear if this works for you.
-
Otherwise. Put the limiter directly in the relevant interface pass rule. I find the interface rules easier to deal with than floating.
-
@jeremyj After looking at multiple guides and switching them around, it did not work. I immediately noticed the bandwidth limit was uncapped when I swapped them and the ping was way worse. So It's back to how it was.
Maybe this is just an issue with Codel and how steam downloads things? It's only Steam that does this.
-
@brswattt some further comments. I would suggest you set the "queue management algorithm" to coddle in both the limiter (parent) and the child queue. You've set the scheduler but not the QMA.
Also, presumably you initiated the connection to steam. In which case I think you need to apply the rules on the LAN. I suspect that is the problem. If not, I would mark the rule to to be logged and then look at the firewall log and make sure your rule is triggering correctly. If not, work out why. You seem to be aware of the need to sometimes set quick actions on the floating rules to make the fire immediately but it could be something like that (though not from the looks of things).
As an aside, I would avoid using the floating rules and the WAN until you have this set-up right on the LAN itself. I say this because it is just easier and, as NAT is applied before the rules apply on the WAN, there can be problems writing rules that hit the packets intended. The workaround is tagging packets on the original interface before they hit the WAN then searching for the tagged packets. But the point is avoid applying stuff on the WAN and via floating rules until it is right on the interface rules.