linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Goodenough <david.goodenough@btconnect.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [RFC 0/7] hostap: add DFS master ability
Date: Mon, 30 Jan 2012 11:08:43 +0000	[thread overview]
Message-ID: <201201301108.43737.david.goodenough@btconnect.com> (raw)
In-Reply-To: <CAGRGNgVhSdTNnmfw0=KHYEEz1r=5=uQbUNvPwTXODnS3LJmr=w@mail.gmail.com>

On Monday 30 Jan 2012, Julian Calaby wrote:
> On Mon, Jan 30, 2012 at 21:35, David Goodenough
> 
> <david.goodenough@btconnect.com> wrote:
> > On Monday 30 Jan 2012, Goldenshtein, Victor wrote:
> >> On Thu, Jan 26, 2012 at 9:27 PM, David Goodenough
> >> 
> >> <david.goodenough@btconnect.com> wrote:
> >> > As I understand it hostapd is not involved in mesh (802.11s) networks,
> >> > so how does this integrate there?  As I understand it 802.11s is
> >> > entirely done in the kernel.
> >> 
> >> At this point we don't have any plans to extend DFS support to mesh
> >> networks.
> > 
> > That is fine, and obviously your choice.  My point is simply that
> > provision so that someone else can add it would be sensible, and in
> > particular to assume that anything that could have mesh support would
> > have a userland component kind of locks it out as I understand 802.11s
> > support at the moment.
> 
> I understand that using *secure* mesh requires a userspace component:
> 
> http://o11s.org/trac/wiki/HOWTO
> 
> Arguably there's no reason why a separate userspace component couldn't
> handle DFS for mesh interfaces. A project for the future could be to
> split it out of hostapd so it can be re-used for interfaces that
> aren't managed by hostapd.
> 
> Thanks,
True, I had not thought of that one.  So maybe it would be worth making
the DFS code in hostapd sufficiently modular that it can easily be moved/
copies/re-implemented into other environments.

David

  reply	other threads:[~2012-01-30 11:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 12:41 [RFC 0/7] hostap: add DFS master ability Victor Goldenshtein
2012-01-26 12:41 ` [RFC 1/7] hostapd: implement dfs drv ops functions Victor Goldenshtein
2012-02-09 23:19   ` Luis R. Rodriguez
2012-02-15 16:47     ` Goldenshtein, Victor
2012-01-26 12:41 ` [RFC 2/7] hostapd: add channel switch ability Victor Goldenshtein
2012-01-26 12:41 ` [RFC 3/7] hostapd: add dfs events Victor Goldenshtein
2012-01-26 12:41 ` [RFC 4/7] hostapd: add dfs support into interface init flow Victor Goldenshtein
2012-01-26 13:10   ` Felix Fietkau
2012-01-26 13:36     ` Goldenshtein, Victor
2012-01-26 12:41 ` [RFC 5/7] nl80211: add support to enable TX on oper-channel Victor Goldenshtein
2012-01-26 12:41 ` [RFC 6/7] nl80211: add channel switch command/event Victor Goldenshtein
2012-01-26 12:41 ` [RFC 7/7] nl80211: add start radar detection command/event Victor Goldenshtein
2012-01-26 19:27 ` [RFC 0/7] hostap: add DFS master ability David Goodenough
2012-01-30  7:32   ` Goldenshtein, Victor
2012-01-30 10:35     ` David Goodenough
2012-01-30 11:02       ` Julian Calaby
2012-01-30 11:08         ` David Goodenough [this message]
2012-02-09 20:18           ` Luis R. Rodriguez

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=201201301108.43737.david.goodenough@btconnect.com \
    --to=david.goodenough@btconnect.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).