NWA130BE - "deauthenticated by key handshake fail" with certain devices

Hi @colonie ,

Due to the connection issues occurring only with the Zero 2W, we recommend the following steps:

1. AP Firmware Update: Ensure your NWA130BE is running the latest firmware version 7.00P1
2. Wi-Fi Driver Update (Raspberry Pi): The issue could be related to an outdated Wi-Fi driver on the Raspberry Pi Zero 2W. Try updating the Wi-Fi driver on your Raspberry Pi Zero 2W devices to the latest version available.
3. Credentials: Carefully check your password when connecting the Zero 2W to the SSID.
4. WPA2/WPA3 Compatibility: Double-check the security settings on your NWA130BE. Ensure that the configured WPA2/WPA3 settings are compatible with the Raspberry Pi Zero 2W. You can try temporarily switching to a different security protocol (e.g., open or WPA2 personal only) to see if it resolves the issue.

If the problem persists, please collect the NWA130BE’s diagnostic file and provide us with the Zero 2W’s MAC address and the time of the connection attempt. We will check and inform you if we find anything.

HI @colonie ,

After reviewing the diagnostic file, there are no abnormal issues with the AP. Here are some steps you can try on the radio profile. The path: Configuration > Object > AP Profile > Radio > Edit

1. Adjust the radio mode to 802.11b/g.
2. Disable the A-MPDU and A-MSDU options in advanced settings.
3. After applying the new settings to the AP, forget/delete the SSID (Wi-Fi) on the Pi Zero 2W’s Wi-Fi list and reconnect.

If the issue persists, we recommend the following steps to further investigate the connection logs:

1. Connect the Pi Zero 2W to the Wi-Fi multiple times.
2. Immediately collect a new diagnostics file to ensure the related logs are retained.

Additionally, you mentioned that other devices and Raspberry Pi models can connect to your Wi-Fi without issue using the same configuration. We have found many Wi-Fi connectivity issues with the Pi Zero 2W in the Raspberry Pi forum. Therefore, we also recommend reaching out to Raspberry Pi support to clarify if it is not an end-device issue.