ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Cc: Zach Sherin <zach@netblazr.com>,
	benjamin@sipsolutions.net,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	Peter Oh <peter.oh@bowerswilkins.com>
Subject: Re: Is using 802.11s with DFS possible?
Date: Fri, 30 Jun 2017 11:48:29 +0200	[thread overview]
Message-ID: <2614300.ercbpO68rJ@prime> (raw)
In-Reply-To: <CAEFj986gxesLcSaeVH9Yfwre7cTB0uqSzHBMpZKSNbmgQFcmhA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1378 bytes --]

On Friday, June 30, 2017 12:08:51 PM CEST Chun-Yeow Yeoh wrote:
> On Fri, Jun 30, 2017 at 1:53 AM, Peter Oh <peter.oh@bowerswilkins.com> 
wrote:
> > On 06/28/2017 06:54 PM, Zach Sherin wrote:
> >> Hi all,
> >> 
> >> I've been running some experiments in LEDE thanks to your help many
> >> months ago, and I want to use DFS frequencies with my mesh network.
> >> Does ath10k currently support this or am I up a creek? My tests show
> >> that I can use DFS frequencies with AP mode but have always failed
> >> when I use them in a mesh, such that the interface won't even start.
> >> 
> >> Any suggestions?
> > 
> > As far as I know, no DFS channels enabled in mesh mode at this moment.
> > To support DFS channels in mesh mode, wpa_supplicant and mac80211 changes
> > are required.
> 
> https://www.spinics.net/lists/linux-wireless/msg162307.html
> Simon and Benjamin have submitted the above patches and some of them
> has upstream to mac80211-next.
> 
> Perhaps, Simon and Benjamin can comment on this.

Our mac80211 patches have been upstreamed. However, the (experimental) 
wpa_supplicant patches have not been adopted and I've reworked them a little 
but they are not in a state to resubmit yet. So I don't expect the 
wpa_supplicant portion to work yet, and you also may need to think of a good 
way to have the mesh peers on a channel succession order.

Cheers,
     Simon

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2017-06-30  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29  1:54 Is using 802.11s with DFS possible? Zach Sherin
2017-06-29 17:53 ` Peter Oh
2017-06-30  4:08   ` Chun-Yeow Yeoh
2017-06-30  9:48     ` Simon Wunderlich [this message]
2017-06-30 11:23       ` Benjamin Berg

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=2614300.ercbpO68rJ@prime \
    --to=sw@simonwunderlich.de \
    --cc=ath10k@lists.infradead.org \
    --cc=benjamin@sipsolutions.net \
    --cc=peter.oh@bowerswilkins.com \
    --cc=yeohchunyeow@gmail.com \
    --cc=zach@netblazr.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