From: Larry Finger <Larry.Finger@lwfinger.net>
To: Chunkeey@web.de
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Deauthentications with p54usb
Date: Sun, 09 Aug 2009 15:27:58 -0500 [thread overview]
Message-ID: <4A7F314E.7050808@lwfinger.net> (raw)
In-Reply-To: <1756555272@web.de>
Chunkeey@web.de wrote:
> Ahh, wait... screw up: I failed to explain the difference between:
>
> - powersave (=> responsible for your connection problems)
> In this mode: the device goes into a lower power state,
> but continues to listen for dtim beacons and multicast frames,
> from the AP.
>
> mac80211 does not have printks for these ps events,
> since the device power state may chance every second.
>
> howeve, it's possible to trace them through the generic _trace_
> framework with MAC80211_DRIVER_API_TRACER Kconfig
> option enabled.
>
> vs.
>
> - hibernation (soft rfkill that went in with "[PATCH] p54: implement rfkill")
> In this mode: the device's radio is completely shutdown... so
> it only makes sense to enter this mode when there's really nothing
> to do (=> the device is not scanning or associating/associated)
>
> mac80211 will printk (with CONFIG_MAC80211_VERBOSE_DEBUG set)
> whenever the IEEE80211_CONF_IDLE changes. e.g:
> phy0: device no longer idle - REASON
> or:
> phy0: device now idle
> in the kernel logs.
>
>> Turning off CONFIG_CFG80211_DEFAULT_PS stopped the messages,
>> thus it certainly looks like a power saving event.
> so hibernation (rfkill) is fine, just powersave is playing tricks...
> weirdly, intel disabled ps in their driver _again_ not too long ago,
> maybe a coincident, maybe not... do you think you can send me
> a kismet/wireshark/airodump dump whenever the AP kicks the device?
We don't know that hibernation is OK. I just never make my machine
hibernate (suspend to disk) or sleep (suspend to RAM). The last time I
tried it had one or more drivers that would not cooperate, and I have
not tried recently.
I'll try to collect a dump.
> BTW: you can set different PS modes with the old iwconfig utility:
> iwconfig wlanX power off <-- disables PS
> (just like turning off the CONFIG_CFG80211_DEFAULT_PS option)
>
> iwconfig wlanX power timeout 0 <--- most aggressive PS setting,
> (only uses PS-POLL to retrieve data).
>
> AFAIK the current default is just "1", maybe your link would be
> totally reliable with a more _relaxed_ 200, 500 setting...
I'll re-enable CONFIG_CFG80211_DEFAULT_PS and try a more relaxed value
for the power timeout. In any case, with it disabled, there have been
no deauthentications nor disassociations. The link is rock solid.
Larry
next prev parent reply other threads:[~2009-08-09 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 20:02 Deauthentications with p54usb Chunkeey
2009-08-09 20:27 ` Larry Finger [this message]
2010-03-08 23:38 ` Christian Lamparter
2010-03-09 2:12 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2009-08-13 22:27 Chunkeey
2009-08-13 22:53 ` Larry Finger
2009-08-14 10:41 ` Christian Lamparter
2009-08-14 17:17 ` Kalle Valo
2009-08-09 21:45 Chunkeey
2009-08-07 20:50 Larry Finger
2009-08-07 21:50 ` Christian Lamparter
2009-08-09 15:12 ` 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=4A7F314E.7050808@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Chunkeey@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).