Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Cc: Iain Fraser <iainf@netduma.com>,
	Luke Barlow <luke.barlow@netduma.com>,
	 ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] fq_codel not-so-secret sauce in netduma's anti-bufferbloat implementation
Date: Thu, 11 Apr 2019 17:40:33 +0200	[thread overview]
Message-ID: <CAA93jw5r0AkkdNwXMUcw2BAOVuJ=JeM2+O=u5Q5a5t1g4g5tGw@mail.gmail.com> (raw)

My understanding of netduma's implementation of "anti-bufferbloat" is
that it also does weird things with attempting to classify traffic,
and as far as I can tell, they still don't correctly compensate for
dsl or cable modem framing which is the root cause of some angst in
their forums. And I sure wish they's come clean about using RFC8290 in
their design, to me anyone that publicly states they are using
fq_codel is a mark of quality.... :) and I'd also like to know if the
have ecn on or off.

It was good, after all this time, to see this error message.

http://forum.netduma.com/topic/25802-qos-rpc-error-error_cmdfail-exec-tc-qdisc-add-dev-ppp0-parent-21-handle-3-fq_codel-failed-with-2/

-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

                 reply	other threads:[~2019-04-11 15:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw5r0AkkdNwXMUcw2BAOVuJ=JeM2+O=u5Q5a5t1g4g5tGw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=iainf@netduma.com \
    --cc=luke.barlow@netduma.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