T-mon

Hi Kim! glad to hear that it worked for you! We don't support the Raspberry Pi zero w yet, because of the armv6 architecture. But that device is a perfect use case for our little side project. I'll investigate on how much effort it will be to provide a armel solution and will come back to you asap! No, it can't be locked down to a particular phone at this point. Currently the wireless setup is enabled whenever the device is not connected to a network. This means, just rebooting it does not allow hijacking it if the wireless setup has been done before. However, if an attacker manages to disconnect the wireless connection he might be able to open up the server again. We have a solution for that, but not implemented yet. We will continue with development and spend more time for the tool since it got some interest now :-) Cheers, Simon

It's open source, released under GPLv3 also the app!

Hey, we made a tool that allows us to configure the wireless connection of a headless systems using just a smartphone. The reason was that we often ended up in situations where we prepared a headless system with our full stack (see https://nymea.io) and handed it over to someone else to just it in their WLAN. The target group are end users which are not able to use a console. In an attempt to return something to the community we've created a standalone tool for this to share it with others, BerryLan. At the moment it requires to add the nymeas debian repository and install nymea-networkmanager. You can find all the details about it on https://berrylan.app. It was originally designed for the Raspberry Pi, but it works with any other debian based system too. The device must have a wireless adapter and a Bluetooth LE adapter. The daemon works with network-manager and bluez. The source code of the daemon can be found here: https://github.com/guh/nymea-networkmanager By default, this will open up a Bluetooth LE server on the device which allows to connect with the BerryLan app whenever there is no other network connection. As soon as the device is connected to a network (either LAN or WLAN), the Bluetooth server will shut down. This behavior can also be configured to e.g. only allow configuring a network once and then never open up again. We'd be happy for any feedback, please let us know about issues you find. Also we'd love to know if you find this tool useful and if it'd be worth going through the efforts of trying to get it included in the Debian archive. Enjoy, and please do let us know what you think about it! Cheers, Simon