Arend, Thank You. I was able to disable NetworkManager and wpa_supplicant and then restarted the supplicant manually. The system did not disconnect when suspended, but it would not wake up on magic packet (what I set it to). On resume it again disconnected and reconnected however. I put a WOW compatible NIC in my laptop and will do some more testing. I also need to verify that the wake packets are making it onto the air. Thank you for all your help. Greg On 07/20/2013 12:50 PM, Arend van Spriel wrote: > On 07/19/13 20:06, greg.huber wrote: >> Thank you for your reply, I'm trying this now. >> >> Greg >> >> On 07/18/2013 09:38 PM, Luis R. Rodriguez wrote: >>> On Wed, Jul 17, 2013 at 11:11 AM, greg.huber<greg.huber@xxxxxxxxxxxxxx> wrote: >>>> I'm trying to get Wake-on-wireless working with an Atheros AR9462. >>>> The problem I seem to be having is that there is a Deauth requested >>>> when the system is suspended. Does anyone know how to keep the >>>> association while suspended?? I'm using kernel 3.9.9. >>>> >>>> The log after waking (from keyboard) >>>> >>>> [ 320.117062] wlp3s0: deauthenticating from 00:24:01:12:de:7a by local choice >>>> (reason=3) >>> Typical managers for networking will disassociate you (and therefore >>> deauth first) prior to kicking the system to suspend. To test WoW you >>> need to run the supplicant manually because as far as I can tell the >>> GUI managers don't consider if WoW was enabled or not. In such a case >>> that WoW was enabled the GUI managers should not send the >>> deauth/disassoc. > > There has been recent commit, which may affect you: > > commit 8125696991194aacb1173b6e8196d19098b44e17 > Author: Stanislaw Gruszka <sgruszka@xxxxxxxxxx> > Date: Thu Feb 28 10:55:25 2013 +0100 > > cfg80211/mac80211: disconnect on suspend > > It is mentioning something about wowlan so I am not sure whether it does. As > you are on 3.9.9 I guess you do not have this commit. > > Regards, > Arend > > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
