@Cepheus0815 at least we have an answer saying that if you want to lose the ability to see clients' IPs with Omada, buy any ES series switches. I have replaced the ES switch with a 10buck switch, and it is working fine with the client's IPs seen by the controller. 

  @Clive_A 

Clive_A wrote

Hi @Psav

Psav wrote

  @Clive_A 

 

to be honest a simple statement on the product sheet that says that the "Centralised Cloud Management via the web or Omada" only applies to the "device itself" and not the attached "client list" would help to clarify.

 

as a buyer that would help-- because as a buyer who looked at the spec sheets it wasn't clear when I purchased.  And I will have to substitute these products with others at my cost.

 

Speaks less to the hardware quality and features (tp-link will build whatever they like and think will sell) and speaks more to the quality customer experience.

 

thanks again for answering -- gives a definite way forward now that a firmware fix isn't an option 

I updated the statement again. When you meet these prerequisites, you will have the client IP displayed.

What statement are you referring to, this one?

In the future, if you are using the Omada router, ES series switch, and the connected to ES switch client's DHCP IP is assigned by the Omada router, the client IP will be displayed. Period. No additional features. This is the only improvement down the road regarding this.

As for the ES switch, and this specific request is NOT gonna be considered in the future firmware update.

I have the ES205G v1.0 connected to ER706W v1.20, I see only the IP of the switch, any other wired client is not displaying the IP, although the DHCP pool allocates the IP to them, only wireless clients are displaying the IPs.

  @Clive_A  thank you for your answer. I am sorry, but I think I am missing something here and it could be because I am not a native speaker. Therefore, to clarify this whole "thread" for myself and maybe someone else, I will try to address this point by point by using my setup as an example.

ER706W v1.20 - gateway

EAP650-Desktop(EU) v1.0 - wireless AP

EAP650-Desktop(EU) v1.0 - wired AP

ES205G v1.0 - directly connected to the ER706W v1.20

Omada software controller 5.15.20.12

Issue: Connecting an ES205G switch is resulting in losing the information about the client IPs in the controller, all of them, even though they are not connected through the switch, and only wireless clients are showing their IPs.

Solution: Replacing the switch by a non-Omada switch solves this. Alternatively, replacing the ESxxx series with a high series should solve it. 

------

However, from your last answer I have understood that the above mentioned "Issue" will be solved in the future - considering the setup outlined above, i.e. Omada gateway, etc... 

Frankly speaking, if the above is correct, I believe I have misunderstood somehow the whole thread since I was expecting we are talking here about a fully equipped Omada environment (gateway, controller, APs) that is facing this issue with the ESxxx series switch, not a standalone switch.

Please, correct me if I am wrong.

thx, tomas

  @tsalat 

My implementation is as you say full stack-

Gateway - full feature switches with the smaller 5 ports on the edge of the network.  and an OC-200 hardware controller.

On the small switches the Device IP is registered and the switch is controlable but client IPs for devices plugged into the switch do not show on the app Or website (Mac address, client name etc do show up)

  @Clive_A 

When can we expect the firmware update to resolve this issue?

I have 2 ES205 switches that I would love not to have to return.

  @Cepheus0815 

lets hope the fix will come soon. The latest Omada software controller is not fixing this issue so I hope it will be fixed in the upcoming release.