Business Community > All Threads > Server log: Known wireless client handled as wired client
< All Threads

Server log: Known wireless client handled as wired client

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

Server log: Known wireless client handled as wired client

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Server log: Known wireless client handled as wired client
Server log: Known wireless client handled as wired client
2023-02-27 02:05:37
Tags: #log
Model: OC200  
Hardware Version: V1
Firmware Version: 5.7.6

What is the reason why the wireless client was handled as a wired client?

 

[client-inform-work-group-1] [] c.t.s.o.c.d.a.s(210): Known wireless client CLIENT-MACADDRESS is informed by switch: SW-MACADDRESS, omadac: HASH, site: HASH, handle as wired client now.

 

Saw this line in the server.log file.

  0      
 
  0      
 
#1
Options
2 Reply
Re:Server log: Known wireless client handled as wired client
2023-03-01 12:45:57

  @2Dr 

 

This is a problem with the equipment reporting mechanism.
For example, if it is Omada switch -----EAP ----- Unmanaged switch -----AP, then the wireless client behind the AP will appear as a wired client connected to the switch.
 

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:Server log: Known wireless client handled as wired client
2023-03-09 00:12:54

  @Virgo The EAPs are not connected to an unmanaged switch.

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 450

Replies: 2

Tags

log
Related Articles
Wired client at eap235
2057 0
Known Client List
326 0
Wirless Client Show up as Wired -
463 0
Logs - Client Connection changed (Wired)
391 0
Omada Controller Log/Event/Client is not working (no entry at all)
3114 0
OC200 More Client Detail Log
1701 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.