Raspberry Pi WLAN setup

Post by azinman2 » Sat, Nov 24, 2018, 6:07 PM UTC

otachack wrote: post #38

azinman2 wrote: post #35

Earlier quoted context omitted.

But you can’t do that from a raspbian image, and if you want me to mod my file system post install that only works assuming I can mount it (eg I have another Linux box with keyboard). I’ve had this problem multiple times and find this approach really nice (and wish it shipped with raspbian!)

But where was the SD card flashed? I think the idea is to enable ssh right after flashing the image.

Post by kingosticks » Sat, Nov 24, 2018, 6:29 PM UTC

ryanianian wrote: post #26

fpgaminer wrote: post #24

I'm building a gift for someone else that uses a RasPi internally, and thus needed a user friendly way for them to configure its WiFi connection. It's been ... quite the adventure (mostly because I'm dumb). My first idea was to put an OLED and a rotary encoder on the box. That way they can do a special dance on the button to enter setup mode, scroll through a list of wifi networks, and then tediously scroll through l…

Raspbian defaults to being discoverable by bonjour so you can just `ssh pi@raspberrypi.local` and then modify the wifi config file (`/etc/network/interfaces`). You can script this bootstrap process pretty easily using Ansible etc. Downside is you do have to have a machine on the same ethernet network as the rpi for a short time. So fewer "cool project" points but ends up being quite simple.

Post by Nexxxeh » Sat, Nov 24, 2018, 6:35 PM UTC

Uehreka wrote: post #9

noja wrote: post #6

or create /boot/wpa_supplicant.conf and touch /boot/ssh and it will do the right thing on boot.

Can you seriously put wpa_supplicant.conf in /boot and it’ll work? I have honestly never heard this in 2 years of doing Raspberry Pi, after looking at tons of documentation and web sites. This wouldn’t surprise me, but I feel like it should be much better documented, given that it’s pretty much the first and biggest hurdle to getting things to work on a new image.

Post by vardump » Sat, Nov 24, 2018, 6:45 PM UTC

tzs wrote: post #41

noja wrote: post #6

or create /boot/wpa_supplicant.conf and touch /boot/ssh and it will do the right thing on boot.

I'd like to see one addition to that. On boot, it should also write a file, /boot/MAC-address, if it does not exist. This should be a text file containing the Pi's MAC address. With that, those whose networks require whitelisting by MAC address who are trying to set up a headless Pi could boot it once to get it to write its MAC address to the SD card, whitelist that MAC address and assign it a static IP address, crea…

Post by callumjones » Sat, Nov 24, 2018, 7:08 PM UTC

lisper wrote: post #47

callumjones wrote: post #45

Earlier quoted context omitted.

But this is just the process of connecting it to a wireless network, which would be the hacker's network? The risk seems pretty contrived? You could make the same argument for other assisted headless installations: speakers, smart plugs, etc.

> You could make the same argument for other assisted headless installations: speakers, smart plugs, etc. That's true, but in those devices can be isolated from the internet by a firewall. Berrylan can't be, or it loses its utility. In order to talk to the app, Berrylan has to send packets to and receive packets from the internet. Also, even after the setup, most RaspPi applications entail having the computer continu…