This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I'm trying to troubleshoot AP disconnection issues.
I've logged in via ssh but find that I'm hobbled by the lack of root access (can't ping, for instance).
As an experienced linux and network admin, how do I troubleshoot device issues?
It does not support root access. You can only have the guest access role.Could you please specify the diconnect issue you mentioned? Do you use a controller to manage it?Is it disconnecting from the controller?Please confirm that the connection between the controller and the EAP is working properly, and then try to readopt it and troubleshoot based on the error by referring to this article.
What should I do when the Omada Controller (V4) fails to adopt the devices?
@Hank21 I've submitted a bug report TKID240727652 on the device crashes. At this point I suspect the controller is causing the crashes because the device doesn't crash when configured only via its own web interface. Also see https://community.tp-link.com/en/business/forum/topic/675602
It's a shame the device is so locked down. Remote syslog seems to be useless: with "More client detail log" disabled it doesn't log anything. If I turn that option on it logs every packet, which is way too much detail. There doesn't seem to be anything in between,.
Helpful: 0
Views: 604
Replies: 2
No one has voted for it yet.
We use cookies and browser activity to improve your experience, personalize content and ads, and analyze how our sites are used. For more details, please read our Privacy Policy.
