Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Cc: geoffrey.fowler@washpost.com
Subject: [Make-wifi-fast] Why is my WiFi so bad?
Date: Wed, 6 May 2020 10:05:07 -0700	[thread overview]
Message-ID: <CAA93jw4r6cMm9yBcRmiA24z8gXMxmiHHP_Z0_zhBM58QZ=5xbw@mail.gmail.com> (raw)

just once... in one major pub...

would I like bufferbloat to be identified as a root cause of home
networking problems. Just once. I'd figured
when vint cerf and jim and van and nick weaver all got on this root
cause back in 2011 that somehow
the concept and problem would have ended up in the public vernacular,
and then all the solutions now
deploying....

There's a lot of good advice here, actually:

https://www.washingtonpost.com/technology/2020/05/06/wifi-problems-questions/

bufferbloat so easy to fix nowadays[1], and still so badly
misunderstood. When you ISP has seconds of
buffering, or your wifi, your network goes to hell, but much of the
time, the problem is at
the isp, and it doesn't help to sit on top of the AP. I like to think
that cable is going to get a lot better with
deployment of the docsis-pie aqm....

best I can do I guess is point folk at the reddit threads on
bufferbloat and sqm for various routers, keep giving talks,
pointing at references like https://lwn.net/Articles/705884/ and the
more recent: https://gettys.wordpress.com/
pieces...

and just hope that more folk actually isolate the true causes of why
is the internet slow today, especially on cable access!
and dsl and shaped fiber. Bufferbloat (and the related jitter), really
messes up videoconferencing.

[1] and sigh, up until last week, so easy to test for via dslreports.com





-- 
Make Music, Not War

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

                 reply	other threads:[~2020-05-06 17:05 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/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='CAA93jw4r6cMm9yBcRmiA24z8gXMxmiHHP_Z0_zhBM58QZ=5xbw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=geoffrey.fowler@washpost.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