From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] the 3 focus problems we have
Date: Mon, 16 Mar 2015 10:01:01 -0700 [thread overview]
Message-ID: <CAA93jw5CE9eZUA0EbHrzC1Sjad5g_gu_ad7RnLCbeq6ygYE0JA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
1) We need a new box that can do inbound shaping at up to 300mbit. So far
that box has not appeared. We have not explored policing as an alternative.
2) We need a new box that anyone can use that should be available for 2-3
years to come.
3) I'd like to be focused mostly on wifi, personally.
Do we have more top-level problems than this?
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
[-- Attachment #2: Type: text/html, Size: 776 bytes --]
next reply other threads:[~2015-03-16 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 17:01 Dave Taht [this message]
2015-03-16 17:34 ` David Lang
2015-03-16 17:35 ` Dave Taht
2015-03-16 17:49 ` David Lang
2015-03-19 16:01 ` Richard Smith
2015-03-19 19:32 ` Aaron Wood
2015-03-19 20:15 ` 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=CAA93jw5CE9eZUA0EbHrzC1Sjad5g_gu_ad7RnLCbeq6ygYE0JA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@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