From: Mark Captur <mark.captur@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] (no subject)
Date: Thu, 7 Dec 2017 14:34:46 +0100 [thread overview]
Message-ID: <CAGjAyJC8o5VJSEoSiVMNgNPnxDr0kEvLFh41jCW_F9JjsWbNkA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
I am using cake on latest lede nightly. I'm using diffserv 4 which creates
4 tins bulk, best effort, video and voice.
Is there a way to change dscp markings on in comming traffic to place it in
te video tin. More specifically i would like all incoming traffic with
source port 23000 to be set to dscp class CS4.
Thanks,
Mark
[-- Attachment #2: Type: text/html, Size: 411 bytes --]
next reply other threads:[~2017-12-07 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 13:34 Mark Captur [this message]
2017-12-07 22:48 ` [Cake] dscp marking ingress traffic (was (no subject)) John Sager
2017-12-07 23:05 ` Georgios Amanakis
2017-12-08 11:17 ` John Sager
2017-12-08 11:55 ` [Cake] (no subject) Andy Furniss
-- strict thread matches above, loose matches on Subject: below --
2017-03-29 18:15 vignesh kannan
2017-03-29 18:18 ` Jonathan Morton
2017-03-29 18:25 ` vignesh kannan
2016-12-26 12:44 Y
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=CAGjAyJC8o5VJSEoSiVMNgNPnxDr0kEvLFh41jCW_F9JjsWbNkA@mail.gmail.com \
--to=mark.captur@gmail.com \
--cc=cake@lists.bufferbloat.net \
/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