From: Dave Taht <dave.taht@gmail.com>
To: John Sager <john@sager.me.uk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] conntrack lookup continuation
Date: Fri, 3 Feb 2017 09:08:31 -0800 [thread overview]
Message-ID: <CAA93jw4w7KuTKzjMrvY2eVcOozTkesv+7yPu8Y317nE+0pZqxg@mail.gmail.com> (raw)
In-Reply-To: <fd3fe4d3-fd43-ab93-7324-471de066ba27@sager.me.uk>
On Fri, Feb 3, 2017 at 8:42 AM, John Sager <john@sager.me.uk> wrote:
> I would support this. It would allow cake to behave pretty much as I have
> HTB+fq_codel currently set up for both egress and ingress (via ifb0) on my
> border router/firewall. I fwmark egress traffic based on various criteria
> using ip[6]tables & transfer the marks to conntrack where they are recovered
> on ingress to classify inbound responses to outbound requests.
I'm not huge on using fwmarks. Is this because you cannot re-mark
w/dscp consistently via conntrack?
>
> It would also classify inbound traffic better if cake could use fwmarks in
> that way as diffserv is currently pretty much useless for that purpose with
> most ISPs.
My understanding of this is that cake runs before iptables does on
inbound. (?) so fw marks won't help here. But it's probable I'm wrong.
> John
>
> On 31/01/17 21:14, chromatix99 at gmail.com (Jonathan Morton) wrote:
>>> On 31 Jan, 2017, at 16:49, Felix Resch <fuller at beif.de> wrote:
>>>
>>> Since we now already do the conntrack-lookup for the nat keyword, would it be
>>> expensive to implement a kind of internal conntrack-mark-and-restore by cake-tin?
>>>
>>> E.g. when traffic leaves throu canke tin#x, the conntrack entry will get a fwmark and return traffic is put in the corresponding tin/bin on the ingress cake.
>>
>> That's an interesting idea. At this point I don't know how easy it is to implement, though.
>>
>> Certainly we need to clean up some other things first.
>>
>> - Jonathan Morton
>>
>>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2017-02-03 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 14:49 Felix Resch
2017-01-31 21:14 ` Jonathan Morton
2017-02-03 16:42 ` John Sager
2017-02-03 17:08 ` Dave Taht [this message]
2017-02-03 19:01 ` John Sager
2017-02-03 19:30 ` Jonathan Morton
2017-02-03 21:25 ` John Sager
2017-02-04 5:51 ` Konstantin Shalygin
2017-02-04 9:12 ` John Sager
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=CAA93jw4w7KuTKzjMrvY2eVcOozTkesv+7yPu8Y317nE+0pZqxg@mail.gmail.com \
--to=dave.taht@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