ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:06:38 -0700	[thread overview]
Message-ID: <dfe29bc6-a8e0-4690-9aa2-b38a15ae1297@gmail.com> (raw)
In-Reply-To: <241fe825-991f-4dca-ad1c-e45f6a524edf@quicinc.com>


On 9/28/24 7:14 PM, Baochen Qiang wrote:
>
> On 9/27/2024 7:53 PM, James Prestwood wrote:
>> I think what I saw here was because the capture was done through the AP vendor was automatically decrypted or something. The frame was still marked as protected, but I never had to add the PMK to get wireshark to parse it correctly.
> this is exactly what I see. there is no automatic decryption here, it is only because the frame is NOT encrypted, though 'protected' bit set.
>
>> On my home network when I was referring to "always encrypted" it was because the frames always had the CCMP IV and the content of the frame itself was not visibly a neighbor report/request, just a string of hex values. Once I added the PMK and decrypted it wireshark could parse it.
> is this tested still with IWD?
Yes, only with IWD.


  reply	other threads:[~2024-10-01 13:06 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 [this message]
2024-09-29  2:16             ` Baochen Qiang
2024-10-01 13:08               ` 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=dfe29bc6-a8e0-4690-9aa2-b38a15ae1297@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