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 @Hank21, your suggestion to enhance the log level was really helpful. I've found a faulty Xiaomi Screen Bar, which tried to connect every 20s to the Wifi and failed to do so. Once I had it reset these problems stopped.
- Copy Link
- Report Inappropriate Content
Hi @Hank21
I've tried the latest Beta for the EAP653 after I've encountered the same problem mentioned here https://community.tp-link.com/en/business/forum/topic/628596 and https://community.tp-link.com/en/business/forum/topic/641576
I've got three EAP653 in total and flashed them all with the same version 1.0.90 Build 20231012 Rel. 31553. Since I've installed the update I've got no problems with unresponsive Accesspoints. However, a few other side effects occurred now way more often:
Last time I've checked my Omada Controller Log I've seen a huge number of association failures:
I've read that I should reduce the transmitter power, so its now to medium. I've got two APs quite close together, but separated with a big concrete wall of a staircase, but this doesn't seem to affect these failures.
Additionally I've had download problems that only occurred when connected via Wifi, but not via LAN. So I could rule out my internet connectivity. Wifi connection was quite good at around 800mbps during that time so it shouldn't be the issue. It happened on two separate Macs connecting to the same AP. Once they connected via LAN the download was fast again.
- Copy Link
- Report Inappropriate Content
Hi @Centurio,
Thank you so much for taking the time to report the issue to our community!
Could you check the Logs to see what time period these 18772 errors are generated?
The error message "Association Timeout" generated may be caused by the client devices entered the wrong password when connecting to the SSID, or there are packet loss during the wireless association handshake process, detailed info please refer to here.
According to your description, the two EAPs are quite close to each other, can you adjust the position of the EAPs or try the WLAN optimization?
Is there any specific effect on your client's usage, such as not getting IP/no network, etc.?
- Copy Link
- Report Inappropriate Content
Hi @Hank21,
I cannot move the EAPs, since they are already in their place for over an year without seeing this authentication error issue.
During that time no devices were added to my network, so that shouldn't be an issue of wrong passwords. I've tried the AI Wifi Optimization in the past but it did not help much, so I've put each AP on separate channels with enough space to the next one to avoid overlaps in the frequency bands.
In the meantime, I did not check Omada again. But when I wanted to check the log as you suggested, I've seen 20221 new authentication failures. I've noticed this morning, that my iPhone was unable to use the Wifi and asked me, if I'm really connected to the internet. What place should I check the logs? I've selected the organization with the affected failures and clicked on logs. I don't see any error messages, except the ones where one of my EAP653 started to disconnect regularly and I flashed the beta firmware to solve this. I don't have any messages on warning and on Info I only got messages of devices connecting/disconnecting, which looks quite normal I assume.
However, what's interesting is that these 20221 new authentication failures came all from the same EAP653 which started to misbehave and caused my journey of flashing beta firmware in the first place. Do you need anything specific from this AP only? I've pulled the Device Info for this AP and could send it to you.
- Copy Link
- Report Inappropriate Content
Hi @Centurio,
Centurio wrote
In the meantime, I did not check Omada again. But when I wanted to check the log as you suggested, I've seen 20221 new authentication failures. I've noticed this morning, that my iPhone was unable to use the Wifi and asked me, if I'm really connected to the internet. What place should I check the logs? I've selected the organization with the affected failures and clicked on logs.
Please go to Logs > Notifications > Clients, and keep all options checked. So we can analyze the reasons of the error messages generation.
Centurio wrote
I don't see any error messages, except the ones where one of my EAP653 started to disconnect regularly and I flashed the beta firmware to solve this. I don't have any messages on warning and on Info I only got messages of devices connecting/disconnecting, which looks quite normal I assume.However, what's interesting is that these 20221 new authentication failures came all from the same EAP653 which started to misbehave and caused my journey of flashing beta firmware in the first place. Do you need anything specific from this AP only? I've pulled the Device Info for this AP and could send it to you.
Are three EAP653 still running the latest Beta firmware 1.0.90 Build 20231012 currently? How did you connect them? Wired? Wireless? How did you power them?
How did you recover the iPhone internet connection? By reconnecting manually or automatically? Is it working properly now?
- Copy Link
- Report Inappropriate Content
The client logs where on the default levels and I've set them as you requested. In the meantime it showed today 19615 failures for the affected AP.
All three EAP 653 run 1.0.90 Build 20231012 Rel. 31553 and are powered via PoE on a TL-SG2008P v2.0 with Firmware 2.0.7 Build 20230602 Rel.73473.
The iPhone recovered itself after a while, at least when I've taken a look the next time I've checked it. Its currently working.
- Copy Link
- Report Inappropriate Content
Hello @Centurio,
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID231242565, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hi @Hank21, your suggestion to enhance the log level was really helpful. I've found a faulty Xiaomi Screen Bar, which tried to connect every 20s to the Wifi and failed to do so. Once I had it reset these problems stopped.
- Copy Link
- Report Inappropriate Content
Hi @Centurio,
Thank you for your valued sharing! 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
Hi @Hank21,
I've got a new problem today. One of my EAP653 decided to be unresponsive to the health requests and stopped serving data. Devices connected to it had a dropped connection until I've unplugged that AP and restarted it. Its the only AP that was unresponsive. The other two APs are using the same beta firmware and are now online for 34 days withour reboots.
- Copy Link
- Report Inappropriate Content
i have the same issue with the new firmware for eap 650 v1 that was released
a lot of devices won't connect to ssd or don't receive an IP
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2632
Replies: 14
Voters 0
No one has voted for it yet.