Hi @WM1 

Thanks for posting in our business forum.

Probably reboot the whole system. Don't see a better way to find out what's wrong.

I cannot get any information from your description or the picture. It is too general.

What are the two devices you circled? Where do they connect to?

Oh, you are using the pre-release. You probably consult this matter with the controller specialist. It does not look like a problem with the router. No similar cases were reported last quarter.

Try to avoid posting cases like this if you are using the pre-release firmware. Report this matter to the pre-release thread and they will take a further look. I may say this could be a controller issue.

Hi @WM1 

Thanks for posting in our business forum.

WM1 wrote

Hi @, Clive_A, thanks for your response.

 

You propose to reboot the whole system. Obviously that is what I already tried. Since that didn't solve the issue, and like I mentioned I'm pretty sure that in earlier versions of the firmware of the ER605 and/or the OC200 the wired clients on the ER605 were listed, I thought let's report it.

 

The picture in initial posting shows that the whole system is capable of properly managing the wired clients connected to the LAN-ports of the router (meaning DHCP Reservation, IP-MAC Binding and VLAN) and that these clients are shown in the overview of Known Clients (which may or may not be connected at that moments). The wired cleinst are only not shown in the overview of connected clients. Below is the overview I refer to (it doesn't seem to have a name).

 

 

The two devices I circled in the other screenshot are two of the clients shown in Known Clients but not in the overview of connected clients. Like mentioned the're connected to ports 'WLAN/LAN2', 'LAN1' and 'LAN2' of the router.

 

Yes, I'm using a pre-release of the OC200, but I propose that you consult the controller specialist on my behalf (instead of me having to find out which specialist to reach out to, don't you think?).

 

Lastly, I don't agree with you to try avoiding posting cases like this when I'm using the pre-release firmware. Like mentioned I use many different TP-Link components in my system. Since I'm not aware what is actually causing this behavior (in particular because quite recenty several firmwares for these components were released), I post it in the for me most likely part of the TP-Link Omada Business Community. I only report this finding to the Community to make specialists like you aware and have it structurally solved for all of your customers.

1. ER605 did not have a new firmware update recently. 2.2.4 is the official release and I don't see any other posts like yours reporting a similar issue. I don't know your switch model but this time the picture shows they are connected to a switch.

2. I am not a controller specialist and if there is a problem, and you should report this to the controller page where it releases the pre-release firmware and he/she will collectively report to the dev.

You have replies under that post and I think you should know how things work and as a member who has participated in the beta since V5.9. Hank will take care of it as it is under the controller page.

There is a reason why we have two specialists for different products. That's how things work and we contact different devs for issues and reports.

3. You are aware of this that a pre-release firmware has a dedicated post to collect feedback on the experience with the firmware. The dev usually may check daily or weekly to see if there is a serious problem that needs to be addressed.

4. I would assume that our dev would refer this case to the controller as we have not released new firmware. If you believe this is a ROUTER issue, reply to this post and I am happy to give it a try to the router dev and take a look. But I don't guarantee that this will be further escalated by our router/switch devs.

5. And let's break it down with your new information. I am not following because you mosaic everything and information is scattered. If you post stuff in the router, you should at least see my message before I have a note like this:

Please mosaic your sensitive information. Here is a list of information considered sensitive:

1. Public IP address on your WAN if your WAN is.

2. Real MAC address of your device.

3. Your personal information including address, domain name, and credentials.

For troubleshooting purposes, when a WAN IP is needed, please leave some values visible for identification.

I cannot cross-reference your MAC address and know if there is a problem with the router or not. At this moment, no indication shows that the problem results from the switch/router.

The new picture shows a switch. So, what are the devices? Are they connected? Are they connected to the switch as the picture shows which accurately reflects the fact?

Your title is about the ports on the router which is different from what you described here.