public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: wait for beacon before associating
Date: Mon, 25 Jan 2010 14:25:48 +0100	[thread overview]
Message-ID: <4B5D9BDC.8030307@openwrt.org> (raw)
In-Reply-To: <1264423044.23766.39.camel@johannes.local>

On 2010-01-25 1:37 PM, Johannes Berg wrote:
> This patch makes mac80211 wait for a beacon
> before associating to have proper information
> from it, in particular the DTIM period. It
> also makes it not probe the AP if it already
> has a probe response, so that only one of
> probing and waiting for beacon can be done,
> one of them must have been received to know
> about the BSS.
> 
> Note that I don't think this helps the
> synchronisation issue Kalle pointed out since
> we do not tell the driver about the bssid, in
> fact in this patch I explicitly open up the
> filters to receive the beacon.
> 
> The default timeout is 112.5% of the beacon
> interval, so a single lost beacon could cause
> the association to fail, I'm not sure if that
> is desirable or if the default timeout should
> be longer.
I think if this is required only for powersave, it would be nice if it
would only wait for the beacon if either powersave is actually enabled,
or user space requests it.
I'd like to avoid making the assoc process more unreliable for noisy
environments in cases where it isn't necessary to do so.

- Felix

  reply	other threads:[~2010-01-25 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25 12:37 [RFC] mac80211: wait for beacon before associating Johannes Berg
2010-01-25 13:25 ` Felix Fietkau [this message]
2010-01-25 13:41   ` Johannes Berg

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=4B5D9BDC.8030307@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=johannes@sipsolutions.net \
    --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