From: moeller0 <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: ching lu <lsching17@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] diffserv based on firewall mark
Date: Wed, 12 Oct 2016 14:07:09 +0200 [thread overview]
Message-ID: <375CB1B8-0D16-4EEA-B4AC-73BDCFB76460@gmx.de> (raw)
In-Reply-To: <CAA93jw7M3AsTqD7OQ0XFXvYL86YBozywBnOyE4xVtZcestbcVw@mail.gmail.com>
> On Oct 12, 2016, at 12:21 , Dave Taht <dave.taht@gmail.com> wrote:
>
> I still defend the idea of the diffserv "squash" option cake once had.
> It was essentially RFC compliant, simple to use, and because iptables
> was too late on inbound, needed, no matter the layer violation.
As stated I am not sure whether that is a relevant layering violation to begin with… I believe that Jonathan found a way to have a dscp qdisc stacked on top of cake that does the squashing afterwards. I am uncertain whether that only worked in theory (so whether research stopped after finding the dscp qdisc) or whether that was actually tested to DTRT in allowing cake to use the internally set DSC values but re-map them to 0 before putting them on the wire?
Best Regards
Sebastian
next prev parent reply other threads:[~2016-10-12 12:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 5:52 ching lu
2016-10-12 7:26 ` Jonathan Morton
2016-10-12 8:11 ` ching lu
2016-10-12 9:10 ` moeller0
2016-10-12 9:35 ` ching lu
2016-10-12 10:05 ` moeller0
[not found] ` <CACHiF8D=iF4cww0QRC-UODpvC=oRmchP6jp3tT2A-=9M2piy+g@mail.gmail.com>
[not found] ` <CACHiF8BH2Pfx7de8Se6pv83tHUx1enLt_pc1MBp=uSs2mD=kYA@mail.gmail.com>
2016-10-12 10:17 ` ching lu
2016-10-12 10:21 ` Dave Taht
2016-10-12 11:10 ` Kevin Darbyshire-Bryant
2016-10-12 12:07 ` moeller0 [this message]
2016-10-12 12:04 ` moeller0
2016-10-12 12:40 ` ching lu
2016-10-12 13:07 ` moeller0
2016-10-13 0:08 ` ching lu
2016-10-12 15:36 ` Jonathan Morton
2016-10-12 20:19 ` Sebastian Moeller
2016-10-13 0:19 ` ching lu
2016-10-13 0:26 ` David Lang
2016-10-12 19:42 ` Y
2016-10-12 19:59 ` 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=375CB1B8-0D16-4EEA-B4AC-73BDCFB76460@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=lsching17@gmail.com \
/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