EAP225 V3 FW bug ?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi TP,
I am using EAP225 V3 in stand-alone mode, managed by Web-UI only. In the WiFi network I am using a multi-room audio system (Block) which can be managed by the Undok App. After reboot of the AP everything works fine with the audio system. But then after > 10 (?) hours (audio system on or on stand-by) it gets somehow disconnected to the Undok App (device not found) - although it is still in the active client list of the EAP AP. I can also switch the audio system on manually and it works fine with Internet radio. But it cannot be found on the WiFi network anymore by a network scan. The only way to resolve this issue is a reboot of the EAP225.
To me this looks like a bug in the EAP V3 FW ... like as if the SSID isolation gets activated after a while automatically/accidentially/by false trigger. Can anyone of the TP team please create a support ticket on this case? Thank you.
Cheers, Manfred
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, I am having very similar issues as described in this thread. I am running an EAP225 connected to a Netgear router. I manage it via the web interface and it's on firmware 2.3.0 Build 20180628 Rel. 54512(4555).
The netgear is configured to provide DHCP, but I also have a couple of devices with a static IP as well.
After a reboot of the EAP225 the network functions correctly. I can ping all my devices and everyone is happy. However after some time (maybe around the 10 hours described by the OP) then all devices connected to the EAP225 become unreachable. They cannot be pinged, they do not respond to ARP requests (by checking wireshark), however they can continue to ping out to the router, and internet devices too. This affects all devices, such as laptops assigned an address via DHCP, or my IOT devices which have a static address.
Everything works fine if I enable WiFi on the router instead of the EAP225 - so to me that indicates a problem with the EAP225 rather that my network configuration. The symptoms do seem very similar to have SSID isolation enabled - even though it is not.
Can this be investigated further? Thank you.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
We have tested in our lab but we didn't reproduce your issue, please upgrade the firmware to the latest version, and then check if the problem still exists, if yes, please tell us and we will try our best to help you with your issue.
- Copy Link
- Report Inappropriate Content
Hi,
Thank you for your reply. That is the latest firmware according to my region: https://www.tp-link.com/uk/support/download/eap225/#Firmware
The problem still persists for me - after a certain amount of time (many hours), devices connected to the EAP225 are no longer reachable (unable to ping in). They continue to retain connection and can ping out though. A reboot of the EAP225 fixes the issue for some futher period of time until it stops working again.
Can you advise where I can obtain a newer firmware version for my region (UK)?
Many thanks.
- Copy Link
- Report Inappropriate Content
bjh_101 wrote
Hi,
Thank you for your reply. That is the latest firmware according to my region: https://www.tp-link.com/uk/support/download/eap225/#Firmware
The problem still persists for me - after a certain amount of time (many hours), devices connected to the EAP225 are no longer reachable (unable to ping in). They continue to retain connection and can ping out though. A reboot of the EAP225 fixes the issue for some futher period of time until it stops working again.
Can you advise where I can obtain a newer firmware version for my region (UK)?
Many thanks.
Hi，
You can download the latest firmware in our global website: https://www.tp-link.com/en/support/download/eap225/#Firmware
- Copy Link
- Report Inappropriate Content
jonas wrote
Hi，
You can download the latest firmware in our global website: https://www.tp-link.com/en/support/download/eap225/#Firmware
Thank you, I have installed that now, and I will see how things go and let you know what I find.
- Copy Link
- Report Inappropriate Content
Hi,
Since installing the latest version of the firmware, I am still getting the same problem - devices connected via the EAP225 are no longer accessible via ping (although they are still connected, and can access the internet) after a while (eg. overnight.)
Are there any further things I can try to help you diagnose the issue?
Thanks.
- Copy Link
- Report Inappropriate Content
Hi,
as stated above I have exactely the same issue and purchased another EAP225 just to make sure that it's not a hardware fault. But even with the new EAP225 V3.1 the issue persists. On the 2.4GHz network the client (a multi-room audio system with internet radio) is not "visible" after 10-12 hrs of operation, although visible in the EAP's client list. A hard reboot resolves the issue but after the same period trouble starts again. All other clients remain fully operational but you can't ping them anymore.
As a matter of blank despair I connected the multi-room audio system to the 5GHz network. And now I observe 2 interessting effects:
1) the multi-room audio system works now since 17 hrs .... no problem, no interruption, always visible and can be pinged
2) the host name is now properly visible (wasn't on 2.4GHz) together with my home network domain name
I think this is the ultimative evidence that the Firmware is buggy !
Cheers,
Manfred
- Copy Link
- Report Inappropriate Content
Have you tried configuring your 2.4ghz radio to only do 802.11 B/G? In my case that allowed some clients to connect...
But, I agree, the EAP225 has issues. I do not know if they are hardware or firmware but they are certainly real.
I am having so much trouble with this AP that I am considering just shelving it.
- Copy Link
- Report Inappropriate Content
Looks like disabeling air time fairness on the 2.4Ghz helped in my case. Still evaluating.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 6520
Replies: 26
Voters 0
No one has voted for it yet.