General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Collier-Brown <dave.collier-brown@indexexchange.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Dumb question time 1: using upload and download speeds from dslreports
Date: Sun, 4 Oct 2020 12:44:08 -0400	[thread overview]
Message-ID: <09e20edc-c2da-1094-0a14-c2efcb933478@indexexchange.com> (raw)
In-Reply-To: <D8E857D9-2F93-46C7-971F-670D808333AE@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]

Phew, thanks! --dave

On 2020-10-04 12:31 p.m., Jonathan Morton wrote:

On 4 Oct, 2020, at 6:25 pm, Dave Collier-Brown <dave.collier-brown@indexexchange.com><mailto:dave.collier-brown@indexexchange.com> wrote:

When setting my laptop to explicitly use CAKE for an article- and
recipe-writing effort, I blithely took the download speed and stuffed it
into

   tc qdisc replace dev enp0s25 root cake docsis ack-filter bandwidth
179mbit

When Iván Baldo kindly suggested I mention ingress, it suddenly struck
me: I was using the downstream/ingress value for my upstream setting!

Should I not be using my upload speed, some 13mbit, not 179 ???



For ingress traffic (usually the download direction), you need to redirect the ingress traffic to an IFB device and attach an ingress-configured Cake instance there.  You would use "ingress" instead of "ack-filter" and your download bandwidth.

For egress traffic you should indeed use the upload speed.

 - Jonathan Morton



--
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
dave.collier-brown@indexexchange.com<mailto:dave.collier-brown@indexexchange.com> |              -- Mark Twain



CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory.

[-- Attachment #2: Type: text/html, Size: 2882 bytes --]

      reply	other threads:[~2020-10-04 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-04 15:25 Dave Collier-Brown
2020-10-04 16:31 ` Jonathan Morton
2020-10-04 16:44   ` Dave Collier-Brown [this message]

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

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

  git send-email \
    --in-reply-to=09e20edc-c2da-1094-0a14-c2efcb933478@indexexchange.com \
    --to=dave.collier-brown@indexexchange.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@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