From: Jouni Malinen <j@w1.fi>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: Henning Rogge <hrogge@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: State of DFS with Mac80211/ath9k
Date: Fri, 6 Mar 2015 14:50:47 +0200 [thread overview]
Message-ID: <20150306125047.GB26204@w1.fi> (raw)
In-Reply-To: <CALhHN=oQ99+tp2zAPmM2Tzu3WWrgtH=xnc0iqTUPVJTjyWV+Yg@mail.gmail.com>
On Fri, Mar 06, 2015 at 01:29:06PM +0100, Janusz Dziedzic wrote:
> So, in case of ibss/mesh you could make wpa_supplicant dfs.c common
> and use it (perform CAC and other operations).
I actually pushed out changes yesterday to allow dfs.c/CAC to be used
from wpa_supplicant in case of AP mode operations. I have not tried what
would happen with mesh in similar case, but that may need changes and
IBSS certainly would require more work for DFS.
> > Has the "802.11s support" ever been merged to wpa_supplicant?
> >
> > At the moment we are using neither wpa_supplicant nor hostapd... when
> > we use encryption, we use the authsae tool from the open802.11s page.
> >
> I am not sure, adding Jouni here.
Yes, wpa_supplicant has support for mesh BSS since November.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2015-03-06 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 8:04 State of DFS with Mac80211/ath9k Henning Rogge
2015-03-06 8:38 ` Janusz Dziedzic
2015-03-06 9:26 ` Henning Rogge
2015-03-06 12:29 ` Janusz Dziedzic
2015-03-06 12:50 ` Jouni Malinen [this message]
2015-03-06 12:54 ` Henning Rogge
2015-03-06 13:00 ` Jouni Malinen
2015-03-06 12:24 ` Zefir Kurtisi
2015-03-06 12:32 ` Henning Rogge
2015-03-06 15:36 ` Zefir Kurtisi
[not found] ` <54F9A41F.4090505@neratec.com>
[not found] ` <CAGnRvuqpD6YHS6wJFR5J3n0sQqM3cfKYcydE4wYE52eiZjZeDA@mail.gmail.com>
[not found] ` <54F9C7B1.3090406@neratec.com>
2015-03-07 8:33 ` Henning Rogge
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=20150306125047.GB26204@w1.fi \
--to=j@w1.fi \
--cc=hrogge@gmail.com \
--cc=janusz.dziedzic@tieto.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).