From: Georgios Amanakis <gamanakis@gmail.com>
To: John Sager <john@sager.me.uk>, cake@lists.bufferbloat.net
Subject: Re: [Cake] dscp marking ingress traffic (was (no subject))
Date: Thu, 07 Dec 2017 18:05:42 -0500 [thread overview]
Message-ID: <1512687942.28287.2.camel@gmail.com> (raw)
In-Reply-To: <772b6eb3-065e-ea22-0895-74516bceebb5@sager.me.uk>
You can do it, but it has to be on a different interface than the
incoming traffic.
Say incoming traffic is on eth0 (WAN) and outgoing LAN traffic is on
eth1. Then you can DSCP mark with iptables on incoming eth0, and since
the traffic is forwarded to eth1 the DSCP marking is going to be
preserved.
On Thu, 2017-12-07 at 22:48 +0000, John Sager wrote:
> I've wondered that, and at the moment I don't think there is. The
> ingress
> qdisc stuff happens before the packets hit any iptables hooks so you
> can't
> use iptables rules to do it. None of the actions that can be attached
> to a
> filter on the ingress qdisc seem to offer what you want.
>
> I use packet marks and connmarks to classify outgoing traffic using
> iptables
> rules. The connmarks are then transferred back to incoming packets
> using the
> connmark action, followed by the mirred action to send them to ifb0
> where
> the real downstream qdiscs - htb and fq_codel - are applied. This
> works well
> to partition my upstream & downstream bandwidth between different
> traffic
> classes, but I can't yet see how to adapt this to work with cake.
>
> John
>
>
> On 07/12/17 13:34, Mark Captur wrote:
> > 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
> >
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2017-12-07 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 13:34 [Cake] (no subject) Mark Captur
2017-12-07 22:48 ` [Cake] dscp marking ingress traffic (was (no subject)) John Sager
2017-12-07 23:05 ` Georgios Amanakis [this message]
2017-12-08 11:17 ` John Sager
2017-12-08 11:55 ` [Cake] (no subject) Andy Furniss
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=1512687942.28287.2.camel@gmail.com \
--to=gamanakis@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=john@sager.me.uk \
/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