2017-03-27 18:16 GMT+02:00 Dan Williams <dcbw@xxxxxxxxxx>:
> I'm actually thinking that the supplicant shouldn't be stopped cleanly
> in this case at all, and I've got to believe that whatever is managing
> system services (systemd? upstart? something else?) can differentiate
> between "shut down and keep WOWLAN enabled" and "shut it all down".
> And maybe that thing should be deciding whether or not to stop the
> supplicant or to just kill it.
To do this the service manager (systemd, sysvinit, whatever) should
have some logic to query the WoWLAN status (via nl80211, wext,
$proprietaryctl..) or needs to be informed that the system is going to
shutdown but with WoWLAN enabled on almost an interface.
This is a bit tricky as an user can enable it manually with iw or
other interfaces.
Also, imagine to have multiple supplicant instances handling multiple
radios, or even worse, a supplicant managing two radios, only one with
WoWLAN enabled. What should the service manager do? Leave wpa_s
running and leaving the wrong one connected too until the timeout, or
kill it and break WoWLAN?
--
Matteo Croce
Ubuntu - Linux For Human Beings
perl -e 'for($t=0;;$t++){print chr($t*($t>>8|$t>>13)&255)}' |aplay
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
