I've recently created a video tutorial showing how to setup a Raspberry Pi model A (no ethernet) using a £6-7 console cable and another computer, I used a Mac, but you can also use Windows or Linux. It goes through three tasks, flashing the SD card with Raspbian, connecting through the Console cable and setting up wifi, finally connecting through wifi and SSH.jbeale wrote:I want to figure out the easiest way to setup wifi networking on a headless Pi that has no user-accessible I/O apart from wifi. By "easy" I mean easy to explain to someone who hasn't used a Pi before.
The only thing I can think of so far is for the Pi to start out as a wifi hotspot itself, and serve a web page that the user would access via phone/tablet/etc. to enter the name and password for their wifi router. Maybe they could select from a list of wifi networks from a scan the Pi had previously done at bootup.
Is there a better way? With all the buzz about "Internet of Things" and embedded systems / internet appliances, I suppose this must be a common problem. I recall seeing some wifi routers with an easy setup button that must allow some kind of handshake to allow a new device on the network, but I don't think I can assume everyone has one of those.
That definitely works, but I want users to not have to use an ethernet cable or ssh. What seems like a long workaround above is to avoid ever having to plug in any IO devices at all, including ethernet cable, and to interact solely by a web interface.Richard-TX wrote:I have several Rpis that I run headless. All I do when starting with a new Rpi is to boot with the ethernet connected, login via ssh, drop in my interfaces file and reboot. Poof - it is up and running. No config for supplicant needed.
But what do you do if you have a model A without Ethernet port. That's why I find the console cable so handy.Richard-TX wrote:I have several Rpis that I run headless. All I do when starting with a new Rpi is to boot with the ethernet connected, login via ssh, drop in my interfaces file and reboot. Poof - it is up and running. No config for supplicant needed.
Buy a model B.keithellis wrote:
But what do you do if you have a model A without Ethernet port.
I was kidding. Sortof.keithellis wrote:That is an answer, but the model A is much better when running off batteries for robot or remote projects. It is also cheaper.
Yes it’s easy now, once you have burnt your new Raspbian image, mount the boot directory on you desktop/laptop and create a wpa_suplicant.conf file with your wifi settings.gulliverrr wrote:Does anyone have a solution that works with recent Raspbians as above solution does not work anymore?
NB: probably better to tell people to put it on the FAT partition of the card. If you're on Windows it's the only partition you can access.keithellis wrote:Save both of these files in /boot
Code: Select all
sudo apt-add-repository deb http://repository.nymea.io stretch main sudo apt-get update sudo apt-get install nymea-networkmanager sudo systemctl enable nymea-networkmanager
TBH: I can't see the advantage if I have to install a load of 3rd party software before I can use it. I would have to connect and log in to make the changes first.