Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Björn Smedman" <bs@anyfi.net>
To: Avery Pennarun <apenwarr@google.com>, David Reed <dpreed@reed.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	dstanley@arubanetworks.com, Derrick Pallas <pallas@meraki.com>
Subject: [Cerowrt-devel] Open Source RRM & Hand-Over Optimization (WAS: Throughput regression with `tcp: refine TSO autosizing`)
Date: Mon, 2 Feb 2015 17:44:38 +0100	[thread overview]
Message-ID: <CAJ1dT9x+vWm4uZ-r9PZrTmKjEQc260NhOKoRzH=Ab=oWkeZ83w@mail.gmail.com> (raw)

On Mon, Feb 2, 2015 at 5:21 AM, Avery Pennarun <apenwarr@google.com> wrote:
> On Sun, Feb 1, 2015 at 9:43 AM,  <dpreed@reed.com> wrote:
>> Just to clarify, managing queueing in a single access point WiFi network is
>> only a small part of the problem of fixing the rapidly degrading performance
>> of WiFi based systems.
>
> Can you explain what you mean by "rapidly degrading?"  The performance
> in odd situations is certainly not inspirational, but I haven't
> noticed it getting worse over time.
>
>> Similarly, mesh routing is only a small part of the
>> problem with the scalability of cooperative meshes based on the WiFi MAC.
>
> That's certainly true.  Not to say the mesh routing algorithms are
> much good either.
>
>>  Also, as we noted
>> earlier, "handoff" from one next hop to another is a huge problem with
>> performance in practical deployments (a factor of 10x at least, just in
>> that).
>
> While there is definitely some work to be done in handoff, it seems
> like there are some find implementations of this already in existence.
> Several brands of "enterprise access point" setups seem to do well at
> this.  It would be nice if they interoperated, I guess.
>
> The fact that there's no open source version of this kind of handoff
> feature bugs me, but we are working on it here and the work is all
> planned to be open source, for example: (very early version)
> https://gfiber.googlesource.com/vendor/google/platform/+/master/waveguide/

We've got an SDN-inspired architecture with 802.11 frame tunneling (a
la CAPWAP), airtime fairness, infrastructure initiated hand-over,
Opportunistic Key Caching (OKC), IEEE 802.11r Fast BSS Transition and
a few more goodies. It's currently free as in beer
(http://anyfi.net/software,
https://github.com/carrierwrt/carrierwrt/pull/7 and
http://www.anyfinetworks.com/download) up to 100 APs, but we're
definitely going to open source in one form or another.

We've also tried to raise some interest in fixing up CAPWAP
(https://www.ietf.org/mail-archive/web/opsawg/current/msg03196.html),
which is (unfortunately) the best open standard at the moment.
Interest seems marginal though...

If anybody's interested in joining forces on either front we'd be be
happy to talk.

Cheers,

Björn

             reply	other threads:[~2015-02-02 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 16:44 Björn Smedman [this message]
2015-02-02 22:53 ` Avery Pennarun
2015-02-02 23:27   ` David Lang
2015-02-03 10:13     ` Björn Smedman
2015-02-03 10:02   ` Björn Smedman

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ1dT9x+vWm4uZ-r9PZrTmKjEQc260NhOKoRzH=Ab=oWkeZ83w@mail.gmail.com' \
    --to=bs@anyfi.net \
    --cc=apenwarr@google.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    --cc=dstanley@arubanetworks.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pallas@meraki.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