linux-wireless.vger.kernel.org archive mirror
 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: Fri, 28 Sep 2018 09:19:21 +0200	[thread overview]
Message-ID: <1538119161.14416.57.camel@sipsolutions.net> (raw)
In-Reply-To: <a409f0b7-5a91-1add-484d-588a554f0cd4@candelatech.com>

On Thu, 2018-09-27 at 08:32 -0700, Ben Greear wrote:

> > 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?
> 
> I am thinking that if the 'timeout' is 500ms, and the number of probes is 2
> (the default values), then it should probe at 0ms, and at 250ms, and then finally
> fail at 500ms if nothing was received.  In otherwords, X probes, x/timeout apart.

That seems reasonable I guess. Although I'm not sure - perhaps once we
know it failed we *do* want to try a bit quicker again? Otherwise we
have a totally dead period there in the meantime, no?

johannes

  reply	other threads:[~2018-09-28  7:19 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
2018-09-27 15:32               ` Ben Greear
2018-09-28  7:19                 ` Johannes Berg [this message]
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=1538119161.14416.57.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).