From: "dpreed@deepplum.com" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] not sure how to reproduce this...
Date: Tue, 16 Jan 2018 16:03:59 -0500 (EST) [thread overview]
Message-ID: <1516136639.857124847@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw4R08nvJpa=eT6dqrzn4-xJ5KS3VMazkjbjHAJ3036KgQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
Looks like a bufferbloat problem. Or maybe non-fair-sharing of the WiFi channel. I'm betting on it being a simple bufferbloat problem, though. Easy to swamp the uplink path.
If it is a bufferbloat problem, then it's not the router that's the real problem, though running some kind of rate-limited AQM solution will mitigate it.
(It really, really bugs me that the DOCSIS folks have yet to roll out known bufferbloat fixes in their cable modems and CMTS's after many years!)
-----Original Message-----
From: "Dave Taht" <dave.taht@gmail.com>
Sent: Tuesday, January 16, 2018 3:37pm
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] not sure how to reproduce this...
https://www.theverge.com/2018/1/16/16897426/wi-fi-google-home-chromecast-archer-router
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
_______________________________________________
Make-wifi-fast mailing list
Make-wifi-fast@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/make-wifi-fast
[-- Attachment #2: Type: text/html, Size: 1995 bytes --]
prev parent reply other threads:[~2018-01-16 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 20:37 Dave Taht
2018-01-16 21:03 ` dpreed [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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1516136639.857124847@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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