Association Timeout after Firmware upgrade to 1.2.3 Build 20230922 Rel. 67667
Last night I saw there was a firmware upgrade for my EAP610-Outdoor so I went ahead with the upgrade. Since then I see the logs filling up with Association Timeout errors from my 2.4GHz IoT devices. I'm now left with only one AP I can have 2.4GHz turned on in the house. The EAP650 also has this problem and has never been fixed yet (https://community.tp-link.com/en/business/forum/topic/610000)
Please provide a solution!
Hello @Bromo，
Thank you so much for taking the time to report the issue to our community!
The PMF feature was supported since Omada Controller v5.7, which requires to upgrade the EAP device firmware to take effect. The previous firmware you used is not adapted to controller 5.7, that is, the previous firmware doesn't support the PMF feature, thus the PMF configuration with "Mandatory" won't affect the connection of non-PMF-capable clients.
While the EAP610-Outdoor 1.2.3 new firmware is adapted to controller 5.9, which supports the PMF feature. It seems that your IoT client is non-PMF-capable, so changing PMF from "Mandatory" to "Capable" can fix the issue. If your IoT still has connection issue with the "Capable" option, you may disable PMF for the IoT network.
Hello @Bromo，
Thank you so much for taking the time to report the issue to our community!
The PMF feature was supported since Omada Controller v5.7, which requires to upgrade the EAP device firmware to take effect. The previous firmware you used is not adapted to controller 5.7, that is, the previous firmware doesn't support the PMF feature, thus the PMF configuration with "Mandatory" won't affect the connection of non-PMF-capable clients.
While the EAP610-Outdoor 1.2.3 new firmware is adapted to controller 5.9, which supports the PMF feature. It seems that your IoT client is non-PMF-capable, so changing PMF from "Mandatory" to "Capable" can fix the issue. If your IoT still has connection issue with the "Capable" option, you may disable PMF for the IoT network.