02-12-2023, 05:21 PM
(This post was last modified: 02-12-2023, 05:22 PM by Tim Curtis.
Edit Reason: eta
)
(02-12-2023, 04:53 PM)adam_zzz Wrote:(02-12-2023, 03:04 PM)Tim Curtis Wrote: Some info in this Raspberry Pi Linux issue
https://github.com/raspberrypi/linux/issues/4718
One of the posters mentions adding some params to spa_supplicantl.conf
https://github.com/raspberrypi/linux/iss...1214411359
ETA: Ran a quick test with a 3A+ and no issues with WiFi connecting to my Router running WPA2-PSK.
Thanks for checking and for the suggestions!
I have realized after a few hours of trying to put different things in wpa_supplicant.conf that probably they are not taken into effect... I have changed the SSID with a test string in the file but in the UI still the old one shows, the same in the log after rebooting when calling "moodeutl -l".
Is there anything I need to run in order for the wpa_supplicant.conf to be used?
What I did so far:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
Ctrl +X , and Y
sudo reboot
Edit: When running "sudo wpa_cli" I get this message:
openat(AT_FDCWD, "/var/run/wpa_supplicant", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
pselect6(1, [], [], [], {tv_sec=0, tv_nsec=999998000}, NULL) = 0 (Timeout)
The Network Config page stores its entries in the cfg_network SQL table. This table is used to write wpa_supplicant.conf when SAVE is clicked.
Afterwords wpa_supplicant.conf can be manually edited with entries that are not also maintained in the SQL table, just don't subsequently SAVE from the Network Config page or it will overwrite the file and the manual changes will be lost.