From: Jonathan Foulkes <jf@jonathanfoulkes.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Make - fast - wifi project plan review from 2014....
Date: Fri, 18 Sep 2020 16:58:32 -0400 [thread overview]
Message-ID: <5E9A4F5D-AADC-41FF-943E-1B3E3D866878@jonathanfoulkes.com> (raw)
In-Reply-To: <CAA93jw4Ad4LVWxouqa9BG4PzMBFVvYfTuR62co4PV2D9UyYXUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Dave, You are not the only one noticing widespread wifi issues, and I’m beginning to think something is amiss in the core 80211 or related code, as ever since 18.06 (and up to recently released 19.07.4) I’m observing issues with sensitivity to congestion, drastic decreases in throughput at distance, and on MT76, very frequent ‘drops’ of network connectivity, yet stations remain enrolled and show good signal levels. Sometimes if comes back in 10 seconds, other times minutes. And often, a restart is the only answer.
LEDE 17.x had very good Wifi on the Archer C7, then 18.x and 19.x are nowhere near as good, especially on 2.4.
Current 5.x Master looks better on Mt76, but still see some issues.
A shame, as when the units are operating, and one is reasonably within range of 5Ghz, the throughput and low-latencies are quite good.
Are there any guides on how to gather relevant stats to help document these issues so the devs can zero in on the problems?
Cheers,
Jonathan
> On Sep 18, 2020, at 12:05 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
> I have been observing pretty bad behavior with a lot of 802.11ac
> access points around,
[-- Attachment #2: Type: text/html, Size: 3034 bytes --]
next prev parent reply other threads:[~2020-09-18 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 16:05 Dave Taht
2020-09-18 20:58 ` Jonathan Foulkes [this message]
2020-09-19 7:33 ` Bob McMahon
2020-09-19 10:40 ` Toke Høiland-Jørgensen
2020-09-19 18:11 ` Bob McMahon
[not found] <mailman.0.1600531202.4968.make-wifi-fast@lists.bufferbloat.net>
2020-09-25 7:24 ` Jon Pike
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=5E9A4F5D-AADC-41FF-943E-1B3E3D866878@jonathanfoulkes.com \
--to=jf@jonathanfoulkes.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