Btw, why doesn't hostapd wait for the interface to show up either (instead it just fails if the interface isn't there, yet)? On Thu, 14 Nov 2019 at 14:12, Tom Yan <tom.ty89@xxxxxxxxx> wrote: > > Currently hostapd is forked to background once the interface state is > changed from the UNINITIALIZED state. Is there any reason no to do > that after it entered the ENABLED state? (Or even, AP-ENABLED, if that > isn't the same thing) > > This is useful if one wants to configure e.g. systemd to trigger a > sequence like (rfkill-unblock ->) hostapd -> rfkill-block, so that > he/she can turn on the AP later by just doing rfkill unblock. (One can > now easily turn it off with just rfkill block, given that hostapd has > successfully enabled the AP.) _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
