The issue with such a feature would be that a novice would likely require a DHCP server to provide any client device with an IP. Without it, a default IP and a requirement for the user to configure their device with a compatible IP would put it beyond many novices.
And then there is the requirement for hostap to be installed and configured.
In the end, how would it be different to the wifi hotspot software using dietpi-software? Would you require a scheduled task to have the Pi detect a returning wireless network?
How many people using this feature would be unable to simply connect via a LAN cable and rely on the auto-ip (169.254.x.x)?
As I know, people seldom use Lan cable.
This function is not for novice, it is right for one who have no idea what a dietpi is.
One who is familier with dietpi could configure a dietpi, and then give the pi to a layman for use.
The layman just needs to know how to simply connect the dietpi to the WIFI, then he could use it.
User need not care about IP. Once a computer or a cellphone connect to the Hotspot set up by dietpi, any time it run a browser, it will open the specific webpage which would let you input the SSID and PASSWORD. Then, user can use a dietpi without know how does it works.
Even we don’t configure WIFI by webpage, we can set the IP for Hotspot as a constant like “10.0.0.1”.
User can simply connect dietpi and set the WIFI with assistance from a specialist.
The service calls a script that checks for presence of the SSID entered into wpa_supplicant.conf, and if not present then starts hostapd and dnsmasq and creates a hotspot. It presently requires mucking about in /etc/network/interfaces and replacing the entire contents with the following.
# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'
# Include files from /etc/network/interfaces.d:
I am about to try it out and will report back it works or doesn’t.