Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200

Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200

Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
2024-06-07 21:06:24 - last edited 6 hours ago
Model: ER605 (TL-R605)  
Hardware Version: V2
Firmware Version: 2.2.4

My ER605 v2.0 router (firmware 2.2.4) is connected to a modem on port 'WAN'. A SG2210P v5.20 switch (firmware 5.20.1) is connected to port 'WLAN/LAN1'.

 

On ports 'WLAN/LAN2', 'LAN1' and 'LAN2' wired clients are connected directly. These wired clients are not visible in the overview of clients in OC200 (Omada Hardware Controller_V5.14 Pre-release).

 

All wired clients connected to the switch and wireless clients connected to the EAP615-Wall(EU) v1.0, EAP225-Outdoor(EU) v1.0 and EAP230-Wall(EU) v1.0 access points are all visible in the overview of clients in OC200.

 

The wired clients show up in the overview of Known Clients, however with 0 KB download and 0 KB upload:

 

 

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.

 

Does anyone have an idea how this can be solved?

  0      
  0      
#1
Options
7 Reply
Re:Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
2024-06-11 02:05:16 - last edited 2024-06-11 02:07:10

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.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  1  
  1  
#2
Options
Re:Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
2024-06-11 19:18:46

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.

  0  
  0  
#3
Options
Re:Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
2024-06-12 00:56:40

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.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting Manual ★ ☚ (Disclaimer: Short links are used above solely for guidance to TP-Link subdomains and are safe and tracker-free. Exercise caution with short links from non-official members on forums. We are not liable for external content or damage from non-official members' link use.)
  0  
  0  
#4
Options
Re:Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
2024-06-12 21:06:23

Hi @Clive_A, first of all, take it easy.

 

Secondly, I started my initial posting with mentioning all components in my system:

 

  • ER605 v2.0 router
  • SG2210P v5.20 switch
  • OC200 v1.0 controller
  • EAP615-Wall(EU) v1.0 access points
  • EAP225-Outdoor(EU) v1.0 access points
  • EAP230-Wall(EU) v1.0 access points

 

You are indeed correct that the second picture shows that the clients are connected to a switch (model mentioned above). That is the whole point: all wired clients connected to the switch and wireless clients connected to the access points (which are connected to the switch) are all visible in the overview of clients, while the wired clients connected to the router (except for the switch) are not.

 

Please also see the Topology:

 

 

Lastly, I would say that the simple explanation should suffice for a specialist to understand, even though I may have posted it in the incorrect part of the TP-Link Omada Business Community.

 

I don't like to be sent from pillar to post, but since you seem to be convinced that it is a controller pre-release firmware issue and not a router official firmware issue, I will take it up with your controller specialist colleague wink.

  0  
  0  
#5
Options
Re:Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
2024-06-15 11:04:09 - last edited 6 hours ago

Hi @Clive_A, interestingly enough today an update for my ER605 v2.0 router from version 2.2.4 to  2.2.5 seems to have solved the issue.

 

Spot the difference with the previous screenshot of the Topology:

 

 

So it looks like it was the router all along.

  0  
  0  
#6
Options
Re:Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
7 hours ago - last edited 6 hours ago

Hi @Clive_A, an update of my ER605 v2.0 router from version 2.2.5 to 2.2.6 (ER605(UN) V2 2.2.6 20240621 Pre-Release Firmware (Released on July 3rd, 2024)) and my OC200 v1.0 controller to version 1.31.3 (OC200(UN)_V1_1.31.3 Build 20240620) the problem rises again.

 

A screenshot of the newly designed Topology shows that the Client Group on the ER605 v2.0 router is missing again:

 

 

Also multiple reboots of the router and also of the whole system (router, controller and PoE switches) doesn't solve the issue.

 

Can I ask you to look into it again, if needed with your controller specialist colleague? Thanks in advance.

  0  
  0  
#7
Options
Re:Wired clients connected to WLAN/LAN2, LAN1 and LAN2 not visible in OC200
6 hours ago - last edited 6 hours ago

Hi @Clive_A, interestingly enough several minutes after posting the previous post the issue seems to have vanished.

 

Spot the difference with the previous screenshot of the Topology:

 

  0  
  0  
#8
Options