-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wetek Play 2: Invalid-key while connecting to wifi #8760
Comments
I can see the following in the logs. The WPA3 error also in the 8731 report. iwd[371]: Could not register frame watch type 00b0: -22 Proposition “does iwd fail when the capabilities of the card don’t match the access point” eg FT, WPA3, …. given you have a fail with bcm to openwrt. But success bcm to android HS. I’m pretty sure the reported “invalid key” is the default error when the iwd gets an error during authentication. We saw this last year when doing detailed testing that the driver or wireless stack errors propagate. given that you have a working scenario a) bcm to android - what capabilities doesn’t that network offer that are offered by openwrt. Remove those from openwrt, retest, cross fingers….. I don’t think this is the magic fix for all, it seems like different drivers have different results, and given your experience - the bcm driver is “more fragile/picky/???” |
|
I'm curious if you are able to connect to your OpenWrt router when configured for an unencrypted connection. In issue #8731, I seem to have trouble with unencrypted signals too which seems to indicate that the problem lies elsewhere in |
Is this still occurring with the latest LE13 nightlies?
|
I hope, I manage to give it a try next weekend. |
Describe the bug
This is a continuation of issue #7166 but for LE12.
How to reproduce
Steps to reproduce the behavior:
Information
Log file
kodi.log:
https://paste.libreelec.tv/in-elephant.log
dmesg output:
https://paste.libreelec.tv/welcomed-sloth.log
Context
I have LE12 on rock64 working flawless on the same OpenWrt router. The wireless signal strength reported by the wetek is rather low (~50), but also with the wifi router next to the wetek (~78) the same error occurs.
What is weird: with an Android Wifi-Hotspot with similar signal strength (~76), wifi on the wetek play 2 works flawless.
The text was updated successfully, but these errors were encountered: