From: James Prestwood <prestwoj@gmail.com>
To: Baochen Qiang <quic_bqiang@quicinc.com>,
"open list:MEDIATEK MT76 WIRELESS LAN DRIVER"
<linux-wireless@vger.kernel.org>
Cc: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: ath11k/WCN6855 neighbor report request made immediately after connection gets no response (with MFP)
Date: Tue, 1 Oct 2024 06:08:51 -0700 [thread overview]
Message-ID: <b8afb2d6-02f6-4b6d-ae63-853225c28eea@gmail.com> (raw)
In-Reply-To: <564bb38f-aef1-4981-b706-926eef5c6776@quicinc.com>
On 9/28/24 7:16 PM, Baochen Qiang wrote:
>
> On 9/27/2024 7:53 PM, James Prestwood wrote:
>>> here is the sequence I saw in sniffer:
>>> #1 AP send M3
>>> #2 station send 'neighbor report request' without encryption, though 'protected' flag is set
>>> #3 station send out M4
>>>
>>> is this the same with what you saw?
>> When I was able to capture the neighbor report request (rarely) it was after M4, not before. If you're seeing it prior to M4 that seems strange, unless the kernel/ath11k is doing some odd queuing?
> yeah... firmware has some odd assumption on the sequence of key install, causing such behavior.
>
Do you think maybe this has something to do with it? Its just a timing
issue (both in my case and when you see it before M4) and in some cases
the keys aren't fully installed and the request either gets dropped or
just isn't encrypted correctly?
Like I said originally, its not like this issue is severe, we can just
request a neighbor report later and that does work. It was just an
observation and didn't seem right.
Thanks,
James
prev parent reply other threads:[~2024-10-01 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 12:21 ath11k/WCN6855 neighbor report request made immediately after connection gets no response (with MFP) James Prestwood
2024-09-25 10:07 ` Baochen Qiang
2024-09-25 11:33 ` James Prestwood
2024-09-26 3:16 ` Baochen Qiang
2024-09-26 12:31 ` James Prestwood
2024-09-27 5:59 ` Baochen Qiang
2024-09-27 11:53 ` James Prestwood
2024-09-29 2:14 ` Baochen Qiang
2024-10-01 13:06 ` James Prestwood
2024-09-29 2:16 ` Baochen Qiang
2024-10-01 13:08 ` James Prestwood [this message]
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=b8afb2d6-02f6-4b6d-ae63-853225c28eea@gmail.com \
--to=prestwoj@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.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