From: Andy Furniss <adf.lists@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Getting Cake to work better with Steam and similar applications
Date: Sat, 22 Apr 2017 15:03:39 +0100 [thread overview]
Message-ID: <8ab8a7e3-3946-a555-ef76-e0acfc16eda8@gmail.com> (raw)
In-Reply-To: <37ea1abc-8c08-784c-0873-ed6df8d089ca@gmail.com>
Andy Furniss wrote:
> Jonathan Morton wrote:
>>>> So please add “atm overhead 32" to cake on eth0 or “atm
>>>> overhead 40” to cake instances on pppoe (these packets do not
>>>> have the PPPoE header added yet and hence appear 8 bytes to
>>>> small).
>>>
>>> Thanks for your help, will definitely use them. Just wondering if
>>> I use "pppoe-vcmux/bridged-llcsnap" on eth0 or "pppoe-llcsnap" on
>>> pppoe0 would have the same effect? Or are there some other
>>> "under-the-hood" changes when using them?
>>
>> On the pppoe interface, use pppoe-vcmux if your modem is set to use
>> VC-MUX, or pppoe-llcsnap if it’s set to use LLC-SNAP (they might
>> be described using slightly different terms, but should still be
>> recognisable as one or the other). This probably depends on your
>> ISP, and may further vary regionally within the same ISP.
>>
>> I really prefer to use the self-explanatory keywords (which is why
>> I added them in the first place) instead of opaque magic numbers.
>> This is a point on which Sebastian has long disagreed with me.
>
> Either way (or maybe not!), what about the observation that
> attaching cake on pppoe, for me at least, required the use of the raw
> param due to the "auto compensation" mechanism seeing pppoe as +8
> when the actual packets are just ip len so not +8.
My case is not atm though, perhaps the atm param cancels out all
other auto overhead compensation?
next prev parent reply other threads:[~2017-04-22 14:03 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 [this message]
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
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=8ab8a7e3-3946-a555-ef76-e0acfc16eda8@gmail.com \
--to=adf.lists@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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