Hello,

I think the easiest and most robust way to shape ingress traffic for you
would be to do it on the LAN side.
If you have multiple interfaces facing LAN then use ifb.
I've never used it myself, but to mark multiple address ranges the
easiest way would be to use iptables with ipset - there will be many
examples to be found on the internet.
Even if you do mark (well set dscp cs1) for steam servers you will still
need to be backed off from your ingress rate enough or it still won't
work as the queue will build up too much on the ISP side of the
bottleneck. Shaping ingress is quite different to doing egress as you
are at the wrong end of the bottleneck.

In my case switch0 should work for the LAN, just wondering if setting cake on both pppoe0 (for outbound traffic) and switch0 (fro inbound traffic) at the same time should work without issues? Hmm, probably gonna try it and see if it does. I'm gonna look up iptables and ipset and see what I can find, thanks for the help.

Also I have done some more testing, I was able to limit Steam connections just to one thanks to some console commands ("@cMaxContentServersToRequest" and "@cCSClientMaxNumSocketsPerHost") and while the situation improved (no more packet loss, latency variation within 10ms, but still seeing ping spikes of ~50ms) it's still not what I'd consider ideal, which would be like with any other download. So my guess is there's something else going on other than just the multiple connections, which are definitely big part of the problem but not the only thing.

Anyway these are my current settings for Cake and I've been using them for the last four days without issues:

qdisc cake 8005: root refcnt 2 bandwidth 950Kbit diffserv3 triple-isolate nat wash rtt 100.0ms atm overhead 40 via-ethernet
qdisc cake 8006: root refcnt 2 bandwidth 17500Kbit diffserv3 triple-isolate nat wash ingress rtt 100.0ms atm overhead 40 via-ethernet

I will try Andy's suggestions and see what I can do.

@Sebastian No problem, I tested your updated script and it is indeed reporting overhead 40. 

On 25 April 2017 at 12:26, Andy Furniss <adf.lists@gmail.com> wrote:
Dendari Marini wrote:

FWIW here's a quick example on ingress ppp that I tested using
connmark the connmarks (1 or 2 or unmarked) being set by iptables
rules on outbound connections/traffic classes.


Unfortunately I'm really not sure how to apply those settings to my
case, it's something I've never done so some hand-holding is probably
needed, sorry. At the moment I've limited the Steam bandwidth using
the built-in Basic Queue and DPI features from the ER-X. They're easy
to set up but aren't really ideal, would rather prefer Cake would
take care about it more dynamically.

Anyway about the Steam IP addresses I've noticed, in the almost three
weeks of testing, they're almost always the same IP blocks (most of
which can be found on the Steam Support website, https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711).
I believe it would be a good starting point for limiting Steam, what
do you think?

 I think the easiest and most robust way to shape ingress traffic for you
would be to do it on the LAN side.
If you have multiple interfaces facing LAN then use ifb.
I've never used it myself, but to mark multiple address ranges the
easiest way would be to use iptables with ipset - there will be many
examples to be found on the internet.
Even if you do mark (well set dscp cs1) for steam servers you will still
need to be backed off from your ingress rate enough or it still won't
work as the queue will build up too much on the ISP side of the
bottleneck. Shaping ingress is quite different to doing egress as you
are at the wrong end of the bottleneck.