Wpa Supplicant Configuration File Template For A Document
The removal of the ssh and wpasupplicant.conf files on boot is normal. Once the RPi boots, everything should be persistent and the network and ssh available on subsequent boots. If you want to keep copies 'just in case', you can create a.zip archive of those files in /boot and it will not be removed.As to your wireless network not being recognized, it sounds like you're using raspbian stretch. Try adding the follwing lines to the top of your wpasupplicant.conf: country=USctrlinterface=DIR=/var/run/wpasupplicant GROUP=netdevupdateconfig=1Change US to your 2 character country code. From what I've read, the ctrlinterface line is the real trick, but the others are recommended. I'm using PiAware image 3.5.0 on a Pi Zero.The /boot/ssh file behavior is indeed as Milliways said. To get your credentials to survive a reboot, use piaware-config to set its wireless-ssid and wireless-password entries, or use nano to edit /boot/piaware-config.txt.
On my system, the file /etc/wpasupplicant/wpa-roam.conf (not wpasupplicant.conf) is regenerated at boot time with the network settings in piaware-config.txt.Check the wpa-roam.conf file. If it has the correct credentials, for some reason it's probably not finding the SSID.
Wpa Supplicant Configuration File Template For A Document Download
It only looks on the 2.4G frequencies, not on 5G. If the credentials are wrong, you can change them in wpa-roam.conf and test your changes using 'ifdown -v wlan0' to make sure wlan0 is down, and then 'ifup -v wlan0' to try creating the connection. The -v will give you verbose output, which may help you troubleshoot the problem. Once you get it working, copy the working SSID and psk settings to the piaware-config.txt file so you don't lose them when wpa-roam.conf is overwritten at the next reboot.Hope this helps.