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

Problem with WIFI client when WPA2 password contains "=" character #1299

Closed
6 tasks done
tommyv opened this issue Feb 9, 2023 · 0 comments · Fixed by #1300
Closed
6 tasks done

Problem with WIFI client when WPA2 password contains "=" character #1299

tommyv opened this issue Feb 9, 2023 · 0 comments · Fixed by #1300

Comments

@tommyv
Copy link

tommyv commented Feb 9, 2023

Checklist

  • This is a bug report
  • I observed this bug on a clean install of the OS
  • I have followed the project prerequisites
  • I have searched this repository for existing issues
  • I checked the FAQ and official documentation before creating this issue
  • I have read and understand the issue reporting guidelines

Bug description

WIFI client doesn't save complete WPA2 password when it contains "=" (equal) character, instead it is cut.
EG. password xxxxx=yyyy becomes xxxxx, checked in wpa supplicant.

It does connect on the first try, but cannot auto reconnect later as the password is not saved correctly

Your environment

  1. Operating System: Rasbian GNU/Linux 11 (bullseye)
  2. Hardware and version: RPi 3B+
  3. RaspAP version: 2.8.7
  4. Clean install of a compatible operating system? Yes
  5. RaspAP Quick Install or Manual setup? Quick Install
  6. Using default configuration? Yes Both
  7. Other software or services running with RaspAP?

Steps to reproduce

Screenshots

Additional context

@tommyv tommyv changed the title Problem when WIFI contains "=" in password Problem when WPA2 password contains "=" character Feb 9, 2023
@tommyv tommyv changed the title Problem when WPA2 password contains "=" character Problem with WIFI client when WPA2 password contains "=" character Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants