From: Benjamin Berg <benjamin@sipsolutions.net>
To: Simon Wunderlich <sw@simonwunderlich.de>,
Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Cc: Zach Sherin <zach@netblazr.com>,
"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 13:23:20 +0200 [thread overview]
Message-ID: <1498821800.4798.2.camel@sipsolutions.net> (raw)
In-Reply-To: <2614300.ercbpO68rJ@prime>
[-- Attachment #1.1: Type: text/plain, Size: 1300 bytes --]
On Fri, 2017-06-30 at 11:48 +0200, Simon Wunderlich wrote:
> 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.
For reference, an earlier version of the patchset was submitted as an
RFC in November with a bit of follow up discussion later:
http://lists.infradead.org/pipermail/hostap/2016-November/036726.html
http://lists.infradead.org/pipermail/hostap/2016-December/036741.html
There have been improvements since (e.g. solving the use after free
issue) that are not yet submitted. I cannot comment on the current
state of the patches though.
In general a major issue is making sure that all stations switch to the
same channel when a radar is detected. There is a simple mechanism in
the standard for this which to my knowledge is not implemented in
mac80211 at this point. But even with this in place you will likely
want a versatile mechanism in hostap for stations to switch to a common
channel should they end up on differing ones.
Regards,
Benjamin
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 855 bytes --]
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2017-06-30 11:23 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
2017-06-30 11:23 ` Benjamin Berg [this message]
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=1498821800.4798.2.camel@sipsolutions.net \
--to=benjamin@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=peter.oh@bowerswilkins.com \
--cc=sw@simonwunderlich.de \
--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