public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Yuxuan Shui <yshuiv7@gmail.com>
To: denkenz@gmail.com, ys3al35l@gmail.com
Cc: iwd@lists.linux.dev, yshuiv7@gmail.com,
	arend.vanspriel@broadcom.com, prestwoj@gmail.com
Subject: Re: [RFC PATCH v1 0/2] External Auth support
Date: Sat, 21 Sep 2024 19:58:54 +0100	[thread overview]
Message-ID: <20240921185902.170612-1-yshuiv7@gmail.com> (raw)
In-Reply-To: <20240823174220.498594-1-denkenz@gmail.com>

Hi,


On Fri, Aug 23, 2024 at 12:42 PM Denis Kenzior <denkenz@gmail.com> wrote:
>
> This series implements External Auth support on Full MAC cards that do
> not support SAE offload.  I have not been able to test this fully since
> the brcmfmac firmware on the RPi 5 does not actually work properly.
> Maybe some enterprising person can test it on a firmware that does work?
>
> Denis Kenzior (2):
>   netdev: external auth support
>   sae: Allow ability to force Group 19 / Hunt and Peck
>
>  src/netdev.c      | 258 +++++++++++++++++++++++++++++++++++++++++-----
>  src/nl80211util.c |   4 +-
>  src/sae.c         |  20 ++++
>  src/sae.h         |   3 +
>  src/wiphy.c       |  19 ++--
>  5 files changed, 263 insertions(+), 41 deletions(-)
>
> --
> 2.45.2
>

I tested this on an RPi5 too, and indeed I am having the same problem as KeithG
as well. However I managed to get some debug information from brcmfmac when
running wpa_supplicant. Interestingly wpa_supplicant gets the same -52 error as
well, which it reports as an authentication timeout. But if I ask it to try
again, it will connect successfully, and there is no external auth related log
the second time around.

So I suspect this is a firmware bug, but it should be relatively easy to
workaround I think? Basically we also add a timeout and retry.

BTW, with the current version of this patch, if I ask iwd to disconnect after
getting the -52 error, iwd segfaults.

Regards,
Yuxuan Shui

  parent reply	other threads:[~2024-09-21 18:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 17:41 [RFC PATCH v1 0/2] External Auth support Denis Kenzior
2024-08-23 17:41 ` [RFC PATCH v1 1/2] netdev: external auth support Denis Kenzior
2024-08-26 12:03   ` James Prestwood
2024-08-23 17:41 ` [RFC PATCH v1 2/2] sae: Allow ability to force Group 19 / Hunt and Peck Denis Kenzior
2024-08-24  0:38 ` [RFC PATCH v1 0/2] External Auth support KeithG
2024-08-24  3:21   ` Denis Kenzior
2024-08-24 16:20     ` KeithG
2024-08-24 23:32       ` KeithG
2024-08-26 15:43         ` Denis Kenzior
2024-08-26 16:54           ` Arend Van Spriel
2024-09-02 19:32             ` KeithG
2024-09-07 18:43               ` KeithG
2024-09-21 18:58 ` Yuxuan Shui [this message]
2024-09-22  3:35   ` Denis Kenzior
     [not found]     ` <CAG17S_NOs=rdUFsFRk4ZPsC=GER2J7nHikGEw=3AW0SBYHUEfg@mail.gmail.com>
2024-09-22  4:23       ` Denis Kenzior
2024-09-22  6:09     ` Arend Van Spriel
2024-09-22 15:36       ` KeithG
2024-09-22 16:20         ` Arend Van Spriel
2024-09-22 16:29           ` KeithG
2024-10-10 15:38             ` KeithG
2024-12-11 22:59               ` Jeremy Blum
2024-12-12 14:33                 ` KeithG
2024-09-22 18:56 ` KeithG
2024-09-22 21:01   ` 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=20240921185902.170612-1-yshuiv7@gmail.com \
    --to=yshuiv7@gmail.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.com \
    --cc=ys3al35l@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