Return-path: Received: from mail.w1.fi ([212.71.239.96]:58998 "EHLO li674-96.members.linode.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932097AbbCFMuu (ORCPT ); Fri, 6 Mar 2015 07:50:50 -0500 Date: Fri, 6 Mar 2015 14:50:47 +0200 From: Jouni Malinen To: Janusz Dziedzic Cc: Henning Rogge , "linux-wireless@vger.kernel.org" Subject: Re: State of DFS with Mac80211/ath9k Message-ID: <20150306125047.GB26204@w1.fi> (sfid-20150306_135103_063099_0D2963D6) References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-wireless-owner@vger.kernel.org List-ID: 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