From: Ben Greear <greearb@candelatech.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Logs spammed by associate / authenticate / CRDA calls
Date: Mon, 17 Jan 2011 14:02:43 -0800 [thread overview]
Message-ID: <4D34BC83.2030406@candelatech.com> (raw)
In-Reply-To: <AANLkTin_DESckMrOMK41z3oJtXwmHvL026Mi8ayLeKLA@mail.gmail.com>
On 01/17/2011 12:26 PM, Daniel Halperin wrote:
> On Mon, Jan 17, 2011 at 12:18 PM, Larry Finger
> <Larry.Finger@lwfinger.net> wrote:
>> The MAC address for the device is 00:1F:1F:C8:8E:CB and that of the AP is
>> C0:3F:0E:BE:2B:45, thus corresponding with the above output.
>>
>> Is scanning this often normal? I suspect it is, but I have not looged the events
>> before.
>>
>> Although both AP and STA support 802.11n, the connection is 802.11g (max 54
>> Mbps) using WPA2-PSK.
>>
>> What triggers the "Disassociated due to inactivity"?
>
> Scanning happens every time you associate/re-associate; disassociation
> due to inactivity happens when your device doesn't send packets to the
> AP for some period of time. It looks like your AP's (or device's)
> timeout is 100s.
From what I can tell, this message can also happen if the local
STA thinks it cannot connect to the remote. For instance, if it
doesn't get a TX callback within 500ms for ath5k/ath9k (and perhaps
others).
Thanks,
Ben
>
> Dan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-01-17 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 20:18 Logs spammed by associate / authenticate / CRDA calls Larry Finger
2011-01-17 20:26 ` Daniel Halperin
2011-01-17 22:02 ` Ben Greear [this message]
2011-01-17 22:26 ` Larry Finger
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=4D34BC83.2030406@candelatech.com \
--to=greearb@candelatech.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dhalperi@cs.washington.edu \
--cc=linux-wireless@vger.kernel.org \
/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.