Omada SDN Association Failures
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
How can I get rid of this failures ?
How can I identify which clients do that and why ?
Regards
Jörg
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Koboldo wrote
How can I get rid of this failures ?
By using the correct WPA2 encryption key. See the Omada SDN Controller User's Guide when in doubt about the meaning of those errors:
How can I identify which clients do that and why ?
AFAIK one can't list the clients causing those failures, but maybe I overlooked something in the statistics setup. OTOH, an user should quickly notice that the encryption key he uses is wrong. And why? Because of a typo? Bad long-term memory? CAPS-LOCK KEY was stuck? How should the controller find out about the why?
- Copy Link
- Report Inappropriate Content
Ouch
- Copy Link
- Report Inappropriate Content
@chamadz I have the same problem, device randomly get an WPA Authentication times out on all my access point. EAP245 and EAP225-Outdoor.
but the device connect to the network again.
- Copy Link
- Report Inappropriate Content
@shberge, what's the RSSI of this device when it connects?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Same here 🙄
- Copy Link
- Report Inappropriate Content
@shberge, -68dBm is not »very good«, but »okay«. If the RSSI goes even below -69dBm, packet loss can happen.
A device with an RSSI in this »grey zone« can cause intermittent association errors and nevertheless associate with the SSID successfully in the next few seconds.
- Copy Link
- Report Inappropriate Content
This is very annoying that it logs the issue, tells you to check it, yet it does not capture it in the LOGS pages
- Copy Link
- Report Inappropriate Content
This is a huge failing in the UI.
WPA failure could just be a known device is out of range.
OR
It is unwelcome attempts.
Anything from mobile phones polling for an open connection, Or it could be an infiltration attempt / security risk.
I see hundreds of these and we are in a very remote and rural location, with outdoor EAPs. If someone is attempting to join the network I want as much detail as possible. Why does the Omada interface not gather information on which devices are attempting to connect??
I get a breakdown by AP, but that's useless.
Where is the detail of the handshake?
- Copy Link
- Report Inappropriate Content
^^^^^^^^^^^^^^^^^^^^^^^^^
I'm bumping this right here. Exactly what I was trying to ask/say.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 18999
Replies: 29
Voters 2
