From: "Dembianny, Sven (GDE-EDSO)" <Sven.Dembianny@bshg.com>
To: Sam Nazarko <email@samnazarko.co.uk>
Cc: "connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: Re: WPA connectivity issues with 1.41
Date: Fri, 26 May 2023 06:21:32 +0000 [thread overview]
Message-ID: <20230526062130.GA3841275@rbgwcw0248.bsh.corp.bshg.com> (raw)
In-Reply-To: <0a9616adc89f4fa08a0cd9840fecc582@samnazarko.co.uk>
On Mon, May 15, 2023 at 05:00:56PM +0000, Sam Nazarko wrote:
> Hi,
>
> At OSMC we recently updated to the latest stable release of ConnMan 1.41.
>
> Since then, we have reports that users were unable to connect to WiFi networks where they have WPA2 and WPA3 active. Disabling WPA3 functionality on the AP side allows the devices to connect again.
>
> The primary device being used is Raspberry Pi which doesn't appear to implement WPA3 support at this time. It's unclear for me why ConnMan is trying to connect via WPA3. We are using the standard wpa_supplicant from Debian Bullseye.
>
> If I revert the commits which introduce WPA3 functionality in ConnMan, users can again connect to an AP which has WPA2 and WPA3 enabled.
> I also tried backporting: wifi: Handle invalid-key case on WPA-SAE authentication failure to see if this helped resolve the issue but it did not.
>
> Is it expected behaviour that ConnMan should fail to connect to an AP which has WPA3 enabled where the device does not support WPA3, even if the AP also allows WPA2?
>
> Many thanks
>
> Sam Nazarko
>
>
>
>
Hi Sam,
which Wi-Fi driver/firmware is used in your setup? Maybe we are facing a
similar issue.
Info can be retrieved by:
# dmesg | grep "Firmware:"
# modinfo brcmfmac | grep "^version:"
Best regards, Sven
prev parent reply other threads:[~2023-05-26 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 17:00 WPA connectivity issues with 1.41 Sam Nazarko
2023-05-26 6:21 ` Dembianny, Sven (GDE-EDSO) [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=20230526062130.GA3841275@rbgwcw0248.bsh.corp.bshg.com \
--to=sven.dembianny@bshg.com \
--cc=connman@lists.linux.dev \
--cc=email@samnazarko.co.uk \
/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).