From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: Jonathan Morton <chromatix99@gmail.com>,
moeller0 <moeller0@gmx.de>,
cake@lists.bufferbloat.net
Subject: Re: [Cake] second system syndrome
Date: Wed, 23 Dec 2015 12:43:30 +0100 [thread overview]
Message-ID: <CAA93jw6i8U-X7KU81Di2k3GEyJGZgECMQ6CgsFB1NLRumu79ug@mail.gmail.com> (raw)
In-Reply-To: <5679CF0F.4080506@darbyshire-bryant.me.uk>
squashing and washing are both well within the realm of ietf best
practices. It is highly desirable to have this level of simple control
on cake for inbound - for example, 90+ of all comcast traffic, no
matter how originally marked, comes in marked as background, and
should be changed to best effort on the gateway. Doing so with an
iptables rule is inefficient and it is difficult (along with the rest
of sqm-scripts) to hook into other people's iptables rules.
On outbound - frankly I was surprised remarking dns, ntp, and mosh as
AF42 worked as well as it did, there was only one place where it
failed (which resulted in the removal of AF42 marking to mosh
mainline) - MIT. There ARE a few indicators like background and IMM
that often survive end to end elsewhere.
more extensive remarking, as kevin also wants to do, seems complex.
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
On Tue, Dec 22, 2015 at 11:30 PM, Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk> wrote:
>
>
> On 21/12/15 15:36, Jonathan Morton wrote:
>> In that context, the “squash” and “wash” features truly baffle me. I’d prefer to see them both gone. Either you want to *use* Diffserv, in which case downstream networks might also benefit from the same markings, or you want to *ignore* it, in which case you might as well leave the existing marks alone, or you want to do something more sophisticated that Cake’s core feature set doesn’t support.
>>
>> In short, Cake is *not* the right place to change the DSCP field. A separate qdisc could be written to do that job with minimal overhead and a dedicated configuration interface, and be inserted either before or after Cake as required. Or we could wait for pre-ingress-qdisc firewall rules to become available.
> Feel free to remove. If squash shouldn't be there, then neither should
> wash. It was an idea to split out the use of diffserv markings vs the
> clearing of them that the original "squash" option implemented into
> 'diffserv/squash/wash". Bad ideas shouldn't be included so get rid of
> it :-)
>
> Kevin
>
next prev parent reply other threads:[~2015-12-23 11:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 14:53 Dave Taht
2015-12-06 16:08 ` Sebastian Moeller
2015-12-07 12:24 ` Kevin Darbyshire-Bryant
2015-12-20 12:47 ` Dave Taht
2015-12-20 12:52 ` Dave Taht
2015-12-21 9:02 ` moeller0
2015-12-21 10:40 ` Dave Taht
2015-12-21 11:10 ` moeller0
2015-12-21 12:00 ` Dave Taht
2015-12-21 13:05 ` moeller0
2015-12-21 15:36 ` Jonathan Morton
2015-12-21 18:19 ` moeller0
2015-12-21 20:36 ` Jonathan Morton
2015-12-21 21:19 ` moeller0
[not found] ` <8737uukf7z.fsf@toke.dk>
2015-12-22 15:34 ` Jonathan Morton
2015-12-22 22:30 ` Kevin Darbyshire-Bryant
2015-12-23 11:43 ` Dave Taht [this message]
2015-12-23 12:14 ` Kevin Darbyshire-Bryant
2015-12-23 12:27 ` Jonathan Morton
2015-12-23 12:41 ` Dave Taht
2015-12-23 13:06 ` Jonathan Morton
2015-12-23 14:58 ` Dave Taht
2015-12-20 13:51 ` moeller0
2015-12-06 18:21 ` Kevin Darbyshire-Bryant
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=CAA93jw6i8U-X7KU81Di2k3GEyJGZgECMQ6CgsFB1NLRumu79ug@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=kevin@darbyshire-bryant.me.uk \
--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