All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: ath10k@lists.infradead.org
Subject: Re: duplicate authentications / excessive missing ACKs / deauth due to inactivity timer
Date: Wed, 22 Jul 2020 07:27:16 -0700	[thread overview]
Message-ID: <cdba7890-62e4-4d99-bd0f-f1d458a4adc7@candelatech.com> (raw)
In-Reply-To: <20200722161812.329d7a10@brot>

On 7/22/20 7:18 AM, Leon M. George wrote:
> Hi :-)
> 
> I've encountered connection issues that appear to be strongly related to the
> problem in this thread [1] (found via the arch linux bug tracker [2]).

If this is ath10k-ct only problem, plz don't bother this list and send to just me
and/or add to ath10k-ct bugtracker on github.

If it does affect upstream ath10k too, then that would be valid for this mailing
list.

Thanks,
Ben

> 
> Symptoms:
> ap: "disconnected due to excessive missing ACKs"
> station: "No beacon heard and the time event is over already..."
> 
> Using a monitoring interface on the AP i was able to confirm that the beacon is
> indeed not being sent at any time.
> 
> I've found a configuration that reliably produces this state
> ("error state" from here on):
> If any number of mesh (or adhoc with ct) points are configured alongside any
> number of ordinary APs, this issue starts appearing.
> The mesh connections appear to be working correctly in the error state.
> 
> I tested various combinations of openwrt-19.xx and openwrt-trunk
> with ath10k/ath10k-ct - all were affected.
> Aligning with my vague memory, a user on the openwrt forum reports the issue isn't
> present in openwrt-18.xx [3].
> 
> About the ruling out client issues:
> My employer is operating installations with multiple hundreds of ath10k access
> points.
> We couldn't identify the source of the issue at first when we encountered it in
> our live setup and received unsolicited reports from basically every
> installation.
> As far as we can tell, no client is able to connect in the error state.
> We've had our users confirm the bug for
>    - Apple phones/tablets/macbooks
>    - Samsung phones, laptops
>    - computers with Intel/Realtek/AzureWave-hardware.
> 
> I hope this info is helpful.
> 
> kind regards,
> Leon George
> 
> [1] https://www.mail-archive.com/ath10k@lists.infradead.org/msg11599.html
> [2] https://bugs.archlinux.org/task/58457
> [3] https://forum.openwrt.org/t/wifi-connectivity-issues-with-ath10k/67779
> 
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
> 


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2020-07-22 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 14:18 duplicate authentications / excessive missing ACKs / deauth due to inactivity timer Leon M. George
2020-07-22 14:27 ` Ben Greear [this message]
2020-07-22 16:04   ` Leon M. George
  -- strict thread matches above, loose matches on Subject: below --
2019-12-01 16:30 Justin Capella
2019-12-01 17:01 ` Adrian Chadd
2019-12-01 17:18   ` Justin Capella
2019-12-01 17:21     ` Adrian Chadd
2019-12-01 18:53       ` Justin Capella

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

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

  git send-email \
    --in-reply-to=cdba7890-62e4-4d99-bd0f-f1d458a4adc7@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.