Solution EAP653 Becomes Unreachable Or Clients Fail to Connect SSIDs After Upgrading to 1.0.9 Build20230814
Solution EAP653 Becomes Unreachable Or Clients Fail to Connect SSIDs After Upgrading to 1.0.9 Build20230814
This Article Applies to
EAP653 v1/v1.6_1.0.9_Build 20230814
Issue Description/Phenomenon
We have recently received feedback regarding some abnormal behaviors of their EAP653 v1 after upgrading its firmware 1.0.9 Build 20230814. You may find the EAP stops functioning properly after a few days of operation, and the issue may manifest in the following ways:
-
There might be massive packet loss.
-
EAP devices becoming unreachable or unmanageable.
Related Post: eap653 needs reboot every 3-4 days with v1.0.9 fw - memory leak?
-
Clients are unable to connect to any of the network SSIDs and are not receiving IP addresses.
Related Post: EAP653(EU) v1.0
In the aforementioned situations, a simple reboot resolves the issue temporarily, but it tends to reoccur.
Available Solutions
These abnormal behaviors will be corrected or optimized in the subsequent firmware very soon.
Upon waiting for the new firmware to correct these issues, you may upgrade the following Beta firmware as a workaround.
Beta Firmware Download
EAP653(EU/US)_V1_1.0.90 Build 20231012 (Beta)
Beta Release Note:
1. Fixed the EAP unreachable and the clients fail to connect SSIDs issue based on the current firmware 1.0.9 Build 20230814.
2. Please be sure you have read the Beta Test Agreement before proceeding!
Recommended Threads
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Current Available Solutions to Omada EAP Related Issues [Constantly Updated]
Current Available Solutions to Omada Router Related Issues [Actively Updated, Post for Subscription]
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Mariomark1541，
Mariomark1541 wrote
a lot of devices won't connect to ssd or don't receive an IP
May I know whether these devices are all 2.4G clients?
If so, the PMF feature was supported since Omada Controller v5.7, which requires to upgrade the EAP device firmware to take effect. The previous firmware 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 EAP650 new firmware is adapted to controller 5.9, which supports the PMF feature, so changing PMF from "Mandatory" to "Capable" can fix the issue. If your clients still has connection issue with the "Capable" option, you may disable PMF for the network.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Hank21 found it and looks like it was the solution!!
- Copy Link
- Report Inappropriate Content
Hi @Mariomark1541，
Thank you for your valued feedback! Glad to hear that your concern was resolved finally.
Hope you enjoy the Internet with TP-Link products and have a great day!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2689
Replies: 14
Voters 0
No one has voted for it yet.