I just received a second Pi Zero 2 W I ordered due to having an issue with my previous one, however this one's behaviour is identical.
I have had my PZ2W for several years now (2 or 3?) and it has been working perfectly fine on WiFi. Recently, I moved home and have a new SSID that I wanted to connect it to, so using ethernet I connected into it and reconfigured it for the new SSID. I believe the Pi has also been updated since I last used it, so I believe the OS version I brought with me to the new place was never successfully used on a network.
The new SSID is configured for 2.4GHz only and uses WPA2 security. The PZ2W will attempt to handshake, and then fails miserably at some key exchange stage. If I configure the SSID to be an open network without security, the PZ2W will connect to this however will seemingly not transcieve packets (no DHCP requests occur) and after a short time, the AP kicks it off due to a timeout.
For these tests, I have been using a mixture of WPSD (HAM hotspot distro) and Raspberry Pi OS Lite (64 Bit). Regardless of which OS I use, the behaviour is identical.
When in AP mode (WPSD automatically switches to this mode when it fails to connect to an AP, in order to reconfigure via web interface), the PZ2W can be connected to and operates without fault. This issue only occurs when in station mode, and doesn't seem to matter what AP it is connecting to. I have so far tried 3 different APs.
One of the APs, an OpenWrt device, I saw this message in the log when the PZ2W failed to connect with the AP configured for WPA2: code]received EAPOL-Key msg 2/4 with invalid Key Data contents[/code]
I didn't capture any additional logs, however can set up to do so on both the PZ2W and AP end if necessary.
In short, the setup is a PZ2W with a 16GB SD card, flashed with Raspberry Pi OS Lite (64 Bit) with Raspberry Pi Imager v1.8.5, configured for 2.4GHz WiFi in with a GB Wireless LAN Country, SSH enabled, and an OpenWrt AP configured for 2.4GHz only with WPA2 security (though I have tried other APs too)
I have had my PZ2W for several years now (2 or 3?) and it has been working perfectly fine on WiFi. Recently, I moved home and have a new SSID that I wanted to connect it to, so using ethernet I connected into it and reconfigured it for the new SSID. I believe the Pi has also been updated since I last used it, so I believe the OS version I brought with me to the new place was never successfully used on a network.
The new SSID is configured for 2.4GHz only and uses WPA2 security. The PZ2W will attempt to handshake, and then fails miserably at some key exchange stage. If I configure the SSID to be an open network without security, the PZ2W will connect to this however will seemingly not transcieve packets (no DHCP requests occur) and after a short time, the AP kicks it off due to a timeout.
For these tests, I have been using a mixture of WPSD (HAM hotspot distro) and Raspberry Pi OS Lite (64 Bit). Regardless of which OS I use, the behaviour is identical.
When in AP mode (WPSD automatically switches to this mode when it fails to connect to an AP, in order to reconfigure via web interface), the PZ2W can be connected to and operates without fault. This issue only occurs when in station mode, and doesn't seem to matter what AP it is connecting to. I have so far tried 3 different APs.
One of the APs, an OpenWrt device, I saw this message in the log when the PZ2W failed to connect with the AP configured for WPA2: code]received EAPOL-Key msg 2/4 with invalid Key Data contents[/code]
I didn't capture any additional logs, however can set up to do so on both the PZ2W and AP end if necessary.
In short, the setup is a PZ2W with a 16GB SD card, flashed with Raspberry Pi OS Lite (64 Bit) with Raspberry Pi Imager v1.8.5, configured for 2.4GHz WiFi in with a GB Wireless LAN Country, SSH enabled, and an OpenWrt AP configured for 2.4GHz only with WPA2 security (though I have tried other APs too)
Statistics: Posted by ahorner — Wed Dec 11, 2024 7:13 pm
