From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [IPv6:2a01:7e00::f03c:91ff:feae:7028]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id C92633B2BC for ; Sun, 14 Feb 2016 13:23:14 -0500 (EST) Received: from dair-1314.lan (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id C97D42130C for ; Sun, 14 Feb 2016 18:23:13 +0000 (UTC) To: cerowrt-devel@lists.bufferbloat.net From: =?UTF-8?Q?Dave_T=c3=a4ht?= X-Enigmail-Draft-Status: N1110 Message-ID: <56C0C6E3.6000700@taht.net> Date: Sun, 14 Feb 2016 10:26:43 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: [Cerowrt-devel] archer c7v2 gets third party unupgradable firmware X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Feb 2016 18:23:14 -0000 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.