From: Simon Wunderlich <sw@simonwunderlich.de>
To: Marek Puzyniak <marek.puzyniak@tieto.com>
Cc: linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH v5] cfg80211: fix dfs channel state after stopping AP
Date: Tue, 17 Dec 2013 15:44:48 +0100 [thread overview]
Message-ID: <201312171544.48479.sw@simonwunderlich.de> (raw)
In-Reply-To: <1387209049-25529-1-git-send-email-marek.puzyniak@tieto.com>
> In AP mode DFS channel state is changed to DFS_AVAILABLE
> after successful CAC and remains as such until a radar
> signal is detected during the In-Service Monitoring.
> When AP is stopped it is no longer monitoring current channel
> for radar signals. DFS channel state should be changed
> to DFS_USABLE when last AP interface is stopped. Starting AP
> again on that channel will start CAC instead of starting radiation.
>
Sorry for answering after so many revisions, but ... why do you think this is
required? Many APs first do a CAC on all available channels, but then pick one
channel and use that, while being able to switch to another channel
immediately.
WIth this patch (if I understand that correctly), this is not possible
anymore. Why do you think it is required? I can not find this requirement in
ETSI, at least.
To quote from ETSI 301.893:
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.
I think this patch is wrong and should not be applied.
Thanks,
Simon
next prev parent reply other threads:[~2013-12-17 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 15:50 [PATCH v5] cfg80211: fix dfs channel state after stopping AP Marek Puzyniak
2013-12-16 20:31 ` Johannes Berg
2013-12-17 14:44 ` Simon Wunderlich [this message]
2013-12-18 9:34 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2013-12-18 9:19 Marek Puzyniak
2013-12-18 11:11 ` 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=201312171544.48479.sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marek.puzyniak@tieto.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).