Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Björn Smedman" <bs@anyfi.net>
To: David Lang <david@lang.hm>
Cc: "Björn Smedman" <bs@anyfi.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"Derrick Pallas" <pallas@meraki.com>,
	"Avery Pennarun" <apenwarr@google.com>,
	dstanley <dstanley@arubanetworks.com>
Subject: Re: [Cerowrt-devel] Open Source RRM & Hand-Over Optimization (WAS: Throughput regression with `tcp: refine TSO autosizing`)
Date: Tue, 3 Feb 2015 11:13:54 +0100	[thread overview]
Message-ID: <CAJ1dT9z+vjB--Ba4o7=YQ081wJwWDW_q26GTzNPchreCH_OH_Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1502021506460.8636@nftneq.ynat.uz>

On Tue, Feb 3, 2015 at 12:27 AM, David Lang <david@lang.hm> wrote:
> On Mon, 2 Feb 2015, Avery Pennarun wrote:
>> On Mon, Feb 2, 2015 at 11:44 AM, Björn Smedman <bs@anyfi.net> wrote:
>>> 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.
>
> Please keep in touch, when it is released open source I'd be very interested
> in trying it for SCaLE. I'll probably exceed your 100 radio free limit this
> year, and it's hard to justify using non-free code at a linux conference
> (not impossible, but not something I'm going to try to do 3 weeks before the
> show :-)

Will do. :)

> I'm doing social engineering to push people to the 5GHz network (SSID for 5G
> is scale, for 2.4 is scale-slow), it would be great to be able to do this
> directly. And better handoffs as people move around would be good.
>
> It would also be good if something like this could help identify gaps in
> coverage. If it can identify cases where users go from having coverage to
> poor connectivity to having coverage, we can manually investigate to see
> where in the building that is and see what we can do to fix it.

Both of those should be well within scope. :)

  reply	other threads:[~2015-02-03 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 16:44 Björn Smedman
2015-02-02 22:53 ` Avery Pennarun
2015-02-02 23:27   ` David Lang
2015-02-03 10:13     ` Björn Smedman [this message]
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='CAJ1dT9z+vjB--Ba4o7=YQ081wJwWDW_q26GTzNPchreCH_OH_Q@mail.gmail.com' \
    --to=bs@anyfi.net \
    --cc=apenwarr@google.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    --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