WiFi Authmodes are being shuffled on v5.1.1 (IDFGH-11372) #12517
Comments
github-actions
bot
changed the title
|
Retested with latest master (commit 294c2bd). |
|
@sarveshb14 @nachiketkukade Any update? Will v5.1.2 fix this issue? |
|
@AxelLin sorry that not fix this in v5.1.2. Currently esp-idf consider WPA/WPA2/WPA3 an invalid auth mode. Will consider how to fix this, and add it in v5.2 and v5.1.3. |
|
Hi @bill88t @AxelLin, Sorry for making you wait. As per WPA3 Specification,
I agree that scan results should not show authentication mode of such AP as We will consider security of such AP as |
|
|
|
Also, the network |
|
Hi @bill88t , Can you please
ESP-device should be able to connect with WPA3-SAE security.
If phone sees |
|
I ran the connection example from C6, S2 and C3, all of which say it's WPA2-PSK, which is correct. The network configuration is as follows:
I also set my thinkpad in "monitor mode" and captured all the wifi 802.11 traffic. I do not know how to read it though. |
|
Thank you providing the capture. Does this same configuration shows |
Alright, sorry for the wait, I captured channel 1 this time. ch1.zip
Yes. |
|
|
|
Yes, it should use WPA2. I don't think WPA3 would work for these networks.
Maybe it should be reported as |
You are right. If AP does not follow WPA3, we will treat this AP as |
espressif-bot
added
Status: Done
|
Hi @bill88t , we have merged above discussed changes into master branch now. Thank you for your support |
|
is it already in master? we are also affected by this bug and I would like to know which commit in master fixed the issue to start my rebases on |
|
I don't think so. I did test master 2 weeks ago with the latest commit and didn't see any changes. It's possible the fix has been applied downstream and we will see it with the release. I don't know how espressif works. |
|
Hi @0xFEEDC0DE64 , @bill88t . Sorry for making you wait. Fix is merged in internal repository. Push to github It is stalled due to internal CI. It will soon be available on github. |
|
No problem, thanks for letting us know! |
…or bugfixes - Add support for WPA3 + WPA3_EXT_PSK mixed mode - Improvements in scan and connect path as per specifications along with minor bugfixes - When AP advertises all PSK modes (WPA, WPA2 and WPA3), make sure that station treats it as WPA2_WPA3_PSK mixed mode. Closes #12517
It is available now. (615d928a) |
|
Can confirm, this fixed the issue. Thanks! |
@sarveshb14 v5.1.3 does not include this fix. |
|
I can confirm an update to latest esp-idf has fixed all problems for us, thank you |
Answers checklist.
IDF version.
v5.1.1
Espressif SoC revision.
ESP32-C6 ESP32 ESP32-S3 (and probably the rest)
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
WeAct ESP32-C6, M5Stack Timer Camera X, Adafruit Feather ESP32-S3 TFT
Power Supply used.
USB
What is the expected behavior?
A wifi scan from my trustworthy thinkpad returns:
What is the actual behavior?
Using wifi scan example (examples/wifi/scan) as is, with just flash parameters and speed changed, 10cm from the thinkpad's scan spot:
Steps to reproduce.
Unkown.
Debug Logs.
No response
More Information.
The network "KeyFalse" in question is a linux computer with NetworkManager doing the hotspot with it's motherboard's wifi.
The full connection parameters are as follows:
Under random chance, during the day, other networks, frequently "Feline34" which is also mine appears also as OPEN. That network is a standard isp provided router and it's pretty old.
This issue is in fact not a dupe of #11202 as there are no Enterprise networks in the vicinity.
The text was updated successfully, but these errors were encountered: