Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Avery Pennarun <apenwarr@google.com>
Cc: dstanley@arubanetworks.com,
	Andrew McGregor <andrewmcgr@gmail.com>,
	Stig Thormodsrud <stig@ubnt.com>,
	netdev@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Jesper Dangaard Brouer <jbrouer@redhat.com>,
	Derrick Pallas <pallas@meraki.com>,
	Matt Mathis <mattmathis@google.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	Jonathan Morton <chromatix99@gmail.com>,
	Mahesh Paolini-Subramanya <mahesh@dieswaytoofast.com>,
	Kathy Giori <kgiori@qca.qualcomm.com>,
	Tim Shepard <shep@alum.mit.edu>
Subject: Re: [Cerowrt-devel] Fwd: Throughput regression with `tcp: refine TSO autosizing`
Date: Sun, 1 Feb 2015 23:07:23 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1502012249100.19609@nftneq.ynat.uz> (raw)
In-Reply-To: <CAPp0ZBa43kVBWN5iGgmW=-YQAkdm2DrmMN0URvVu=yXA-_TZCQ@mail.gmail.com>

On Sun, 1 Feb 2015, Avery Pennarun wrote:

> On Sun, Feb 1, 2015 at 9:43 AM,  <dpreed@reed.com> wrote:
>> I personally think that things like promoting semi-closed, essentially
>> proprietary ESSID-based bridged distribution systems as "good ideas" are
>> counterproductive to this goal.  But that's perhaps too radical for this
>> crowd.
>
> Not sure what you mean here.  ESSID-based distribution systems seem
> pretty well defined to me.  The only proprietary part is the
> decision-making process for assisted roaming (ie. the "inter-AP
> protocol") which is only an optional performance optimization.  There
> really should be an open source version of this, and I'm in fact
> feebly attempting to build one, but I don't feel like the world is
> falling apart through not having it.  You can build a bridged
> multi-BSS ESSID today with plain out-of-the-box hostapd.

I will be running a fully opensource bridged ESSID system at SCaLE this month. 
last year we had ~2500 people and devices with ~50 APs deployed, and it worked 
well. The only problem was that I needed to deploy a few more APs to cover some 
of the hallway areas more reliably.

There are tricks that the commercial systems pull that I can't currently 
duplicate with opensource tools. But as Avery says, they are optimizations, not 
something required for successful operation. It would be nice to get the 
assisted roaming portion available. But it's not required.

David Lang

  reply	other threads:[~2015-02-02  7:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+BoTQkVu23P3EOmY_Q3E1GJnWsyF==Pawz4iPOS_Bq5dvfO5Q@mail.gmail.com>
     [not found] ` <1422537297.21689.15.camel@edumazet-glaptop2.roam.corp.google.com>
     [not found]   ` <54CB5D08.2070906@broadcom.com>
     [not found]     ` <1422623975.21689.77.camel@edumazet-glaptop2.roam.corp.google.com>
     [not found]       ` <54CB8B69.1070807@broadcom.com>
     [not found]         ` <CAA93jw5fqhz0Hiw74L2GXgtZ9JsMg+NtYydKxKzGDrvQcZn4hA@mail.gmail.com>
2015-01-31 21:05           ` Dave Taht
2015-01-31 21:51             ` dpreed
2015-02-01  3:06               ` Avery Pennarun
2015-02-01  8:07                 ` Andrew McGregor
2015-02-01  8:45                   ` Dave Taht
2015-02-01 10:47                     ` Jonathan Morton
2015-02-01 14:43                       ` dpreed
2015-02-01 23:34                         ` Andrew McGregor
2015-02-02  4:04                           ` Avery Pennarun
2015-02-02 15:25                             ` Jim Gettys
2015-02-02  4:21                         ` Avery Pennarun
2015-02-02  7:07                           ` David Lang [this message]
2015-02-02 16:22                           ` dpreed
2015-02-02 18:29                             ` David Lang

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=alpine.DEB.2.02.1502012249100.19609@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=andrewmcgr@gmail.com \
    --cc=apenwarr@google.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dstanley@arubanetworks.com \
    --cc=jbrouer@redhat.com \
    --cc=kgiori@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mahesh@dieswaytoofast.com \
    --cc=mattmathis@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pallas@meraki.com \
    --cc=shep@alum.mit.edu \
    --cc=stig@ubnt.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