Wired Clients not showing on Omada software controller
Omada software (version 5.15.20.18) is running in a docker container on a NAS. The ER7142-M2 is running DHCP server and administers IP addresses to both wired and wireless clients with no problem.
Wireless clients: All of my 30 or so wireless clients are visible on Omada software controller. They are connected via EAP225s to unmanegd TPlink swiches and then to the ER7142-M2 .
Wired clients: None of the approx 20 wired clients appear on the Omada controller client list. Most of these are connected via 5 and 8 port TPLink unmanaged switches. The NAS is directly connected to the ER7142-M2 and it doesn't appear either. New wired clients may show up on the omada client list briefly and then disappear for good.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @sparkles
To understand the issue better, please let us know the following info:
What's the model number of the TP-Link unmanaged switches?
What kind of wired clients are plugged in the network?
Did the wired clients display correctly on the controller before? Or they never showed up?
Did you try different web browsers? Please also clear the cache of the browsers.
- Copy Link
- Report Inappropriate Content
Hi Vincent,
In answer to your questions:
1) the unmanaged switches are TL-SG1008D and TL-SG1005D
2) wired clients include windows PCs, smart TVs and set top boxes and printers
3) The wired clients generally never show up. There has been exception - in the last week I connected a newly configured wired raspberry PI model B via a TL-SG1005D and it showed up for a while. I just rebooted it and reappeared for 15 mins (as reported by Omada uptime value) and then disappeared. After less than a minute it reappeared but Omada said uptime was 5 minutes. Afer a few more minutes it dissappeared. I also rebooted a wired synology device and it did not appear at all. Right now there are no wired devices showing.
4) I was using Brave browser. I have now tried Microsoft Edge browser with cache cleared and it makes no difference.
Thanks
Peter
- Copy Link
- Report Inappropriate Content
Is your NAS firewall (assuming it has one) blocking ICMP / ARP ?
Since the controller is running on the nas, in a container, its subject to whatever filtering the NAS firewall is doing to incoming and outgoing traffic on its own port
Tyr completely disabling the NAS firewall first, see what happens (controller IP lists can take a while to update) and work from there
- Copy Link
- Report Inappropriate Content
Hi @GRL . I stopped the NAS firewall. When running command line arp in the docker container it shows both wired and wireless clients. I can also ping wired devices from within the container with no problem. The new wired raspberry pi will appear and dissappear intemittedly but no other wired clients show (even after I reboot them).
- Copy Link
- Report Inappropriate Content
Thank you so much for taking the time to post the issue on TP-Link community!
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 TKID250422626, 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
Information
Helpful: 0
Views: 93
Replies: 5
Voters 0
No one has voted for it yet.