Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] https://tools.ietf.org/html/draft-ietf-tsvwg-le-phb-06 is in last call
Date: Sun, 3 Feb 2019 22:02:11 +0200	[thread overview]
Message-ID: <64FB4B3D-E94A-4F3E-81EE-52ED212736DC@gmail.com> (raw)
In-Reply-To: <CAA93jw6Fe8x2s=W3Vp6h0WoN7Q8ia4CddL6e4kA+GQNn87LiUw@mail.gmail.com>


> On 3 Feb, 2019, at 8:39 pm, Dave Taht <dave.taht@gmail.com> wrote:
> 
> it's 000001 which I guess is:
> 
> diff --git a/sch_cake.c b/sch_cake.c
> index 3a26db0..67263b3 100644
> --- a/sch_cake.c
> +++ b/sch_cake.c
> @@ -343,7 +343,7 @@ static const u8 diffserv4[] = {
> };
> 
> static const u8 diffserv3[] = {
> -       0, 0, 0, 0, 2, 0, 0, 0,
> +       0, 1, 0, 0, 2, 0, 0, 0,
>        1, 0, 0, 0, 0, 0, 0, 0,
>        0, 0, 0, 0, 0, 0, 0, 0,
>        0, 0, 0, 0, 0, 0, 0, 0,
> 
> (or is that reversed? my big endian/little endian chops scuks, and
> nobody modified the gen_cake_const tool to match what cake expects
> now)

That looks correct to me, though it should also be added to the other Diffserv modes including a bulk tin.  Fields in TCP/IP are all laid out in "network order" which is most-significant bit/byte first, the same way you'd *normally* write a number down.

The TOS field can sometimes be confusing because the DSCP field is the upper 6 bits and the ECN field the lower 2, and the BSD Sockets API gives you the while byte to work with while DSCPs are quoted as just their own 6 bits.  So you have to shift the latter left two bits before applying them to the former.

 - Jonathan Morton


  reply	other threads:[~2019-02-03 20:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 18:39 Dave Taht
2019-02-03 20:02 ` Jonathan Morton [this message]
2019-02-03 22:42 ` David P. Reed
2019-02-04  0:17   ` Dave Taht
2019-02-04  1:12   ` [Cerowrt-devel] [Cake] " Jonathan Morton
2019-02-04  6:02   ` [Cerowrt-devel] " Mikael Abrahamsson
2019-02-04  6:58     ` [Cerowrt-devel] [Cake] " Dave Taht
2019-02-04  7:11       ` Mikael Abrahamsson
2019-02-04 10:23         ` Dave Taht
2019-02-04 10:34           ` Mikael Abrahamsson
2019-02-04 10:40             ` Dave Taht
2019-08-21 15:07 ` [Cerowrt-devel] " Dave Taht
2019-08-21 16:38   ` [Cerowrt-devel] [Cake] " Kevin Darbyshire-Bryant
2019-08-21 16:52     ` Dave Taht
2019-08-22  6:11       ` Mikael Abrahamsson

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64FB4B3D-E94A-4F3E-81EE-52ED212736DC@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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