From: "Chien Wong" <m@xv97.com>
To: "Sai Pratyusha Magam" <sai.magam@oss.qualcomm.com>,
<johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>, <sai.magam@oss.qualcomm.com>,
<quic_drohan@quicinc.com>
Subject: Re: [PATCH wireless-next v3] wifi: mac80211: Fix AAD/Nonce computation for management frames with MLO
Date: Thu, 12 Feb 2026 17:58:13 +0800 [thread overview]
Message-ID: <DGCW7TTCQC89.2G77C3IBE4SRC@xv97.com> (raw)
In-Reply-To: <20260212042601.2250514-1-sai.magam@oss.qualcomm.com>
Hey,
While adding MLO decryption feature to Wireshark, I noticed this issue that
mac80211_hwsim handles MLO management frames encryption incorrectly.
It seems that wlantest can also verify the correctness of the encryption?
However, I couldn't get it to work—wlantest keeps reporting 'No PTK known
to decrypt the frame', but at least I verified using Wireshark that the
encryption of unicast data frames and management frames in MLO is correct
with the patch.
BTW, the changes to Wireshark are already in the upstream repository. If you
want to use it for verification, you need to compile it yourself because
the currently released version does not yet include these changes.
Tested on base commit 05f7e89ab9731565d8a62e3b5d1ec206485eeb0(v6.19)
Tested case eht_mld_sae_two_link from hostapd
Tested-by: Chien Wong <m@xv97.com>
next prev parent reply other threads:[~2026-02-12 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 4:26 [PATCH wireless-next v3] wifi: mac80211: Fix AAD/Nonce computation for management frames with MLO Sai Pratyusha Magam
2026-02-12 9:58 ` Chien Wong [this message]
2026-02-18 6:24 ` Sai Pratyusha Magam
2026-02-23 9:17 ` Jouni Malinen
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=DGCW7TTCQC89.2G77C3IBE4SRC@xv97.com \
--to=m@xv97.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_drohan@quicinc.com \
--cc=sai.magam@oss.qualcomm.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