From: "Arend van Spriel" <arend@broadcom.com>
To: "greg.huber" <greg.huber@carestream.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
daniel.wagner@oss.bmw-carit.de, "Dan Williams" <dcbw@redhat.com>
Subject: Re: Wake-On-Wireless and Deauthentication
Date: Sat, 20 Jul 2013 18:50:18 +0200 [thread overview]
Message-ID: <51EABFCA.4060307@broadcom.com> (raw)
In-Reply-To: <51E9800C.8040007@carestream.com>
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@carestream.com> 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@redhat.com>
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
next prev parent reply other threads:[~2013-07-20 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 18:11 Wake-On-Wireless and Deauthentication greg.huber
2013-07-19 1:38 ` Luis R. Rodriguez
2013-07-19 18:06 ` greg.huber
2013-07-20 16:50 ` Arend van Spriel [this message]
2013-07-22 12:22 ` greg.huber
2013-07-23 18:23 ` greg.huber
2013-07-24 13:56 ` greg.huber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51EABFCA.4060307@broadcom.com \
--to=arend@broadcom.com \
--cc=daniel.wagner@oss.bmw-carit.de \
--cc=dcbw@redhat.com \
--cc=greg.huber@carestream.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.