iwd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Wen Gong <quic_wgong@quicinc.com>
To: James Prestwood <prestwoj@gmail.com>, <iwd@lists.01.org>,
	<iwd@lists.linux.dev>
Cc: Denis Kenzior <denkenz@gmail.com>
Subject: Re: [PATCH v3 3/3] owe: netdev: refactor to remove OWE as an auth-proto
Date: Thu, 13 Jul 2023 11:07:23 +0800	[thread overview]
Message-ID: <84d37909-756b-f09f-904f-a4310335bb2b@quicinc.com> (raw)
In-Reply-To: <0617fffe-2f26-bceb-5bd9-782882f24dd0@gmail.com>

On 7/13/2023 11:04 AM, James Prestwood wrote:
> Hi Wen,
>
>>
>> ======================Association Response start======================
>>
...
> Indeed, it doesn't include the RSNE as it should. Out of curiosity do 
> you know what AP model/manufacturer this is? Its nice to document this 
> for others and to reference in the future.
>
Hi James,

you can see the assoc request, it is ASUS 6 GHz AP.

Tag: SSID parameter set: ASUS-6GAP
     Tag Number: SSID parameter set (0)
     Tag length: 9
     SSID: ASUS-6GAP

> Thanks for digging into this. If Denis is fine with relaxing the check 
> I'll send a patch and take care of that.
>
> Thanks,
> James
>
>>
>>
...

  reply	other threads:[~2023-07-13  3:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 19:35 [PATCH v3 1/3] netdev: factor out scan_bss from CMD_CONNECT builder James Prestwood
2021-09-03 19:35 ` [PATCH v3 2/3] wsc: set ssid in handshake James Prestwood
2021-09-03 19:35 ` [PATCH v3 3/3] owe: netdev: refactor to remove OWE as an auth-proto James Prestwood
2021-09-03 19:44   ` Denis Kenzior
2023-07-12 11:17   ` Wen Gong
2023-07-12 14:52     ` James Prestwood
     [not found]       ` <00246aa8-fe45-f5c2-cf2a-3450cee414f2@quicinc.com>
2023-07-13  2:33         ` James Prestwood
2023-07-13  2:52           ` Wen Gong
2023-07-13  3:04             ` James Prestwood
2023-07-13  3:07               ` Wen Gong [this message]
2023-07-13  3:56               ` Wen Gong
2023-07-13 14:14           ` 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=84d37909-756b-f09f-904f-a4310335bb2b@quicinc.com \
    --to=quic_wgong@quicinc.com \
    --cc=denkenz@gmail.com \
    --cc=iwd@lists.01.org \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.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 NNTP newsgroup(s).