From: Jonathan Morton <chromatix99@gmail.com>
To: "Luis E. Garcia" <luis@bitamins.net>
Cc: Dave Taht <dave.taht@gmail.com>,
make-wifi-fast@lists.bufferbloat.net,
bufferbloat-fcc-discuss
<bufferbloat-fcc-discuss@lists.redbarn.org>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] arstechnica confirms tp-link router lockdown
Date: Fri, 11 Mar 2016 21:07:44 +0200 [thread overview]
Message-ID: <C697DA79-E676-4579-BCEF-95A8D28336B1@gmail.com> (raw)
In-Reply-To: <CALnBQ5=B7fEDSmHBXGp2BL+np88qSUhjwF1Z6KESsQM3Y78v_g@mail.gmail.com>
> On 11 Mar, 2016, at 20:22, Luis E. Garcia <luis@bitamins.net> wrote:
>
> Time to start building our own.
A big project in itself - but perhaps a worthwhile one. We wouldn’t be able to compete on price against the Taiwanese horde, but price is not the only market force on the table. Firmware quality is a bit abstract and nebulous to sell to ordinary consumers, but there is one thing that might just get their attention.
Making the damned thing easier to configure.
Almost every router now on the market is a blank box with some ports on the back, some antennas on top and some lights on the front. If you’re lucky, there’ll be a button for WPS (which most consumers would still need to read the manual to figure out how to use, and most tinkerers would turn right off) and maybe one or two “feature switches”; my Buffalo device has one which does “something” to the QoS setup in the stock firmware, and nothing at all in OpenWRT.
The lights only tell you that “something is happening” and occasionally “something is wrong”, and are invariably cryptic. For example, a green flashing light can mean “it’s setting up but not working yet” or “it’s working and passing traffic right now”, often on the same light! A critical error, such as a cable not plugged in, is often signified only by the *absence* of one of the several normal lights, which is invisible to the untrained eye.
To actually configure it, you must first connect a computer to it and point a Web browser at the right (usually numeric) URL. This URL varies between vendors and models, and sometimes even between firmware revisions; the only infallible way to determine it is to delve into the configuration that DHCP handed out.
You and I can cope with that, but we want something better, and less-technical people *need* something better if they are to trust their equipment enough to start actually learning about it.
As a starting point, suppose we build a small display into the case, and invite the user to temporarily plug a keyboard, console controller or even a mouse directly into the USB port (which most routers now have) to do the setup? No Web browser required, and no potentially-vulnerable web server on the device either.
When not in config mode, the input device can be disconnected and returned to its primary role, and the display can offer status information in a human-readable format; an RGB-controlled backlight would be sufficient for at-a-glance is-everything-okay checks (which is all Apple gives you without firing up their proprietary config software on a connected computer). Some high-end router models provide just this, without leveraging the possibility of easier setup.
- Jonathan Morton
next prev parent reply other threads:[~2016-03-11 19:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 18:17 [Make-wifi-fast] " Dave Taht
2016-03-11 18:22 ` [Make-wifi-fast] [Cerowrt-devel] " Luis E. Garcia
2016-03-11 19:07 ` Jonathan Morton [this message]
2016-03-11 19:31 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Paul Vixie
2016-03-11 20:26 ` [Make-wifi-fast] " Alan Jenkins
2016-03-11 20:40 ` David Lang
2016-03-12 9:38 ` Jonathan Morton
2016-03-13 0:15 ` David Lang
2016-03-13 15:18 ` Jonathan Morton
2016-03-13 17:40 ` moeller0
2016-03-13 18:17 ` Jonathan Morton
2016-03-13 18:25 ` moeller0
2016-03-13 20:15 ` Jonathan Morton
2016-03-13 21:17 ` moeller0
[not found] ` <CAEfCu-p+87PkRrN-=9=-CA3JpQesRU2RDmxN-yEJt_95Au-yxA@mail.gmail.com>
2016-03-13 17:48 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Dave Taht
2016-03-13 18:23 ` [Make-wifi-fast] [Cerowrt-devel] [bufferbloat-fcc-discuss] " moeller0
2016-03-13 23:22 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] [Cerowrt-devel] " David Lang
[not found] ` <CAEfCu-o7hb+6O0NNc4oUrn7noaVvBhBJK3zNjB8mWtgVtkqpZg@mail.gmail.com>
2016-03-14 1:03 ` David Lang
[not found] ` <CAEfCu-rQN+H7h0OY_3CSrrGcVZ=A4=b0XTAU2h3Pz3_ksh56dw@mail.gmail.com>
2016-03-12 19:14 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Henning Rogge
2016-03-12 20:18 ` Adrian Chadd
[not found] ` <CAEfCu-rmR=p1bAGJjPvaMMBAjKRU1wBeZW4ZQCZVm5eVXCCRQQ@mail.gmail.com>
2016-03-12 22:20 ` Dave Taht
2016-03-13 1:04 ` David Lang
[not found] ` <CAEfCu-r-C3C6P2LpKJduvX733YnbwxBF6nOFAPEMbF28qjRXBg@mail.gmail.com>
2016-03-13 8:06 ` David Lang
2016-03-14 0:51 ` Adrian Chadd
2016-03-14 1:25 ` David Lang
2016-03-13 18:19 ` Dave Taht
2016-03-13 1:00 ` 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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C697DA79-E676-4579-BCEF-95A8D28336B1@gmail.com \
--to=chromatix99@gmail.com \
--cc=bufferbloat-fcc-discuss@lists.redbarn.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=luis@bitamins.net \
--cc=make-wifi-fast@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