- Products
- Network Security
- Threat Protection
- Secure Access Service Edge (SASE)
- Cloud Security
- Endpoint Security
- Email Security
- Secure Access
-
Wi-Fi 6 Access Points
SonicWall SonicWave 600 series access points provide always-on, always-secure connectivity for complex, multi-device environments.
Read More
- Solutions
- Industries
- Use Cases
- Solutions Widgets
- Solutions Content Widgets
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
- Solutions Image Widgets
-
- Partners
- SonicWall Partners
- Partner Resources
- Partner Widgets
- Custom HTML : Partners Content WIdgets
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
- Partners Image Widgets
-
- Support
- Support
- Resources
- Capture Labs
- Support Widget
- Custom HTML : Support Content WIdgets
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
- Support Image Widgets
-
- COMPANY
- PROMOTIONS
- MANAGED SERVICES
- Contact Sales
-
- Menu
- Solutions
- Solutions Widgets
- Solutions Image Widgets
-
- Solutions Widgets
- Partners
- Partner Widgets
- Partners Image Widgets
-
- Partner Widgets
- Support
- Support Widget
- Support Image Widgets
-
- Support Widget
- Solutions
- Solutions Widgets
- Solutions Image Widgets
-
- Solutions Widgets
- Partners
- Partner Widgets
- Partners Image Widgets
-
- Partner Widgets
- Support
- Support Widget
- Support Image Widgets
-
- Support Widget
Wireless: SonicPoint EAPOL-Key timeout troubleshooting steps using SP logs and Client Connectivity
03/26/2020 
9 People found this article helpful
192,051 Views
Description
Sonic Point EAPOL-Key troubleshooting steps using SP logs...
Client Connectivity
---------------------------
We can see the below client dis-connectivity in sonic point logs when 802.1x is used (AES and TKIP).
10:02:b5:29:ce:df WPA: sending 3/4 msg of 4-Way Handshake
May 5 13:00:14 (none) daemon.debug hostapd: ath11: STA 10:02:b5:29:ce:df WPA: EAPOL-Key timeout
May 5 13:00:14 (none) daemon.debug hostapd: ath11: STA 10:02:b5:29:ce:df WPA: sending 3/4 msg of 4-Way Handshake
May 5 13:00:14 (none) daemon.debug hostapd: ath11: STA 10:02:b5:29:ce:df IEEE 802.1X: unauthorizing port
May 5 13:00:14 (none) daemon.info hostapd: ath11: STA 10:02:b5:29:ce:df IEEE 802.11: deauthenticated due to local deauth request
May 5 13:00:14 (none) daemon.debug hostapd: ath11: STA 10:02:b5:29:ce:df WPA: strict rekeying - force GTK rekey since STA is leaving
May 5 13:00:14 (none) daemon.info hostapd: ath11: STA 10:02:b5:29:ce:df IEEE 802.11: disassociated
May 5 13:00:14 (none) daemon.debug hostapd: ath11: WPA rekeying GTK
EAPOL-Key Timeout value, the default is 1 second or 1000 milliseconds.
What this means is when it comes time to exchange the EAPOL keys between the AP and client, the AP will send the key and wait up to 1 second by default for the client to respond.
After waiting the defined time value, the AP will re-transmit the key again.
1 - AP sends key attempt to the client
2 - Wait 1 second for a reply
3 - If no reply, then send eapol key retry attempt #1
4 - Wait 1 second for a reply
5 - If no reply, then send eapol key retry attempt #2
6 - If there is still not a response from the client and the retry value is met, then de-authenticate the client.
Again, as with the EAPOL-Key Timeout, extending the EAPOL-Key retry value could in some circumstances be beneficial, however setting it to the max may again be harmful as the de-authenticate message would be prolonged.
Related Articles
- How to Enable Roaming in SonicOS?
- How to Setup the SonicWave 600 series
- Configuring a Virtual Access Point (VAP) Profile for Sonicwall Access Points
YES
NO