From: Andy Furniss <adf.lists@gmail.com>
To: Dendari Marini <dendari92@gmail.com>,
Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Getting Cake to work better with Steam and similar applications
Date: Tue, 25 Apr 2017 11:26:58 +0100 [thread overview]
Message-ID: <c3ea2c3b-298c-b23a-c52a-1454ae323d79@gmail.com> (raw)
In-Reply-To: <CANCX+3NT_CFrWxVTBJiy_fq5iYQWDTCQyd7Q7G7C2Hf0-52FXg@mail.gmail.com>
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.
next prev parent reply other threads:[~2017-04-25 10:27 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 13:39 Dendari Marini
2017-04-20 13:43 ` Sebastian Moeller
2017-04-20 15:23 ` Dendari Marini
2017-04-20 15:32 ` Jonathan Morton
2017-04-20 16:05 ` Dendari Marini
2017-04-20 17:12 ` Andy Furniss
2017-04-20 17:36 ` Jonathan Morton
2017-04-20 18:35 ` Sebastian Moeller
2017-04-20 18:36 ` Sebastian Moeller
2017-04-21 8:34 ` Dendari Marini
2017-04-21 13:25 ` Sebastian Moeller
2017-04-21 13:27 ` Dendari Marini
2017-04-22 8:25 ` Dendari Marini
2017-04-22 9:36 ` Jonathan Morton
2017-04-22 12:50 ` xnoreq
2017-04-22 13:41 ` Tristan Seligmann
2017-04-22 13:51 ` Andy Furniss
2017-04-22 14:03 ` Andy Furniss
2017-04-22 16:38 ` Andy Furniss
2017-04-22 16:45 ` Dave Taht
2017-04-22 17:00 ` Tristan Seligmann
2017-04-22 20:24 ` Andy Furniss
2017-04-22 16:47 ` Sebastian Moeller
2017-04-22 21:56 ` Dendari Marini
2017-04-22 22:15 ` Sebastian Moeller
2017-04-23 12:32 ` David Lang
2017-04-24 7:55 ` Sebastian Moeller
2017-04-24 8:41 ` Dendari Marini
2017-04-24 11:34 ` Sebastian Moeller
2017-04-24 12:08 ` Dendari Marini
2017-04-24 12:35 ` Sebastian Moeller
2017-04-24 13:49 ` Dendari Marini
2017-04-24 15:42 ` Sebastian Moeller
2017-04-24 17:32 ` Sebastian Moeller
2017-04-25 10:26 ` Andy Furniss [this message]
2017-04-25 11:24 ` Dendari Marini
2017-04-25 12:58 ` Andy Furniss
2017-04-25 18:22 ` Dendari Marini
2017-04-25 19:10 ` Jonathan Morton
2017-04-25 20:44 ` Dendari Marini
2017-04-25 21:32 ` Andy Furniss
2017-04-25 22:33 ` Benjamin Cronce
2017-04-28 15:37 ` Dendari Marini
2017-04-29 15:11 ` Andy Furniss
2017-04-29 17:30 ` Jonathan Morton
2017-04-29 18:29 ` Andy Furniss
2017-04-30 0:05 ` Andy Furniss
2017-05-01 5:50 ` Jonathan Morton
2017-05-01 11:32 ` Andy Furniss
2017-05-01 12:08 ` Jonathan Morton
2017-05-01 13:03 ` Andy Furniss
2017-05-01 13:11 ` Jonathan Morton
2017-05-01 14:46 ` Andy Furniss
2017-04-25 21:06 ` Andy Furniss
2017-04-25 21:16 ` Neil Shepperd
2017-04-25 21:37 ` Andy Furniss
2017-04-25 21:43 ` Sebastian Moeller
2017-04-25 22:06 ` Andy Furniss
2017-04-25 22:29 ` Andy Furniss
2017-04-25 22:32 ` Andy Furniss
2017-04-22 22:35 ` Andy Furniss
2017-04-22 14:12 ` Sebastian Moeller
2017-04-20 18:16 ` Sebastian Moeller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c3ea2c3b-298c-b23a-c52a-1454ae323d79@gmail.com \
--to=adf.lists@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dendari92@gmail.com \
--cc=moeller0@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox