Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Dave Täht" <dave@taht.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] archer c7v2 gets third party unupgradable firmware
Date: Sun, 14 Feb 2016 10:26:43 -0800	[thread overview]
Message-ID: <56C0C6E3.6000700@taht.net> (raw)

A pithy note on
https://wiki.openwrt.org/toh/tp-link/archer-c5-c7-wdr7500 - it contains
a bitter "thank you" to the FCC - you can't upgrade the firmware to a
third party anymore.

I can confirm this - the archer c7v2 I got off of amazon last week has
firmware 3.14.3, and will not take a web upload of openwrt no matter
what I tried. I also failed to get a tftp upload to work (but did not
try hard enough).

So this rules out the netgear wndr 4300, and tp-link archer c7v2 for
future development efforts by the bufferbloat effort.

It's too bad - the cake qdisc is back at a "nearly ready" state and
could use some performance testing and optimization on these lower end
platforms, and I'd like to get make-wifi-fast off the ground.

I guess it would be good to collect a list of those companies that are
engaging in whole router firmware lockdown instead of just lockdown on
the radio, so we can avoid them in the future.

             reply	other threads:[~2016-02-14 18:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 18:26 Dave Täht [this message]
2016-02-14 19:21 ` Michael Richardson
2016-02-14 21:25 ` Eric Johansson
2016-02-15  0:46 ` Rich Brown
2016-02-15 16:11   ` dpreed
2016-02-15 18:38     ` [Cerowrt-devel] nuc stuff Dave Täht
2016-02-15 19:25       ` Outback Dingo
2016-03-27  1:01         ` Valent Turkovic
2016-03-27 16:48           ` Dave Taht
2016-03-28  1:45           ` Outback Dingo
2016-03-28  1:51             ` David Lang
2016-03-28  1:54               ` Outback Dingo
2016-03-28  2:04                 ` Outback Dingo
2016-02-16  2:35     ` [Cerowrt-devel] archer c7v2 gets third party unupgradable firmware Matt Taggart

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=56C0C6E3.6000700@taht.net \
    --to=dave@taht.net \
    --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