Skip to content
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

Cannot connect to certain wifi networks #107

Open
alebustelo opened this issue Aug 13, 2024 · 9 comments
Open

Cannot connect to certain wifi networks #107

alebustelo opened this issue Aug 13, 2024 · 9 comments

Comments

@alebustelo
Copy link

Knulli build version

40-dev-d3b520f949 2024/07/21

Your architecture

RG35XX H

Issue description

If I connect to a wifi signal where the password is all numbers, it connects and picks up an IP quickly, but when I try to connect to a wifi signal with letters, numbers, and special characters, it won't get an IP address. Both wifi connections are WEP2.

Detailed reproduction steps

I start Knulli and go to the network settings in the main menu. Then, I press A on the wifi ssid option and select the wifi network I want and then I go to wifi key and type in the password. The hostname of the device is set to RG35XXH and enable wifi and show network status are both set to on. The IP address and internet status both say NOT CONNECTED.

Details of any attempts to fix this yourself

I have tried power cycling the device and turning the wifi off and on. Changing to another wifi signal works. The only difference between both networks is the working one uses only numbers for its password and the non-working one uses a more complex password.

Details of any modifications you have made to Knulli.

No modifications.

Logs and data

N/A

@alebustelo
Copy link
Author

I forgot to mention, I was having this issue on the last version of the firmware, too (20240530) and I upgraded hoping it would fix the issue. It did not.

@00svd00
Copy link

00svd00 commented Aug 18, 2024

As I know - WEP2 was never used in end user devices. Do you mean WPA2-PSK?
You should never use WEP and WPA/WPA2-PSK with TKIP encryption, they are too unsafe and can be cracked just immediately by anyone who wants.

@alebustelo
Copy link
Author

Sorry, I meant that the network's security is WPA2. I don't know why I typed WEP2.

@anonymouz-trash
Copy link

I also can't connect to my WiFi. I have combined wireless network with 2.4 and 5 GHz. The SSID is just one word with Letters only and the encryption is WPA2. The password looks like Sp3c!alCh@ract3r$.

I also tried to edit /userdata/system/batocera.conf and escape all special characters (\) like mentioned in the comments of same file but no success. When I try to set it in ES it may happen that the password gets cut off. My device is a H700 RG40XX.

@reinaldo-freire
Copy link

We still don't have a solution for the error? That's unbelievable.

@00svd00
Copy link

00svd00 commented Oct 7, 2024

Here are my wifi settings, work perfectly for me:
band=2ghz-n
frequency=2412
width=20mhz
authentication-types=wpa2-psk
disable-pmkid=yes
encryption=ccmp,gcmp
ft=no
ft-over-ds=no
group-key-update=1h
management-protection=allowed
wps=disable

@alebustelo
Copy link
Author

Does your WiFi password also use special characters?

@Mikhailzrick
Copy link
Collaborator

Mikhailzrick commented Nov 7, 2024

If your router has a setting Management Frame Protection, Protected Management Frames, Management Protection, etc. try disabling it or set it to allowed/optional.

the core issue with the wpa3 compatibility is the pmf afaik. So try the above as well as ensuring it’s set to wpa2.

@00svd00
Copy link

00svd00 commented Nov 7, 2024

pmf afaik

Wifi roaming (802.11 k/v/r) also can produce connection problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants