VR600 and C7 confuse between wireless and wired clients

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

VR600 and C7 confuse between wireless and wired clients

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
VR600 and C7 confuse between wireless and wired clients
VR600 and C7 confuse between wireless and wired clients
2018-12-22 10:10:52

On my VR600 and C7 routers, some wireless and wired clients are listed in the wrong client list.

 

My setup includes the VR600 as the main router (DSL Modem Router Mode) providing DHCP services, while the C7 serves as an addition WiFi access point with no DHCP server of it own.

 

I am using the latest firmwares:

   VR600 v2: 0.2.0 0.9.1 v0074.0 Build 170504 Rel.68210n

   C7 v4.0: 1.0.7 Build 20180425 rel.62587(4555)

 

Does any of you have the same issue?

  1      
  1      
#1
Options
3 Reply
Re:VR600 and C7 confuse between wireless and wired clients
2018-12-24 10:12:23
Hi Uribench, We didn't get any feedback like this before. If you setup the C7 as an access point, please make sure the DHCP is disabled. If the DHCP is disabled, all the device should get an IP address from your modem directly. Thanks
Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#2
Options
Re:Re:VR600 and C7 confuse between wireless and wired clients
2018-12-28 16:08:08

Hi Kevin,

 

Indeed as you have said, only the VR600 is set with DHCP enabled. The C7 has its DHCP disabled. Nevertheless, the lists are confuesd.

 

As an example, here is what my VR600 shows now for the "Wired Clients" list. Actually, expect for the devices 1 and 3 that are truly wired, the remaining items in this list are actually wireless.

 

Wired Clients

ID Name IP Address MAC Address
1   192.168.0.21 B8-27-EB-7A-8F-57
2   192.168.0.35 60-36-DD-8A-6B-64
3   192.168.0.29 10-E7-C6-AA-BF-00
4   192.168.0.17 78-0F-77-B9-06-4B
5   192.168.0.39 7C-49-EB-4B-B6-79

 

At the same time, C7 is showing 2 wired clients and both are truely wired. It also shows 0 wireless clients, while for sure there are few connected and active as can be seen using the Advanced IP Scanner.

  0  
  0  
#3
Options
Re:Re:VR600 and C7 confuse between wireless and wired clients
2020-03-27 10:04:15 - last edited 2020-03-27 13:09:45

@uribench I know it's been two years, but that is the normal behaviour because TP Link routers' client list is actually a network list, not an actual client list of the router or AP.

 

They detect network traffic (ARP packets more specifically) and populate the lists, no matter where devices are connected or how.

 

So, from the router point of view, any device connected to the AP is a wired one because it sees traffic coming from an Ethernet port and hence it says "cool, this is a wired device".

 

Plus, there is a bug when showing devices in access points that turns out to be years without being fixed... I even saw a post dating 2016 :S That explains why you don't see all devices in C7.

 

So, to summarize, it's not that they confuse them and they're actually two different issues:

- Main router will show as wired all devices that it discovers by analyzing LAN traffic. That's not really a bug, from its point of view it doesn't know if there's an access point somewhere or not, it just knows packets from a device are coming through the LAN port.

- Access points have a firmware bug, not solved in years. Sometimes they won't display the correct client list. In fact, they may not even list wireless devices that the very same AP has to authenticate. Turns out it's more prone to happen in AP mode. But so far still not solved.

 

  3  
  3  
#4
Options