From: Jon Pike <jonpike54@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Make - fast - wifi project plan review from 2014....
Date: Fri, 25 Sep 2020 00:24:42 -0700 [thread overview]
Message-ID: <CALukJKTu1HTs7CYHkrj+nHRvXVx24S=+AWPFwLHJ4q1J6Qd+YQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.0.1600531202.4968.make-wifi-fast@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]
>
>
> ---------- Forwarded message ----------
> From: Jonathan Foulkes <jf@jonathanfoulkes.com>
> To: Dave Taht <dave.taht@gmail.com>
> Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
> Bcc:
> Date: Fri, 18 Sep 2020 16:58:32 -0400
> Subject: Re: [Make-wifi-fast] Make - fast - wifi project plan review from
> 2014....
> 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
>
You definitely aren't among the few. Its been a continuing issue I've been
having as you describe. It gets mentioned occasionally on the OpenWrt
forums... but never seems to get a critical mass of attention. I and
others have started threads, that have faded out over time.
Now, it seeming that a general thought is developing that "C7's just arent
good for 2.4ghz" hiding that they WERE, and now have an issue.
Anyway, even though I'm mostly a lurking layperson.. I have lots of
collected logs over time, and have lots of observational data on this
issue. Not much in the regular logs, though. A while back in history it
was more the 5ghz radio dropping, but in the last several months to a year
its been almot always the 2.4ghz radio, similar to what you are
describing. I would like very much to know how to find out the necessary
info so that the devs can get a handle on it.
Count me in...
[-- Attachment #2: Type: text/html, Size: 3183 bytes --]
next parent reply other threads:[~2020-09-25 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1600531202.4968.make-wifi-fast@lists.bufferbloat.net>
2020-09-25 7:24 ` Jon Pike [this message]
2020-09-18 16:05 Dave Taht
2020-09-18 20:58 ` Jonathan Foulkes
2020-09-19 7:33 ` Bob McMahon
2020-09-19 10:40 ` Toke Høiland-Jørgensen
2020-09-19 18:11 ` Bob McMahon
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='CALukJKTu1HTs7CYHkrj+nHRvXVx24S=+AWPFwLHJ4q1J6Qd+YQ@mail.gmail.com' \
--to=jonpike54@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