I have managed to compile wpa_supplicant 2.9 from source, and indeed it has solved the problem.
It is not hard to compile, anyone can do that. Here are the steps needed:
1. Download the source from the link from Kaczorek's post:
w1.fi/releases/wpa_supplicant-2.9.tar.gz
2. Extract the source:
$ tar xvzf Downloads/wpa_supplicant-2.9.tar.gz
That creates a directory wpa_supplicant-2.9
3. Go to the build directory wpa_supplicant-2.9/wpa_supplicant
$ cd wpa_supplicant-2.9/wpa_supplicant
4. Create a .config file.
I've used the one I've found at the end of this thread:
raspberrypi.stackexchange.com/questions/...o-raspi-access-point
For your convenience I attach it to the post.
You have to rename it to .config, but the forum does not allow me to upload it by that name:
Of course you can change the values in it as you wish, or make one for yourself based on the provided defconfig file.
5. You will need the development package for dbus and netlink socket, so install them:
$ sudo apt install libdbus-1-dev libnl-genl-3-dev
6. Compile the source
After successful compilation you will get 3 binaries: wpa_supplicant, wpa_cli and wpa_passphrase
7. Install th enew binaries
The original .deb package install wpa_supplican and wpa_cli in /sbin while wpa_passphrase is in /usr/bin. You can simple overwrite them is you wish, but I rather like to keep them, and install the new ones in /usr/local:
$ sudo cp -a wpa_supplicant /usr/local/sbin/
$ sudo cp -a wpa_cli /usr/local/sbin/
$ sudo cp -a wpa_passphrase /usr/local/bin/
Since the /usr/local directories is earlier in $PATH than the system directories, these ones will shadow the originals when called from command line.
8. Update systemd
For the wpa_supplicant service unfortunately the path is hardcoded in the systemd service file, so if you just do what I did, you have to update it:
$ sudoedit /lib/systemd/system/wpa_supplicant.service
On the ExecStart line change
ExecStart=/sbin/wpa_supplicant
to
ExecStart=/usr/local/sbin/wpa_supplicant
Refresh systemd:
$ systemctl daemon-reload
$ systemctl restart wpa_supplicant
It is better to do that from the console or through ethernet connection, since the WiFi will disconnect and reconnect, if it was successful.
You can alternatively simple reboot your RPI, but be prepared that if something is wrong with the new wpa_supplicant or you made a mistake in the systemd config, WiFi will not work.
If something gone wrong, you can check the wpa_supplicant service status with:
$ systemctl status wpa_supplicant
This will tell you if for example you misspelled the path.
9. Connect from your Samsung phone!
Topic Author
