From: Simon Wunderlich <sw@simonwunderlich.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Antonio Quartulli <a@unstable.cc>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mac80211: passively scan DFS channels if requested
Date: Mon, 24 Oct 2016 16:36:51 +0200 [thread overview]
Message-ID: <4116422.yZP7iyh9mq@prime> (raw)
In-Reply-To: <1477318562.4085.28.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 2513 bytes --]
On Monday, October 24, 2016 4:16:02 PM CEST Johannes Berg wrote:
> On Mon, 2016-10-24 at 15:42 +0200, Simon Wunderlich wrote:
> > Otherwise, it would be pretty much impossible to perform CSAs to
> > another DFS channel.
>
> I was told that to do that you'd need another NIC that's pre-CAC'ing
> another channel.
Here is the portion from ETSI 301 893 v1.8.1 [1] (the most recent one to my
knowledege), section 4.7.1.4 which describes operation from master devices
(Access Points):
<snip>
b) A master device shall only start operations on Available Channels. At
installation (or reinstallation) of the equipment, the RLAN is assumed to have
no Available Channels within the band 5 250 MHz to 5 350 MHz and/or 5 470 MHz
to 5 725 MHz. In such a case, before starting operations on one or more of
these channels, the master device shall perform either a Channel Availability
Check or an Off-Channel CAC to ensure that there are no radars operating on
any selected channel. If no radar has been detected, the channel(s) becomes an
Available Channel(s) and remains as such until a radar signal is detected
during the In-Service Monitoring.
The Channel Availability Check or the Off-Channel CAC may be performed over a
wider bandwidth such that all channels within the tested bandwidth become
Available Channels.
NOTE 1:The initial Channel Availability Check may be activated manually at
installation or reinstallation of the equipment.
c) Once the RLAN has started operations on an Available Channel, then that
channel becomes an Operating Channel. During normal operation, the master
device shall monitor all Operating Channels (In-Service Monitoring) to ensure
that there is no radar operating within these channel(s). If no radar was
detected on an Operating Channel but the RLAN stops operating on that channel,
then the channel becomes an Available Channel.
NOTE 2:An RLAN is allowed to start transmissions on multiple (adjacent or non-
adjacent) Available Channels. In this case all these channels become Operating
Channels.
<snap>
As I interpret this, (b) states explicitly that we can have many available
channels. We only need to mark channels where we detect a radar.
BTW, there was also something like a 24h disconnect previously, which was
removed in 2009 [2].
Cheers,
Simon
[1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/01.08.01_60/
en_301893v010801p.pdf
[2] http://www.wlan-skynet.de/docs/rechtliches/etsi_301_893.shtml (german
only)
>
> johannes
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-10-24 14:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 1:29 [PATCH v2 1/2] nl80211: add flag to force passive scan on DFS channels Antonio Quartulli
2015-11-14 1:29 ` [PATCH v2 2/2] mac80211: passively scan DFS channels if requested Antonio Quartulli
2015-11-20 10:49 ` Johannes Berg
2015-11-20 12:52 ` Antonio Quartulli
2016-10-24 12:11 ` Antonio Quartulli
2016-10-24 13:33 ` Johannes Berg
2016-10-24 13:35 ` Antonio Quartulli
2016-10-24 13:42 ` Simon Wunderlich
2016-10-24 14:07 ` Michal Kazior
2016-10-24 14:16 ` Johannes Berg
2016-10-24 14:36 ` Simon Wunderlich [this message]
2016-10-24 14:38 ` Johannes Berg
2016-10-24 14:53 ` Simon Wunderlich
2016-10-26 12:58 ` Johannes Berg
2016-10-26 13:30 ` Simon Wunderlich
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=4116422.yZP7iyh9mq@prime \
--to=sw@simonwunderlich.de \
--cc=a@unstable.cc \
--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;
as well as URLs for NNTP newsgroup(s).