Business Community > General Discussion > WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment
< General Discussion

WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment

WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment

WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment
WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment
2025-05-24 14:43:57
Model: EAP660 HD   EAP245   EAP610  
Hardware Version: V1
Firmware Version: 1.4.2

We are experiencing recurring network issues across several restaurant installations using TP-Link Omada devices. I am responsible for configuring stable networks for our POS software solution. Our standard setup includes an ER605 router and an EAP245 access point, fully managed via Omada Cloud Controller with an active license.

Our POS system functions in a client-server model within the LAN. The server, which is an Android-based POS terminal, communicates via WebSocket with Android tablets and handheld POS clients.

Issue Summary:

Clients intermittently lose connection to the server at the application level, although they remain connected to the Wi-Fi and maintain internet access. The issue is temporarily resolved by changing the client’s IP address.

Technical Setup:

  • Devices use IP reservations via DHCP from the Omada ER605.

  • No static IPs are configured manually.

  • The network is managed entirely from the Omada Cloud.

  • Fast Roaming is only enabled where more than one AP is deployed.

  • Firmware is always up to date on both router and AP (currently version 1.3.1 on ER605).

Key Observations:

  • The issue affects different client models, but inconsistently.

  • In one case, a client tablet lost communication with the server, yet maintained ping to other clients, while the server stopped responding to its IP.

  • Communication uses WebSockets, not raw TCP sockets.

Suspected Causes or Areas for Clarification:

  1. Could ARP cache or stale entry protections in the ER605 or Omada Cloud block communication from a device using the same IP over time?

  2. Is there an ARP timeout setting or clearing mechanism available in Omada Cloud for LAN IP mappings?

  3. Have recent updates to the cloud controller or firmware introduced stricter rules for IP communication or WebSocket traffic on the same subnet?

  4. Are there any known limitations or settings related to Android-based LAN WebSocket communication in Omada-managed networks?

Request:

We would like confirmation on whether Omada Controller, ER605, or EAP245 may have any behaviors that would explain this LAN-level block between devices. Additionally, we ask for guidance on any configuration practices or tools that could help mitigate or trace this issue, especially regarding ARP handling or session management.

Thank you for your support and guidance.

  1      
 
  1      
 
#1
Options
4 Reply
Re: WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment
2025-05-29 06:19:47

Hi  @RojoAnt 

 

Thanks for posting here.

 

This appears to be a local network communication interruption issue. The problem might be associated with the server, client, or AP (Access Point).

 

To determine whether the issue is caused by the AP, please test with another AP for comparison.

You can unplug one EAP from the network, and plug a third-party access point in, and check in the issue persists.

 

Additionally, could you please confirm:

1. Is the server connected via wired Ethernet?

2. Does the clients only support 2.4GHz Wi-Fi? If so, wireless interference could be a possible cause. We recommend optimizing the wireless settings following the guidelines .

How to optimize wireless performance of EAP products

 

3. When did you first notice this problem? Did it occur right after the system was installed? Or was it working fine before, but started happening after upgrading certain devices?

4. Will this issue occurs on all the mentioned android tablets and handheld POS clients?

5. When the issue happened, will it affected on all clients simultaneously, or some are still working correctly?

6. In one case, a client tablet lost communication with the server, yet maintained ping to other clients, while the server stopped responding to its IP.

>>>What about other cases? What's the ping result to the server's IP?

 

To answer your questions:

  1. Could ARP cache or stale entry protections in the ER605 or Omada Cloud block communication from a device using the same IP over time? >>>>Possible, but we can't say it for sure atm.

  2. Is there an ARP timeout setting or clearing mechanism available in Omada Cloud for LAN IP mappings? >>>Nope, we don't have this kind of config.

  3. Are there any known limitations or settings related to Android-based LAN WebSocket communication in Omada-managed networks? >>>No.

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  1  
  1  
#2
Options
Re: WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment
2025-05-29 22:58:33

   

Hi @Vincent-TP, thank you for taking the time to reply, and of course I’ll address your questions to help find a possible solution.

Regarding the first issue you mentioned, I can tell you that the problem is happening at multiple locations. I manage several sites (restaurants), and this issue occurs at six different ones. What they have in common is that they all use the same router model and are connected to the Omada Cloud Manager. At the moment, it’s not possible to connect a third-party EAP, but I will try to run that test.

To confirm:

  1. That’s a good question — when the server is connected via Ethernet cable, the issues are not as consistent, and in some cases, they don’t occur at all. This has been one of the temporary solutions I’ve implemented: connecting the server via Ethernet.

  2. Many of the POS devices only support 2.4 GHz connections. However, I also have 5 GHz networks active at sites with Android tablets. The error happens more frequently with the POS devices.

  3. This problem started around two weeks ago. The only changes I noticed in Omada were some updates for certain EAP models, and one thing I’m certain about is that all sites received an update to the Omada Cloud Manager. I hadn’t experienced this issue before. There was also a POS software update during those two weeks — we’re investigating that too, and it has resolved some connection issues between the server and clients. However, nothing related to this was modified in the previous version’s release.

  4. Yes, especially with the POS devices, it’s difficult to reconnect to the server. While the tablets do disconnect, they manage to reconnect. On the POS clients, unless I change the IP address, it’s not possible to reconnect.

  5. It affects all of them simultaneously. During testing, we noticed that this issue happens when the server initially loses connection — it forces all client devices to disconnect from the server, although they never lose connection to the network.

  6. We investigated this one thoroughly — it’s a specific case with Samsung devices where Android blocks repeated access attempts from other IPs to the device. In other cases, we don’t lose ping.

I hope these answers give you a better understanding of the case. I'm willing to provide all the information you need, as I’m still experiencing this issue to this day.

  0  
  0  
#3
Options
Re: WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment
2025-05-30 02:36:03

Hi  @RojoAnt 

 

Thanks for the detailed reply.

 

Will the Websocket packets be send to the cloud?

 

What's the model number of the EAPs you are using?

 

You mentioned that the issue occurs after you update the firmware.  If you don't mind, please choose a site to test: downgrade the firmware to the previous one, and check if the issue persists.

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#4
Options
Re: WebSocket-based Application Fails on LAN Despite Stable Network — TP-Link Omada Deployment
2025-06-09 06:33:07

Hi 

 

@RojoAnt 

 

Did you have a chance to test this? Is there anything new?

 

Vincent-TP wrote

Hi  @RojoAnt 

 

Thanks for the detailed reply.

 

Will the Websocket packets be send to the cloud?

 

What's the model number of the EAPs you are using?

 

You mentioned that the issue occurs after you update the firmware.  If you don't mind, please choose a site to test: downgrade the firmware to the previous one, and check if the issue persists.

 

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#5
Options

Information

Helpful: 1

Views: 741

Replies: 4

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.