Skip to contentSkip to conversation

Wake-On-Wireless and Deauthentication

DISCUSSION greg.huber 3 participants 7 messages Jul 17, 2013 – Jul 24, 2013

lore
Share & tools
lore

greg.huber

author
#0 lore raw

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)
[  320.125719] cfg80211: Calling CRDA to update world regulatory domain
[  320.186243] cfg80211: World regulatory domain updated:
[  320.186255] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[  320.186259] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[  320.186263] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[  320.186266] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi,
2000 mBm)
[  320.186270] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[  320.186273] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi,
2000 mBm)
[  320.626022] PM: Syncing filesystems ... done.
[  320.632331] PM: Preparing system for mem sleep
[  320.633223] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  320.644617] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[  320.655788] PM: Entering mem sleep
[  320.655917] Suspending console(s) (use no_console_suspend to debug)
[  320.656856] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  320.657069] serial 00:09: disabled
[  320.657086] serial 00:09: System wakeup disabled by ACPI
[  320.679813] sd 0:0:0:0: [sda] Stopping disk
[  320.681171] <6>[fglrx] IRQ 48 Disabled
[  320.681217] <6>[fglrx] Preparing suspend fglrx in kernel.
[  320.927890] <6>[fglrx] Suspending fglrx in kernel completed.
[  320.927893] <6>[fglrx] Power down the ASIC .
[  321.168217] PM: suspend of devices complete after 511.732 msecs
[  321.168512] PM: late suspend of devices complete after 0.289 msecs

Thanks for any insight you could provide.

Greg

#1 lore raw
Quoted 9 lines · greg.huber

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.

Luis

author
#2 lore raw

Thank you for your reply, I'm trying this now.

Greg

Quoted 19 lines · Luis R. Rodriguez
Quoted 9 lines · greg.huber

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.

Luis

#3 lore raw
Quoted 21 lines · greg.huber

Thank you for your reply, I'm trying this now.

Greg

Quoted 16 lines · Luis R. Rodriguez
Quoted 9 lines · greg.huber

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 <[email protected]>
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

author
#4 lore raw

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

Quoted 38 lines · Arend van Spriel
Quoted 21 lines · greg.huber

Thank you for your reply, I'm trying this now.

Greg

Quoted 16 lines · Luis R. Rodriguez
Quoted 9 lines · greg.huber

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 <[email protected]>
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

author
#5 lore raw
In reply to Arend van Spriel

Not working yet, here's an update

I'm running wireshark wireless and can decode the packets between the test laptop and the AP. Once authenticated I can see the WoW magic-packet on the air.

On the laptop, I disabled the NetworkManager and wpa_supplicant in systemd and run wpa_supplicant manually with an appropriate conf file. I see the association and authentication on wireshark.

Again I can also see WoW magic-packets on the air.

I now put the laptop in suspend to ram. Neither wireshark nor the AP log record any disconnect, but I no longer see the WoW magic-packets on the air.

After resuming from the keyboard I see a 4-way authentication cycle, a deauth and another 4-way. I can see the WoW magic-packets again on wireshark.

Can anyone suggest what I might be doing wrong, or something else to try? Also, if it's system normal to deauth on suspend, can WoW ever work??

I'll pull down the latest RC kernel and give it a try.

Thank You again for your assistance.

Greg

Quoted 38 lines · Arend van Spriel
Quoted 21 lines · greg.huber

Thank you for your reply, I'm trying this now.

Greg

Quoted 16 lines · Luis R. Rodriguez
Quoted 9 lines · greg.huber

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 <[email protected]>
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

author
#6 lore raw
In reply to Luis R. Rodriguez

I moved over to an ARM embedded proto board and was able to get further. When suspended, the wireless card appears to stay awake and I can see the WoW magic-packets as well as other traffic to that NIC. First problem is that this is kernel 3.0.35 which I read does not yet support wake-on-wireless.

The second question that perhaps one of you can answer is whether or not the external WAKE_EN# interrupt signal (pin 1 on a mPCIe card) is used to resume the system, or is the PCIe interrupt expected to resume the system. I scoped the WAKE_EN# signal but do not see any activity. I also looked at later drivers, I don't see this signal activated as an interrupt source, but I'm still looking.

Thank You.

Greg

Quoted 19 lines · Luis R. Rodriguez
Quoted 9 lines · greg.huber

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.

Luis