Wireless clients still showing up as wired/LAN
Have LAN consisting of two TL-SG2008P (v3.0) (firmware 3.0.5) and four EAP615-Wall(US) v1.0 (firmware 1.1.6).
Problem: Some devices are showing up as "LAN" when they are wireless (and have no physical connection).
This seems similar to https://community.tp-link.com/en/business/forum/topic/246448
They appear to be reported as switch-port-N rather than being wireless clients of the AP that is connected to that port. Eg: the first four below, each of which are smart-plugs (tp-link Kasa and Tapo as it happens)
and Map showing the same (wrong) topology
Please advise. Thanks!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Virgo that's terrible! Half the _point_ of central management is knowing where/how the devices are connected! Some show properly, some do not. How can this be "normal"?
- Copy Link
- Report Inappropriate Content
Hello @SimonR ,
Please confirm whether the network topology like SG2008P --> EAP615-Wall (1) --> EAP615-Wall (2) )))((( Wireless clients.
Could you please also confirm whether the clients appearing as wired connections are connected to a second access point (AP2) that is connected to the root access point (AP)?
If that is the case, these clients will be displayed as wired clients on the switch. Please note that the Omada EAP products are unable to report the connected wired/LAN clients to the Omada Controller because the data from their LAN does not pass through the CPU.
The switch is aware of the existence of AP2 and recognizes AP2 as directly connected to the switch. This is also because Wall APs cannot report client data on LAN ports. As a result, AP2 and the clients connected to it will only be reported as LAN/wired connections by the switch, giving the impression that they are directly connected to the switch.
- Copy Link
- Report Inappropriate Content
@Hank21 No, there's no "nested" APs. There is a central switch, and another switch in the bungalow, which is connected + POE to the EAP. It issue is/was that wireless clients that are connected to the AP are showing up in the map as wired clients, per the second screenshot in the OP.
(I do understand that wired clients using the 3 ports on my AP will show up as being attached to the upstream switch, as the AP CPU doesn't handle those. Luckily, at least the AP can associate them with VLANs, so they're not useless)
That being said, it looks like they've come right now. Is it normal for Omada to have wrong topology for a while? Maybe until it sees enough traffic?
- Copy Link
- Report Inappropriate Content
I have the same problem. Random client can shows up in Wired connection but within the SSID/Network
It shows how the client truly connect to your Omada system.
It will go away the next time it asks for the DHCP lease.
- Copy Link
- Report Inappropriate Content
Hi All,
The time difference between the switch device and the EAP device reporting the client on the Controller is the cause of this phenomenon.
As soon as the client connects, it may appear in the wired client list as the Switch reported. After a while, the EAP device will report the client to the Controller, and it will then be displayed in the wireless client list as expected.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1166
Replies: 6