asahi.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Paul Fertser <fercerpav@gmail.com>
To: Hector Martin <marcan@marcan.st>
Cc: Daniel Berlin <dberlin@dberlin.org>, asahi@lists.linux.dev
Subject: SAE AP on BCM4345/6 (was: Re: Testing bits/080-wifi on BCM4345/6)
Date: Sat, 27 Jan 2024 17:40:06 +0300	[thread overview]
Message-ID: <ZbUVxhsrbbjhOd0+@home.paul.comp> (raw)
In-Reply-To: <ZYa2Q8ALPbr09L4b@home.paul.comp>

On Sat, Dec 23, 2023 at 01:28:19PM +0300, Paul Fertser wrote:
> 4. AP mode WPA3 SAE starts and beacons but connection to it is
> impossible (probably due to a user error, haven't tested much).

This wasn't supposed to work before [0] so when testing this feature
make sure you run hostapd from git.

For the reference, I haven't tried it with your patches yet and it's
still not working on AP6255 with mainline.

[0] https://w1.fi/cgit/hostap/commit/?id=b089803091cff61e253e09fb560c7ef7a336a611

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com

      parent reply	other threads:[~2024-01-27 14:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  6:05 [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password Hector Martin
2023-11-08 11:12 ` Neal Gompa
2023-12-17 11:25 ` Kalle Valo
2023-12-19  8:52   ` Arend Van Spriel
2023-12-19  8:57     ` Kalle Valo
2023-12-19 11:01     ` Hector Martin
2023-12-19 13:46       ` Arend van Spriel
2023-12-19 14:26         ` Julian Calaby
2023-12-21 20:39           ` Marcel Holtmann
2023-12-22  0:03             ` Neal Gompa
2023-12-22  6:16               ` Marcel Holtmann
2023-12-24  9:03               ` Arend van Spriel
     [not found]         ` <CAF4BwTXNtu30DAgBXo4auDaDK0iWc9Ch8f=EH+facQ-_F-oMUQ@mail.gmail.com>
2023-12-19 14:42           ` Kalle Valo
2023-12-20  0:06             ` Hector Martin
2023-12-20  1:44               ` Linus Torvalds
2023-12-20  4:16                 ` Hector Martin
2023-12-20 11:05                   ` Bagas Sanjaya
2023-12-20 10:20                 ` Kalle Valo
2023-12-20 15:55                   ` Kalle Valo
2023-12-20 16:42                     ` Eric Curtin
2023-12-20 18:14                   ` Hector Martin
2023-12-20 19:36                     ` Arend van Spriel
2023-12-21  0:49                       ` Hector Martin
2023-12-21  9:57                         ` Arend van Spriel
2023-12-22  5:10                           ` Hector Martin
2023-12-22 12:25                             ` Eric Curtin
2024-01-07  9:51                             ` Arend van Spriel
2023-12-20 11:32                 ` Eric Curtin
2023-12-20 10:16 ` Paul Fertser
2023-12-20 18:02   ` Hector Martin
2023-12-23 10:28     ` Testing bits/080-wifi on BCM4345/6 (was: Re: [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password) Paul Fertser
     [not found]       ` <CAF4BwTXJWYGT+8jp9dzxmSN7wbk7xZuy4tNSQDhxJ66UzhhgWw@mail.gmail.com>
2023-12-23 15:28         ` Paul Fertser
     [not found]           ` <CAF4BwTXm62PxBTM2bNX2MkTF4XUypNJAMpxMFaQ3LP5MHrfBZA@mail.gmail.com>
2023-12-24 19:29             ` Testing bits/080-wifi on BCM4345/6 Paul Fertser
     [not found]               ` <CAF4BwTWpVRZJxQnsqKgvNxvruAnN7C=zH23bSvvJOikg5YiMsg@mail.gmail.com>
2023-12-25  2:24                 ` Daniel Berlin
2024-01-27 14:40       ` Paul Fertser [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=ZbUVxhsrbbjhOd0+@home.paul.comp \
    --to=fercerpav@gmail.com \
    --cc=asahi@lists.linux.dev \
    --cc=dberlin@dberlin.org \
    --cc=marcan@marcan.st \
    /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).