EAP615-Wall(US) v1.0 has issues with 1.2.3 Firmware
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I saw the upgrade prompt in the controller, and upgraded my 3 EAP-615WALL APs. Immediately upon upgrading, some devices would not reconnect under any circumstances, all failing with errors pointing to the password being incorrect. However, none of these devices had passwords changed, and other devices using the same password could connect with no issues.
Additionally, 2 of the 3 EAP-615WALL devices had problems re-adopting to the network. They are all are connected via Ethernet (POE) to a TL-SG2210P v3.20 switch. no issues with POE were noted by the switch. After unplugging/replugging to Ethernet, eventually those two would connect, but be meshed, and not connected via Ethernet.
Upon manually downloading the 1.1.6 firmware and installing that back on the APs, immediately everything worked correctly, and previously non-connecting devices connected with no issues.
It seems there are still some issues with the 1.2.3 firmware, at least in respect to the EAP-615WALL 1.0 devices.
@Hank21
> If you re-type in the password on these client devices, can they reconnect EAPs?
No, they would continue to fail with an error indicating that the password was incorrect. I can confidently say that it was not, as I disconnected one of the working devices and reconnected it with the same password to ensure this was not the case.
> Do you mean EAPs can not be adopted via Ethernet? What is the error message when they show "Adopted Failed"?
Here's a screenshot of the logs from that timeframe, with the first (bottom) item being immediately after the firmware update from 1.1.6 to 1.2.3.
This issue is only occuring with this one AP. All of my 615 APs are v1 devices purchased at the same time, and this is the first real issue I've had with any of them. I downgraded them all back to 1.1.6 just before the events happening at 5:47 in the log, but this one device still has issues. It was rock solid before the 1.2.3 upgrade.
My controller is the OC300.
Controller Version
If I can at all solve this without needing to physically remove the device, that would be preferred, as it's in a somewhat inaccessible location (20ft ceiling).
Thanks!
Hi @Skiller00，
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 EAP615-Wall 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.
