From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>, David Lang <david@lang.hm>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Dual Channel Wi-Fi
Date: Fri, 13 Sep 2019 13:58:18 +0200 [thread overview]
Message-ID: <87muf8s90l.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw4AK7xz6R+SXiOmze1w9P5Z4OtN8xrdL8g3jn+2+d6Ang@mail.gmail.com>
Dave Taht <dave.taht@gmail.com> writes:
> There's more to it than that.
>
> https://www-res.cablelabs.com/wp-content/uploads/2019/06/24150908/Dual-Channel-Wi-Fi-Performance-Test-Report-June-2019.pdf
Looking at the code[0], it seems to be a userspace daemon that does
encapsulation of traffic and sends it over a separate, hidden BSS that
is access-controlled to only allow stations that already performed their
handshake.
So, conceptually it turns several WiFi links into a bonded device where
the AP can steer the traffic between underlying devices.
It's an interesting idea, but I doubt it'll see much deployment: Just
the requirement of running a daemon on each client device is bound to
put a damper on that. It's not quite clear to me whether the station
would need to support associating on multiple bands at the same time;
not sure how many clients do that...
Also, I wonder how well the userspace encapsulation stuff works on a
low-powered AP?
-Toke
[0] https://github.com/ewsi/dcstad is the client daemon; the github org
has the rest.
prev parent reply other threads:[~2019-09-13 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 5:47 Etienne Champetier
2019-09-13 6:01 ` Dave Taht
2019-09-13 6:03 ` David Lang
2019-09-13 6:13 ` Dave Taht
2019-09-13 7:18 ` Dave Taht
2019-09-13 9:13 ` Sebastian Moeller
2019-09-13 11:58 ` Toke Høiland-Jørgensen [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muf8s90l.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=david@lang.hm \
/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