Earlier quoted context omitted.
Not in /boot, but the boot partition of the device named "boot".
That is mounted at /boot....
Just wanted to specify. If you put the wpa_supplicant in /boot under the root partition, it won't work :^)
Raspberry Pi WLAN setup
81–86 of 86 posts
Re: Raspberry Pi WLAN setup
#82Re: Raspberry Pi WLAN setup
#83Earlier quoted context omitted.
Ssh can be enabled and wifi configured in /boot.
Yes. Touch (create) an empty file called "ssh" in /boot, and wifi details in wpa_supplicant.conf as mentioned elsewhere in the thread. Very handy!
Yes, I know. I was just telling GP that they are mistaken. :)
Re: Raspberry Pi WLAN setup
#84Earlier quoted context omitted.
There's an explanation of why bluetooth is used here: https://www.raspberrypi.org/forums/viewtopic.php?t=223380
That thread says: "BerryLan works great on the Model 3 but not the ZeroW" Anyone know if that is still the case?
Raspberry Zero W is now supported
Re: Raspberry Pi WLAN setup
#85So GUI and displaying the IP at the end is nice. But. I do wonder: If you already have to write a special image, why not just write the network config directly to wpa_supplicant.conf?
As evan__10 said, if you don't know the details ahead of time. I own a company and we are currently developing a hardware tool for attendance tracking at child care centres. We use the Pi and our plans for shipping these things was to ask our customer what their SSID and password were ahead of time and hard code them in. This tool could solve our problem. Additionally, if the user changes their SSID or password at an…
Did you consider adding a password-changing webapp that connects via a smartphone's headphone jack? Or maybe even just with a _cheap_ piezo for bidirectional beeping to a smartphone? Consider the equalizer commonly used in the output path of a smartphone, but there should be existing work you might be able to build on.
Re: Raspberry Pi WLAN setup
#86Earlier quoted context omitted.
I know you're talking about Someone Else's Network (tm), but isn't whitelisting MAC kind of pointless? MAC can almost always be freely set to any value.
MAC whitelisting as a security measure against deliberate, reasonably knowledgeable attackers is indeed of questionable value. But that's not the only reason you might use MAC whitelisting. Another use is to prevent accidents. Suppose you have multiple networks. For example, at work we have separate networks for machines that handle different kinds of sensitive data, with each network having the appropriate incoming…
If you can mac-whitelist, you might also be able to use 802.1X in some form, and be it just locking to the TPM chip or some other crypto token your device has already.