From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] TP-link archer C5 AC1200 - Still no truth in labeling
Date: Wed, 3 Feb 2016 18:25:04 -0600 [thread overview]
Message-ID: <CAKiAkGR487JxBSwp-=+gKspeftvBDU8+DOUkpV+_fj3PJ1k4Vg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7JDgXo+-Lb7yBrtNDZ2y+vRF6PiDCRz3vSY=vmN-5_5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]
I have half a dozen c7 v2 bought over the last 6 months - they are still
atheros. I have not touched the cheaper c5's
Good to know. Although frustrating however.
On 3 February 2016 at 18:09, Dave Taht <dave.taht@gmail.com> wrote:
> 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
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2551 bytes --]
prev parent reply other threads:[~2016-02-04 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 0:09 Dave Taht
2016-02-04 0:25 ` Joel Wirāmu Pauling [this message]
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='CAKiAkGR487JxBSwp-=+gKspeftvBDU8+DOUkpV+_fj3PJ1k4Vg@mail.gmail.com' \
--to=joel@aenertia.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.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