Key Handshake Failures....

jpblanch75

Look how many times this is happening in 30 seconds on my Pixel 7.

Zyxel_Kay

Hi @jpblanch75

We noticed that you have enabled Zyxel Support access on your Nebula organization. Upon reviewing your setup, we found that the MacBook Pro devices in your network (two supporting 802.11ax and one supporting 802.11ac) are currently connecting to your 5GHz SSID without issues.

Could you clarify the specific problem you’re encountering with the MacBook Pro? Are you experiencing connectivity issues with the 6GHz SSID, or is it something else? From the client list in Nebula, the listed devices appear to have stable connections. If the MacBook Pro experiencing issues isn’t one of the devices shown, could you share its MAC address? This will allow us to investigate further.

Additionally, we noticed that your 6GHz radio channel selection is locked. We recommend enabling DCS for the 6GHz band. This allows the AP to automatically select the optimal channel, which can improve performance and reduce interference.

Zyxel_Kay

Hi @jpblanch75

Key handshake failures can be caused by several factors. We recommend checking out this article to understand the possible causes and how to resolve the issue:

https://community.zyxel.com/en/discussion/17829/what-does-the-blocked-by-key-handshake-fail-log-mean-and-how-to-resolve-the-issue

Based on the event log screenshot you provided, we observed the following:

• Disconnection reason codes: 2 and 5
• Disconnection occurs consistently on the 6GHz SSID

Reason code 2 indicates "Previous authentication no longer valid," while reason code 5 indicates "4-way handshake timeout."

We recommend the following troubleshooting steps:

1. Forget the 6GHz SSID network on your Pixel 7 and reconnect, ensuring that the password is correct.
2. Ensure that your Pixel 7 is not too far from the AP. For optimal connectivity, maintain the signal strength at -65dBm or higher.
3. Since your Pixel 7 supports WiFi 6 (2.4GHz + 5GHz + 6GHz), set your 6GHz channel width to 160MHz. We also recommend using Dynamic Channel Selection (DCS) for the channel settings.

If the issue persists after trying these steps, please enable Zyxel support access on your Nebula org., and provide us with your org. and site name so we can investigate further.

jpblanch75

It was happening to my Macbook Pro as well.

I rebooted the the AP's and that didn't resolve it. Forgetting the network didn't resolve it. What resolved it was rebooting the complete network. This happened after replacing my Managed Core Switch from a Luxul to an Araknis.

Zyxel_Kay

Hi @jpblanch75

We noticed that you have enabled Zyxel Support access on your Nebula organization. Upon reviewing your setup, we found that the MacBook Pro devices in your network (two supporting 802.11ax and one supporting 802.11ac) are currently connecting to your 5GHz SSID without issues.

Could you clarify the specific problem you’re encountering with the MacBook Pro? Are you experiencing connectivity issues with the 6GHz SSID, or is it something else? From the client list in Nebula, the listed devices appear to have stable connections. If the MacBook Pro experiencing issues isn’t one of the devices shown, could you share its MAC address? This will allow us to investigate further.

Additionally, we noticed that your 6GHz radio channel selection is locked. We recommend enabling DCS for the 6GHz band. This allows the AP to automatically select the optimal channel, which can improve performance and reduce interference.

jpblanch75

I was having an issue connecting to 5ghz with the AC Macbook. This was fixed after I rebooted the network.

It doesn't matter if I use Auto channels. I am a professional integrator and have never had so much difficult getting these APs to work as good as the APs I install professionally. I monitor utilization and neighboring channels.

I am lucky if I see 500up/500down using multiple wifi devices in the same room as the AP using 80mhz bands. I need to use 160mhz to see 700up/700down.

No need to respond at this point.