From: "Jonas Mårtensson" <martensson.jonas@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] cake + mpls?
Date: Mon, 10 Jan 2022 22:31:56 +0100 [thread overview]
Message-ID: <CAM9iV=LxEffEgDaAofBOa-emt5aJ18kh-Z3Vx_QQr2gbCyvnHA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7B0y3Voj_fTTS1WMPkCi_mn8ckVbKKU10feR7id-Vefw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
If you just want to use cake with priority tins based on the MPLS "Traffic
Class" (TC) field (i.e. the renamed original "EXP" field, see RFC5462), I
think you can use a tc flower filter (
https://man7.org/linux/man-pages/man8/tc-flower.8.html) matching on mpls_tc
values. See here for some examples:
https://www.redhat.com/sysadmin/mpls-tc-linux-kernel
/Jonas
On Mon, Jan 10, 2022 at 7:21 PM Dave Taht <dave.taht@gmail.com> wrote:
> I noticed that sometime in the past 8 years the flow_dissector gained
> support for dissecting mpls packets. I don't know how deep that rabbit
> hole
> goes.
>
> Over here on this mikrotik thead
> https://forum.mikrotik.com/viewtopic.php?p=904422#p904422 the question
> was asked about cake, the exp bits, and mpls.
>
> In looking over this, would we slam cake onto the vrf? or?
>
> https://blog.swineson.me/en/use-linux-as-an-mpls-router/
>
> I have precisely zero experience with mpls. Is there an mpls expert in
> the house?
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2319 bytes --]
prev parent reply other threads:[~2022-01-10 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:21 [Cake] " Dave Taht
2022-01-10 21:31 ` Jonas Mårtensson [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='CAM9iV=LxEffEgDaAofBOa-emt5aJ18kh-Z3Vx_QQr2gbCyvnHA@mail.gmail.com' \
--to=martensson.jonas@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@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