[PATCH] hostapd: Add wowlan_triggers config param

Jouni Malinen j
Sat Sep 13 07:17:58 PDT 2014

On Wed, Sep 03, 2014 at 02:58:37PM -0700, Dmitry Shmidt wrote:
> New kernels in wiphy_suspend() will call cfg80211_leave_all()
> that will eventually end up in cfg80211_stop_ap() unless
> wowlan_triggers were set.

Could you please clarify why this is needed? If kernel behavior changed
at some point to do something that is not desired, wouldn't the correct
way of fixing this be by reverting parts of the kernel behavior rather
than by trying to make hostapd do something.

I don't understand what WoWLAN triggers have to do with AP mode
operations. Or would there really be a case where WoWLAN can be used
from a station device to wake up the AP?

I'm assuming this is trying to undo some parts of kernel commit
8125696991194aacb1173b6e8196d19098b44e17 ('cfg80211/mac80211: disconnect
on suspend'). Is that the case or did I miss what the main point of the
hostapd changes here would be?

Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list