From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH] wiphy: set neighbor report capability flag
Date: Thu, 05 Aug 2021 21:10:25 -0500 [thread overview]
Message-ID: <4af22a81-e447-0f79-e9d3-062e6148d3ff@gmail.com> (raw)
In-Reply-To: <CACsRnHX0yR+SnWGPPtKkKQGGdcRn=pySxjyFy4eQmG-YkfAoqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Hi Michael,
On 8/3/21 12:41 PM, Michael Johnson wrote:
> Hi Denis,
>
> On Tue, 3 Aug 2021 at 17:35, Denis Kenzior <denkenz@gmail.com> wrote:
>> Hmm, I wonder if we have a different bug here. This gives me a few ideas to
>> look into, let me poke around and I'll get back to you.
>>
>> What other problems are you having?
>
> Thank you!
>
> The other major problem I'm having is when 802.11v is enabled the APs
> are not sending BSS-TM frames during re-associations (i.e. FT roams)
> but it does work during a full association.
> The current suspect is that the client doesn't send the "extended
> capabilities" tags in the re-association frame like it does with a
> full association. Without this the Meraki APs assume the client
> doesn't support it.
> I don't know what the standard says about this one.
>
I believe I have fixed this upstream now with commit 8f9e6b3f7626 ("netdev: Send
addititional IEs for FT/SAE/OWE/FILS")
Can you give it another try?
Regards,
-Denis
next prev parent reply other threads:[~2021-08-06 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 14:19 [PATCH] wiphy: set neighbor report capability flag Michael Johnson
2021-08-03 15:02 ` Denis Kenzior
2021-08-03 16:07 ` Michael Johnson
2021-08-03 16:19 ` Denis Kenzior
2021-08-03 17:41 ` Michael Johnson
2021-08-06 2:10 ` Denis Kenzior [this message]
2021-08-06 15:28 ` Michael Johnson
2021-08-18 17:39 ` Michael Johnson
2021-08-18 18:11 ` Denis Kenzior
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=4af22a81-e447-0f79-e9d3-062e6148d3ff@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.01.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.