($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 2/3] station: fall back to reassociation under certain FT failures
Date: Mon, 28 Aug 2023 13:39:40 -0500	[thread overview]
Message-ID: <111f8eb8-28d5-50d9-3926-51e29ba9ead4@gmail.com> (raw)
In-Reply-To: <4b2351d6-9508-4c55-9929-05591aeec777@gmail.com>

Hi James,

>> Another possibility would be to insert the BSS twice (or reinsert once FT 
>> fails), once with FT and once without FT and try them in rank order. Still, 
>> there's almost no penalty to trying all FT candidates, so unless the ranking 
>> calculation is really off, I think that is a better approach.
> 
> Ok, I'd rather go this route then, re-insert the BSS without FT after this 
> specific failure.

Ok, lets do that then.

> 
> Would you want me to put this behind a config option? Or you think reassociation 
> based on ranking is ok? Again, it would only be with status=53 so I think the 
> impact is minimal.
> 

Make it the default behavior.

Regards,
-Denis

  reply	other threads:[~2023-08-28 18:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 15:29 [PATCH 0/3] Support fallback if FT fails James Prestwood
2023-08-22 15:29 ` [PATCH 1/3] ft: track FT auth/action response status James Prestwood
2023-08-22 15:34   ` James Prestwood
2023-08-27 19:00   ` Denis Kenzior
2023-08-22 15:29 ` [PATCH 2/3] station: fall back to reassociation under certain FT failures James Prestwood
2023-08-27 19:19   ` Denis Kenzior
2023-08-27 21:44     ` James Prestwood
2023-08-28 15:02       ` Denis Kenzior
2023-08-28 15:36         ` James Prestwood
2023-08-28 18:39           ` Denis Kenzior [this message]
2023-08-22 15:29 ` [PATCH 3/3] auto-t: add fallback to reassociate test James Prestwood

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=111f8eb8-28d5-50d9-3926-51e29ba9ead4@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).