From: Jouni Malinen <j@w1.fi>
To: Sujith <m.sujith@gmail.com>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net,
mcgrof@gmail.com, jouni.malinen@atheros.com
Subject: Re: [RFC] Handle Channel Switch Announcement
Date: Thu, 18 Dec 2008 09:05:08 +0200 [thread overview]
Message-ID: <20081218070508.GA15803@jm.kir.nu> (raw)
In-Reply-To: <18761.43079.702658.733757@localhost.localdomain>
On Thu, Dec 18, 2008 at 07:02:55AM +0530, Sujith wrote:
> But after receiving a CSA on the current frequency, and having moved to the new
> advertised frequency, can the STA send out probe requests in the earlier frequency ?
> (In case of a scan run or something)
As far as IEEE 802.11 standard is concerned, yes, that would be allowed.
There are not even explicit limits on doing that (if it is a broadcast
probe request, not unicast to the current BSS) before the channel move.
The only thing that the STA has to do immediately (if mode=1) is to
cease to send anything to the current BSS before the channel switch.
When receiving the CSA, the STA needs to decide whether it wants to
follow the AP or not. If not, it could start scanning immediately for
another AP.. The standard even has a following statement about channel
switch: "It should also be stressed that the channel switch process is
distinct from the regulatory requirement to cease transmission on a
particular channel in the presence of radar."
However, the STA must discontinue operation on the channel if it detects
a radar operating in the channel or learns this from another STA. The
regulatory rules on how quickly this must be done (and how much airtime
may be used after the radar has been detected) may be quire strict, so
doing an active scan on the previous channel immediately after having
received a CSA may not be that good of an idea. Then again, channels
that require radar detection should not really allow active scanning on
them in the first place. In that way it would be enough for the non-AP
STA to just stop using the current BSS because any other AP on the same
channel should stop Beaconing, too, when a radar is detected and as
such, the non-AP STA should not end up using the channel anymore.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2008-12-18 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 14:55 [RFC] Handle Channel Switch Announcement Sujith
2008-12-17 16:20 ` Jouni Malinen
2008-12-18 1:32 ` Sujith
2008-12-18 3:59 ` Sujith
2008-12-18 7:05 ` Jouni Malinen [this message]
2008-12-18 7:18 ` Jouni Malinen
2008-12-17 18:07 ` Johannes Berg
2008-12-18 1:36 ` Sujith
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=20081218070508.GA15803@jm.kir.nu \
--to=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=jouni.malinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=m.sujith@gmail.com \
--cc=mcgrof@gmail.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).