From: Sebastian Moeller <moeller0@gmx.de>
To: Noah Causin <n0manletter@gmail.com>,cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake Diffserv8 Incorrect?
Date: Sun, 06 Nov 2016 07:35:20 +0100 [thread overview]
Message-ID: <4AE39B01-4537-4BED-AF39-2FCD9E7754DD@gmx.de> (raw)
In-Reply-To: <fe26416b-a5e8-9d44-01c1-1f4a73b47dca@gmail.com>
Hi Noah,
So far the only way to figure out what cake is supposed to do is looking at the source code, as there are no high-level design documents, nor even a proper man page. That said I believe that cake's diffuser modes correspond to Jonathan's interpretation of different related RFCs; not that these RFCs necessarily make much sense and it is not clear which RFC a specific mode was based on. Since DSCPs are only ever valid inside a DSCP-domain like a home net, I guess most of the schemes are workable as long as the mapping is well documented. Now it would be sweet if cake would grow a robust and comprehensive documentation, and while I believe this is going to happen, I would not hold my breath...
Best Regards
Sebastian
On November 6, 2016 5:49:56 AM GMT+01:00, Noah Causin <n0manletter@gmail.com> wrote:
>Hi,
>
>I've started using diffserv8 mode on cake with packet marking, and I
>have been noticing that traffic does not appear to go into its correct
>tin in tc -s qdisc in LEDE.
>
>This is what I notice:
>
>cs0 in tin 2
>cs1 in tin 0
>cs2 in tin 2
>cs3 in tin 3
>cs4 in tin 6
>cs5 in tin 6
>cs6 in tin 7
>cs7 in tin 7
>
>Noah Causin
>_______________________________________________
>Cake mailing list
>Cake@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cake
prev parent reply other threads:[~2016-11-06 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 4:49 Noah Causin
2016-11-06 6:04 ` Jonathan Morton
2016-11-06 6:40 ` Noah Causin
2016-11-06 6:35 ` Sebastian Moeller [this message]
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=4AE39B01-4537-4BED-AF39-2FCD9E7754DD@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=n0manletter@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