From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Chaoxing Lin <CLin@3eti.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] DFS userspace handler
Date: Wed, 09 Feb 2011 16:50:51 +0100 [thread overview]
Message-ID: <4D52B7DB.8000000@neratec.com> (raw)
In-Reply-To: <BD54DDEB2546894FAB0731EA7B0EDF8D0571DC0A@RockMX01.rock.corp>
On 02/09/2011 04:35 PM, Chaoxing Lin wrote:
> What about DFS in WDS / Mesh / IBSS mode if DFS is only implemented in hostapd?
>
> Will an instance of hostapd be required for all these modes, too?
>
> Thanks
>
Yes, with this approach you will need to have some userspace component that
evaluates the reported pulses and handles channels upon radar detection.
hostapd was taken as the first shot, but one might also think of a dedicated
DFS deamon that takes this role. Actually that is our intended gain of this
approach: having a defined interface for pulse events reporting and highest
flexibility wrt detection and handling.
Cheers
> -----Original Message-----
> From: linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-owner@vger.kernel.org] On Behalf Of Zefir Kurtisi
> Sent: Wednesday, February 09, 2011 7:02 AM
> To: linux-wireless@vger.kernel.org
> Cc: Zefir Kurtisi
> Subject: [RFC] DFS userspace handler
>
> Hello DFS folks,
>
> this is a patch series to prove the concept of DFS handling done in userspace.
>
> It moves the radar pattern detector introduced in [1] and documented in [2]
> from mac80211 up to hostapd.
>
> The basic concept is:
> 1) pattern detection
> * pulse events detected by HW are passed to hostapd
> * hostapd performs per-wiphy DFS pattern matching
> 2) channel handling: on radar detection hostapd
> * updates channel state (NOL handling)
> * switches to new operating channel with TX disabled (on all wiphys)
> * after CAC period enables TX on that channel
>
> The proposed patches provide part 1) of the concept. The nl80211 interface is
> extended with functions to pass DFS pulse events to hostapd.
>
> Testing as described in [2] results in identical output, indicating that both
> approaches (mac80211 and hostapd based) are equivalent from functional point
> of view.
>
> The testing was done with
> * OpenWRT r25417
> * Atheros AR9280 Rev:2
> * DFS radars generated with R&S vector signal generator
>
> We at our company would prefer this approach over the mac80211 based one as
> soon as we see that part 2) can be implemented as proposed.
>
>
>
> Cheers
> Zefir
>
>
>
> [1] http://article.gmane.org/gmane.linux.kernel.wireless.general/61868
> [2] http://linuxwireless.org/en/developers/DFS/DetectorDesignNt
> ---
next prev parent reply other threads:[~2011-02-09 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 12:01 [RFC] DFS userspace handler Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 1/2] nl80211: interface update Zefir Kurtisi
2011-02-09 14:31 ` John W. Linville
2011-02-09 15:32 ` Zefir Kurtisi
2011-02-14 10:20 ` Johannes Berg
2011-02-14 15:54 ` Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 2/2] ath9k: pulse detection Zefir Kurtisi
2011-02-09 15:15 ` Vasanth Thiagarajan
2011-02-09 15:30 ` Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 1/3] hostapd: simple pattern detector Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 2/3] hostapd: nl80211 interface Zefir Kurtisi
2011-02-09 12:01 ` [PATCH 3/3] hostapd: integrate DFS detection Zefir Kurtisi
2011-02-09 14:34 ` [RFC] DFS userspace handler John W. Linville
2011-02-09 15:35 ` Chaoxing Lin
2011-02-09 15:50 ` Zefir Kurtisi [this message]
2011-02-09 16:09 ` Chaoxing Lin
2011-02-09 16:30 ` John W. Linville
2011-02-09 17:09 ` Chaoxing Lin
2011-02-09 17:50 ` Jouni Malinen
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=4D52B7DB.8000000@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=CLin@3eti.com \
--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).