From: Martin Weinelt <martin@darmstadt.freifunk.net>
To: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] what is the state of 802.11r, k and v in linux these days?
Date: Fri, 1 May 2020 15:18:42 +0200 [thread overview]
Message-ID: <900201bb-9f1f-59c3-57bb-ba961d22b44d@darmstadt.freifunk.net> (raw)
In-Reply-To: <CAA93jw7TyB7u=mptPa76wM1sfW5QJCpxuaBN_YkWcY29VZKmxw@mail.gmail.com>
On 5/1/20 6:48 AM, Dave Taht wrote:
> I'm so out of date.
>
> https://forum.openwrt.org/t/what-is-the-state-of-802-11r-k-and-v-support-in-openwrt/62363
>
There is DAWN, an implementation of a decentralized controller, which is
probably worth checking out.
https://github.com/berlin-open-wireless-lab/DAWN
It exchanges client information, probe/auth/assoc requests, beacon
reports between DAWN instances on multiple APs and creates a hearing map
to make roaming decisions for clients.
Best,
Martin
prev parent reply other threads:[~2020-05-01 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 4:48 Dave Taht
2020-05-01 9:18 ` Toke Høiland-Jørgensen
2020-05-01 13:18 ` Martin Weinelt [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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=900201bb-9f1f-59c3-57bb-ba961d22b44d@darmstadt.freifunk.net \
--to=martin@darmstadt.freifunk.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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