Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: ching lu <lsching17@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] diffserv based on firewall mark
Date: Wed, 12 Oct 2016 17:26:08 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1610121724350.10786@nftneq.ynat.uz> (raw)
In-Reply-To: <CACHiF8C5aYKpfZD9Qcwr6jDA3mQpUGcNJRRr8iGGiE0sBY4vpA@mail.gmail.com>

[-- Attachment #1: Type: TEXT/Plain, Size: 846 bytes --]

On Thu, 13 Oct 2016, ching lu wrote:

>> Setting the DSCP with iptables rules should work just as well and in the
> same way as using the “firewall mark” functionality as you already do.  Set
> it up that way in the first instance, directly replacing each HTB+fq_codel
> combination with a Cake instance, and see how it works.
>>
>>  - Jonathan Morton
>
> I might test how cake distribute ingress bandwidth if I use bittorrent and
> YouTube at the same time, hopefully ingress traffic has correct DSCP value

Ingress traffic probably has no DSCP set. Your ISP would be getting the packets 
from some other ISP (possibly several layers of this) who get it from the 
sender. Each time the packet is handed off from one organization to another, the 
DSCP settings loose their meaning and have a really good chance of being 
stripped.

David Lang

[-- Attachment #2: Type: TEXT/PLAIN, Size: 137 bytes --]

_______________________________________________
Cake mailing list
Cake@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake

  reply	other threads:[~2016-10-13  0:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12  5:52 ching lu
2016-10-12  7:26 ` Jonathan Morton
2016-10-12  8:11   ` ching lu
2016-10-12  9:10     ` moeller0
2016-10-12  9:35       ` ching lu
2016-10-12 10:05         ` moeller0
     [not found]           ` <CACHiF8D=iF4cww0QRC-UODpvC=oRmchP6jp3tT2A-=9M2piy+g@mail.gmail.com>
     [not found]             ` <CACHiF8BH2Pfx7de8Se6pv83tHUx1enLt_pc1MBp=uSs2mD=kYA@mail.gmail.com>
2016-10-12 10:17               ` ching lu
2016-10-12 10:21                 ` Dave Taht
2016-10-12 11:10                   ` Kevin Darbyshire-Bryant
2016-10-12 12:07                   ` moeller0
2016-10-12 12:04                 ` moeller0
2016-10-12 12:40                   ` ching lu
2016-10-12 13:07                     ` moeller0
2016-10-13  0:08                       ` ching lu
2016-10-12 15:36                     ` Jonathan Morton
2016-10-12 20:19                       ` Sebastian Moeller
2016-10-13  0:19                       ` ching lu
2016-10-13  0:26                         ` David Lang [this message]
2016-10-12 19:42 ` Y
2016-10-12 19:59   ` Sebastian Moeller

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=alpine.DEB.2.02.1610121724350.10786@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=lsching17@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