From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] TP-link archer C5 AC1200 - Still no truth in labeling
Date: Wed, 3 Feb 2016 16:09:41 -0800 [thread overview]
Message-ID: <CAA93jw7JDgXo+-Lb7yBrtNDZ2y+vRF6PiDCRz3vSY=vmN-5_5A@mail.gmail.com> (raw)
So I've been getting setup again for a run against make-wifi-fast.
Today I went to frys to refresh my hardware. I knew that the tp-link
archer C5 was "good", so I got one... opened the box... only to find
that it was a C5 v2 (only noted on the router itself), which is a
complete swap-out from the well supported-by-openwrt atheros mips
chipset to a broadcom and totally-unsupported by openwrt *arm* one.
https://wiki.openwrt.org/toh/tp-link/archer-c5-c7-wdr7500
If porshe completely swapped out the engine and all the electronics
from model year to model year, and switched from diesel to gas, they'd
at least somehow, make clear that "stuff had changed under the hood".
Somehow, this awful habit of the home router industry has gotta change.
While I look forward to benchmarking a "new" product with it's
default firmware, it was not my intent to support in any way yet
another model change of this sort. To add even more insult to
injury... this ostensibly "new" product is running kernel 2.6.36.4
according to their GPL drop.
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
next reply other threads:[~2016-02-04 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 0:09 Dave Taht [this message]
2016-02-04 0:25 ` Joel Wirāmu Pauling
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='CAA93jw7JDgXo+-Lb7yBrtNDZ2y+vRF6PiDCRz3vSY=vmN-5_5A@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