linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 17 Dec 2008 18:20:17 +0200	[thread overview]
Message-ID: <20081217162017.GA28712@jm.kir.nu> (raw)
In-Reply-To: <18761.4838.509784.281821@localhost.localdomain>

On Wed, Dec 17, 2008 at 08:25:34PM +0530, Sujith wrote:
> This is an attempt to handle CSA elements from an AP and switch
> to the specified channel.
> 
> Only mode 1 is handled, i.e, we just stop transmission on receiving a CSA element.
> User space notification is not handled yet.

> diff --git a/include/net/wireless.h b/include/net/wireless.h
> + * @IEEE80211_CHAN_CSA_DISABLED: Disabled because a
> +	Channel Switch Announcement was received on this channel.

Why is this flag needed? Or well, the better question: Why is the
channel disabled? CSA may request the STA to stop transmitting _within
the BSS_ until the AP has changed channels (i.e., it could be possible
to use other BSSes even on the same channel). This notification can be
used for other things than just reporting a radar on the channel (e.g.,
the AP could move to a channel that has less traffic on it).

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2008-12-17 16:20 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 [this message]
2008-12-18  1:32   ` Sujith
2008-12-18  3:59     ` Sujith
2008-12-18  7:05     ` Jouni Malinen
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=20081217162017.GA28712@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).