From: Eric Johansson <esj@eggo.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] archer c7v2 gets third party unupgradable firmware
Date: Sun, 14 Feb 2016 16:25:02 -0500 [thread overview]
Message-ID: <56C0F0AE.3000804@eggo.org> (raw)
In-Reply-To: <56C0C6E3.6000700@taht.net>
wdr3600 will soon be on the can't upgrade list. The first one I bought I
made the mistake of following the open WRT instructions to upgrade to
the current firmware which contained a lockout code. Working with with
folks on the WRT IRC channel I was able to produce a flash image which
had the image preamble that made it possible to bypass the lockout image
and install openwrt.
The preamble was something like 207 bytes long but don't quote me on the
exact length. I think I still have it somewhere on my Linux partition if
you are interested.
On 2/14/2016 1:26 PM, Dave Täht wrote:
> 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.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2016-02-14 21:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 18:26 Dave Täht
2016-02-14 19:21 ` Michael Richardson
2016-02-14 21:25 ` Eric Johansson [this message]
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=56C0F0AE.3000804@eggo.org \
--to=esj@eggo.org \
--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