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>,
ath11k@lists.infradead.org
Subject: Re: ath11k multicast action frame RX
Date: Fri, 23 Feb 2024 08:13:27 -0800 [thread overview]
Message-ID: <3cd77b50-f681-4b74-bdaa-6e2bd73ad744@gmail.com> (raw)
In-Reply-To: <df35ce71-84dd-4c2c-af9a-820cb9a71291@quicinc.com>
Hi Baochen
On 2/22/24 5:56 PM, Baochen Qiang wrote:
>
>
> On 2/22/2024 11:38 PM, James Prestwood wrote:
>> Hi Baochen,
>>
>> On 2/21/24 6:26 PM, Baochen Qiang wrote:
>>> But you are using monitor mode, not station mode, on ath10k, right?
>>
>> No I'm using station mode. It looks like ath10k creates a monitor
>> device to receive these frames (that was already done before my
>> patch), but the interface I'm using from userspace is a regular
>> station interface
>>
> OK let's forget what ath10k does to receiver those frames for now and
> focus on ath11k. From what I got from firmware team, it's expected
> that ath11k station interface can't get those frame without a scan
> because device A is connected to an AP already and is supposed to get
> frames only from within the BSS, apparently device B here is not
> within that BSS.
>
I still don't know why a scan would change anything. Maybe the act of
scanning triggers something in the firmware to allow the RX of multicast
frames (like to receive probe responses)? If so that's not really a
mechanism to enable multicast RX, its just a side effect of scanning.
But yes currently when an ath11k device is connected to a BSS it will
only receive frames from within that BSS. This is what I was attempting
to change, allow it to receive multicast action frames while connected
(or disconnected for that matter).
The whole point of DPP is to provision a new device. So one device is
offline and asking the connected device for credentials. This is done
via multicast action frames.
Thanks,
James
>> Thanks,
>>
>> James
>>
prev parent reply other threads:[~2024-02-23 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 13:06 ath11k multicast action frame RX James Prestwood
2024-01-26 19:18 ` James Prestwood
2024-01-30 7:00 ` Baochen Qiang
2024-01-30 12:47 ` James Prestwood
2024-01-30 12:54 ` James Prestwood
2024-01-31 2:01 ` Baochen Qiang
2024-01-31 12:28 ` James Prestwood
2024-02-21 3:45 ` Baochen Qiang
2024-02-21 12:24 ` James Prestwood
2024-02-22 2:26 ` Baochen Qiang
2024-02-22 15:38 ` James Prestwood
2024-02-23 1:56 ` Baochen Qiang
2024-02-23 16:13 ` 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=3cd77b50-f681-4b74-bdaa-6e2bd73ad744@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).