Use transition SSID between boot and ready

[rgaudin]

At the moment, as soon as the Pi boots, it starts the hostAPd and thus the WiFi network is visible.Soon after, the docker stack is started with the Captive portal and all. There thus is a risk of someone accessing the WiFi network before the captive portal is ready.

To prevent this from happening we could wait for the Captive portal to be ready before starting the AP but that would prevent anyone from reaching the box if there is any issue down the road. That's just too much information to remove should we need to assit or debug.

Another approach is to start the WiFi as we do but with a different SSID and password. Something static that's documented in the FAQ but that users are not supposed to know so they dont connect to it. (Starting Kiwix Hotspot… for instance with some password.)
Those with the password can connect to it should it be stuck there and debug.

Then, once the captive portal is ready, we restart hostAPd with the correct config and the regular Kiwix Hotspot SSID appears with its pasword.

[benoit74]

I like this idea. As an SSID, maybe Kiwix Factory or Kiwix Maintenance is sufficient / more self-explanatory? Especially since it could be reused during the lifetime of the product if needed, with same password.