linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Jouni Malinen <j@w1.fi>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [RFC PATCH v2 1/4] mac80211: decrease execution of the associated timer
Date: Fri, 20 Mar 2009 11:41:38 +0100	[thread overview]
Message-ID: <1237545698.5100.145.camel@johannes.local> (raw)
In-Reply-To: <87vdq4lbtq.fsf@litku.valot.fi> (sfid-20090320_113755_292367_61DD61D9)

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

On Fri, 2009-03-20 at 12:37 +0200, Kalle Valo wrote:

> The original (or current) implementation sends probe requests even
> when beacons are received or there is unicast traffic going on. My
> patches change this so that the probe request is only sent when there
> is data idle period (ie. no unicast traffic).

Ok.

> Like we discussed earlier, I think the most optimal solution would be
> to send nullfunc frames during data idle periods just to check that the
> connection is working bothways.
> 
> What should AP do if it receives a nullfunc frame from a station which
> is not associated? Send a deauth frame back to the station? It would
> be nice to check the association state also during the data idle
> period. Sometimes I have noticed that AP might deauthenticate the
> station without station noticing it. It would be just perfect if
> nullfunc frame would do the assocition also during data idle periods.

Yes, I think nullfunc, being data, counts as class 3, and as such the AP
will deauth the station.

> Sorry, I did that only for the period when there is data transmission.
> To get rid of unncessary wakeups altogether I need to do something
> more advanced, like using two timers or something. I haven't thought
> that yet.

Ok, guess I got lost in all the timers.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-03-20 10:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 17:14 [RFC PATCH v2 0/4] mac80211: beacon filtering Kalle Valo
2009-03-14 17:14 ` [RFC PATCH v2 1/4] mac80211: decrease execution of the associated timer Kalle Valo
2009-03-14 17:18   ` Johannes Berg
2009-03-14 18:46     ` Kalle Valo
2009-03-14 19:33       ` Luis R. Rodriguez
2009-03-20  9:22       ` Kalle Valo
2009-03-20  9:42         ` Johannes Berg
2009-03-20 10:37           ` Kalle Valo
2009-03-20 10:41             ` Johannes Berg [this message]
2009-03-14 17:14 ` [RFC PATCH v2 2/4] mac80211: track beacons separately from the rx path activity Kalle Valo
2009-03-14 17:21   ` Johannes Berg
2009-03-14 19:45   ` Luis R. Rodriguez
2009-03-14 19:55     ` Johannes Berg
2009-03-14 20:19       ` Luis R. Rodriguez
2009-03-15  6:52     ` Kalle Valo
2009-03-14 17:14 ` [RFC PATCH v2 3/4] mac80211: disable power save when scanning Kalle Valo
2009-03-14 17:25   ` Johannes Berg
2009-03-14 17:37     ` Kalle Valo
2009-03-14 17:14 ` [RFC PATCH v2 4/4] mac80211: add beacon filtering support Kalle Valo
2009-03-14 17:28   ` Johannes Berg
2009-03-14 17:55     ` Kalle Valo
2009-03-14 20:18   ` Luis R. Rodriguez
2009-03-15  7:22     ` Kalle Valo
2009-03-15 17:59       ` Johannes Berg
2009-03-15 19:27         ` Luis R. Rodriguez
2009-03-15 20:10           ` Kalle Valo
2009-03-16  8:50       ` Jouni Malinen
2009-03-16 12:25         ` Kalle Valo

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=1237545698.5100.145.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.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 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).