Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pi 4 fails to connect to wpa3-psk networks #186

Open
jay0lee opened this issue Jul 25, 2020 · 2 comments
Open

pi 4 fails to connect to wpa3-psk networks #186

jay0lee opened this issue Jul 25, 2020 · 2 comments
Labels

Comments

@jay0lee
Copy link

jay0lee commented Jul 25, 2020

Awesome work on Gentoo for the Pi 4!

I had issues connecting to WiFi where the Pi4 could see SSIDs but would never associate. It wasn't until I went into Advanced networking that I realized the Pi4 was trying to use wpa3-psk with my Google Nest WiFi router (wpa3 is turned on for the router but is backwards compatible with wpa2).

I saw no such issues with Noobs or Arch on the Pi4 so I suspect Gentoo isn't quite ready for wpa3 yet. Two possible solutions here:

  • tell Gentoo to exclude wpa3 throughout the stack so that wpa2 is used even if the AP supports wpa3.
  • googling implies the pi 3 and 4 hardware may be capable of supporting native wpa3 but support is needed in the kernel and wpa_supplicant (maybe network manager also?)

Glad to grab logs if that'd help.

@DaddyBurrito72
Copy link

@jay0lee
Hi, that's interesting information, thank you for sharing. This educated me more on the wpa3 certification.
After reading your post a few times, and reading more about the standard, I just wanted to try to confirm that I think I understand the situation:

  1. It sounds like there's no support at all yet for wpa3 on any Pi distribution, because support is needed in the kernel and wpa_supplicant to support the specific hardware and components.
    Is that correct? It's not just the Gentoo GNU/Linux, not genpi64, but the standard is just not implemented yet (for RPI). Right? Just making sure.
  2. It sounds like the difference here, is, genpi64 is trying to use something implementing wpa3 where noobs and arch are not.
    Did I get that correctly also?
    Here's the part I am not catching:
    If there exists the need for a kernel module, and/or an update to wpa_supplicant to support the new standard, what do we think the genpi64 distribution is trying to implement that is supporting wpa3? What's different about it from noobs or some other pi distribution?
    Or perhaps were you able to get another Linux distribution to connect using the wpa3 (maybe x86_64 or something else, not for RPI)? It looks like the people in Redmond have something working, was there another arch (besides RPI) that has implemented the [no-so] new certification?
    Good info! Interesting stuff- thanks again for sharing! I would certainly still try to give the logs a second set of eyes if you still want to post them.

@sakaki- sakaki- added the EOL label Oct 30, 2020
@sakaki-
Copy link
Owner

sakaki- commented Oct 30, 2020

30 Oct 2020: sadly, due legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the images may be of use still in certain applications); however, there will be no further updates to the underlying binhost etc., nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice.

For further details, please see my post here.

Many thanks for your interest in this project!

With sincere apologies, sakaki ><

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants