All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: How many null-data probes on connection loss?
Date: Wed, 26 Sep 2018 10:38:57 +0200	[thread overview]
Message-ID: <1537951137.28767.5.camel@sipsolutions.net> (raw)
In-Reply-To: <9a1447d9-9a61-dc2d-0101-33c6bdeb946f@candelatech.com> (sfid-20180926_011302_681374_72D229A5)

On Tue, 2018-09-25 at 16:12 -0700, Ben Greear wrote:
> While testing out some other issue, I noticed that my ath10k system creates
> several hundred null-data probes when I abruptly down the AP the station
> is connected to.
> 
> I guess this is because I use the mac80211 stack to handle the probes, and
> the firmware then retries each mac80211 probe many times.
> 
> So, in the case where mac80211 is sending a null-data probe, is the assumption
> that the driver will try each frame exactly once?

Not really, it should be treated like any other management frame.

> Or is several hundred frames expected?  I'm guessing the former, but before I go
> hacking firmware, I thought I would ask...

Certainly not several hundred, but maybe a dozen? I think iwlwifi uses
16, and minstrel would set up max_rate_tries, which drivers set to
somewhere between 1 and 18? One seems s a bit low, mt76?

johannes

  reply	other threads:[~2018-09-26  8:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 23:12 How many null-data probes on connection loss? Ben Greear
2018-09-26  8:38 ` Johannes Berg [this message]
2018-09-26 18:04   ` Ben Greear
2018-09-26 18:26     ` Johannes Berg
2018-09-26 18:47       ` Ben Greear
2018-09-26 18:48         ` Johannes Berg
2018-09-26 18:53           ` Ben Greear
2018-09-26 22:21           ` Ben Greear
2018-09-27  7:12             ` Johannes Berg
2018-09-27 15:32               ` Ben Greear
2018-09-28  7:19                 ` Johannes Berg
2018-09-28 15:14                   ` Ben Greear

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=1537951137.28767.5.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.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.