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: Thu, 27 Sep 2018 09:12:43 +0200 [thread overview]
Message-ID: <1538032363.14416.2.camel@sipsolutions.net> (raw)
In-Reply-To: <e3c18a8d-9a58-54c5-9aaa-b778299f527b@candelatech.com>
On Wed, 2018-09-26 at 15:21 -0700, Ben Greear wrote:
>
> Now only 4 retries per frame, but it seems mac80211 is all 5 of its
> null-data probes within a few miliseconds. Is that expected, or should
> there be a bit more pause between each of the probe requests to better
> weather periodic network glitches?
Hmm. That's a good point, but it seems we've never considered this
before. This must be a consequence of retrying immediately on lost ACK,
but I guess I could see that delaying it for a little bit would make
sense.
We do delay it if there's no reliable ACK reporting, IIRC, but if we
know it failed for sure ...
It seems though that if there's some noise or so on the channel you
wouldn't be transmitting, so what kind of "network glitches" might
affect this? AP going away unexpectedly for some time?
johannes
next prev parent reply other threads:[~2018-09-27 7:13 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
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 [this message]
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=1538032363.14416.2.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.