<div dir="ltr"><div>Hey all,<br><br>If anyone has a locked out wdr3600 this firmware should unlock it so you can <br></div><div>make it usable again. Found it <a href="https://www.dd-wrt.com/phpBB2/viewtopic.php?p=1002758&sid=aa94262340c3299225dc0416f8ec37a3">here</a><br><br></div><div>Happy Flashin!<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 18, 2016 at 3:10 PM, Dan Staples <span dir="ltr"><<a href="mailto:dan@disman.tl" target="_blank">dan@disman.tl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Apologies, I posted the wrong link for the first footnote of my previous<br>
email: <a href="http://wiki.openwrt.org/toh/tp-link/archer-c5-c7-wdr7500" rel="noreferrer" target="_blank">http://wiki.openwrt.org/toh/tp-link/archer-c5-c7-wdr7500</a><br>
<div class="HOEnZb"><div class="h5"><br>
On 02/18/2016 03:09 PM, Dan Staples wrote:<br>
> That is very disappointing. Thanks for asking one of their reps, Adam.<br>
><br>
> It seems like the hairsplitting comes down to the question of whether<br>
> TP-Link started locking down their firmware before the FCC proposed<br>
> rulemaking came out. If they did, then it implies a possibly different<br>
> motivation than simply preemptively complying with regulations.<br>
><br>
> The only reference I read to the first reported locked out TP-Link<br>
> firmware is Archer C7 v2 151014 US, from OpenWRT wiki[1]. Assuming this<br>
> firmware build is from Oct 14, 2015 (rather than Oct 15, 2014), this is<br>
> *after* the proposed rulemaking was published by the FCC (July 21,<br>
> 2015)[2]. But maybe I'm reading the date wrong...<br>
><br>
> Dan<br>
><br>
><br>
> [1]<br>
> <a href="https://www.fcc.gov/news-events/blog/2015/11/12/clearing-air-wi-fi-software-updates" rel="noreferrer" target="_blank">https://www.fcc.gov/news-events/blog/2015/11/12/clearing-air-wi-fi-software-updates</a><br>
> [2] <a href="https://apps.fcc.gov/edocs_public/attachmatch/FCC-15-92A1.pdf" rel="noreferrer" target="_blank">https://apps.fcc.gov/edocs_public/attachmatch/FCC-15-92A1.pdf</a><br>
><br>
> On 02/18/2016 02:45 PM, Ben West wrote:<br>
>> Adam, thanks for chiming in, especially since it was your chat with<br>
>> TP-Link tech support.<br>
>><br>
>> The hair-splitting I saw was at venues like <a href="http://news.ycombinator.org" rel="noreferrer" target="_blank">news.ycombinator.org</a><br>
>> <<a href="http://news.ycombinator.org" rel="noreferrer" target="_blank">http://news.ycombinator.org</a>>, not on listservs we likely are both<br>
>> subscribed to, and should say found such quibbles trivial. TP-Link<br>
>> clearly was motivated by proposed FCC rulemaking, although they may<br>
>> indeed have their own motivations at the same time.<br>
>><br>
>> The specific detail that they're locking down 2.4GHz products too was<br>
>> quite galling; no FCC actions pertain to those devices. So, either<br>
>> their products share enough of the same firmware tree that inexpensively<br>
>> placing locks on one product necessitates placing locks on all products,<br>
>> or TP-Link is mindfully wanting to lock out 3rd party firmware. (Sadly,<br>
>> not the first time this sequence of events has run its course, cf.<br>
>> history with Meraki.)<br>
>><br>
>><br>
>> On Thu, Feb 18, 2016 at 1:36 PM, Adam Longwill<br>
>> <<a href="mailto:adam.longwill@metamesh.org">adam.longwill@metamesh.org</a> <mailto:<a href="mailto:adam.longwill@metamesh.org">adam.longwill@metamesh.org</a>>> wrote:<br>
>><br>
>> Ben, unfortunately there is no hair-splitting according to the chat<br>
>> record I have pasted below from 2 days ago. TP-Link is locking down<br>
>> all devices due to FCC regulations.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Chat transcript<br>
>><br>
>><br>
>><br>
>><br>
>> *Name:* Adam Longwill<br>
>><br>
>> *E-mail:* <a href="mailto:adam.longwill@metamesh.org">adam.longwill@metamesh.org</a> <mailto:<a href="mailto:adam.longwill@metamesh.org">adam.longwill@metamesh.org</a>><br>
>><br>
>> *Choose Product Category:* Wireless Router<br>
>><br>
>> *Please Describe Your Model No. and Problem* WDR3600<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Camille Tue, 02/16/16 09:05:00 pm America/New_York<br>
>><br>
>> Hello. How may I help you?<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Adam Longwill 09:05:15 pm<br>
>><br>
>> I cannot view my support tickets<br>
>> my support tickets were closed because I could not view or reply to them<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Camille 09:05:34 pm<br>
>><br>
>> may I have the ticket number?<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Adam Longwill 09:05:34 pm<br>
>><br>
>> and my original support issues were not resolved.<br>
>> I wish I knew- but because the support site is broken I have to<br>
>> check my e-mail.<br>
>> 194265 is one<br>
>> 195288 is the other regarding your broken site<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Camille 09:07:07 pm<br>
>><br>
>> regarding ticket issue, please follow steps below to have a try<br>
>> 1. Make sure you have clean up all the history of the web browser.<br>
>> 2. Please try different computers and web browser.Did you have the<br>
>> same problem? 3. Try to refresh by pressing the Ctrl+F5. 4. What is<br>
>> the operating system and version of your computers? Is that 32bit or<br>
>> 64bit? 5. What is the version of the web browser you have tried?<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Adam Longwill 09:08:24 pm<br>
>><br>
>> I have tried multiple computers multiple browsers, and cleared cookies<br>
>> I'm using Chrome current and have tried firefox and IE<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Camille 09:09:12 pm<br>
>><br>
>> did you clear history of web browser?<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Adam Longwill 09:09:17 pm<br>
>><br>
>> yes<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Camille 09:09:36 pm<br>
>><br>
>> OK<br>
>> Dear Adam, Many thanks for your valuable reply. If you cannot<br>
>> replace the firmware with a third party firmware, then please try to<br>
>> downgrade the firmware to the older version to see whether it can<br>
>> work. Sorry that we don't have the information about the unlocked<br>
>> firmware. This has to be tried by yourself. Sorry again for the<br>
>> inconvenience caused and your great cooperation & Patience will be<br>
>> highly appreciated.<br>
>> this is my colleague reply<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Adam Longwill 09:10:01 pm<br>
>><br>
>> downgrading does not work<br>
>> I get an 18005 errror<br>
>> upon attempting to downgrade<br>
>> I want to know if this is because of the FCC's rules regarding<br>
>> broadcast strength and DFS control. Has TP-Link complied with these<br>
>> rules and locked down its firmware and if so, for what models<br>
>> I need to know if I am going to continue purchasing devices from you.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Camille 09:13:25 pm<br>
>><br>
>> wait one moment please<br>
>> Thanks for your waiting, right now only these products has<br>
>> limitation on firmware: Archer C7 V2 Archer C1900 V1 Touch P5 V1<br>
>> Archer C2600 V1 Archer C3200 V1 Archer C2 V1 Archer C5 V2 Archer C8<br>
>> V1 Archer C9 V1 TL-WR841N V11 TL-WDR3500 V1 TL-WR940N V3.0<br>
>> TL-WR1043ND V3.0 TL-WR710N(USA) TL-WR841N V9.0<br>
>> and all products will also limite firmware in the future.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Adam Longwill 09:26:19 pm<br>
>><br>
>> Wow. Thank you. I'm impressed with your digging<br>
>> And this limitation is due to FCC rule clarifications in 2015?<br>
>> And not some other reason<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Camille 09:28:15 pm<br>
>><br>
>> Right, due to FCC<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Adam Longwill 09:28:50 pm<br>
>><br>
>> Thank you very much. Can you explain why the WDR3600 appears to be<br>
>> locked down? Is it possible that your list is not totally updated?<br>
>> And do you have a method or avenue that people who wish to use other<br>
>> firmware have?<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Camille 09:34:02 pm<br>
>><br>
>> Yes, wdr3600 as dual band wifi router, is also locked down. And<br>
>> there is no other way to use other firmware. Sorry for that<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Adam Longwill 09:34:19 pm<br>
>><br>
>> Thank you very much, Camille. You've been very helpful.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Duration: 29m 32s<br>
>><br>
>> Chat started<br>
>> on: <a href="http://www.tp-link.us/support-contact.html#Hotline-Support" rel="noreferrer" target="_blank">http://www.tp-link.us/support-contact.html#Hotline-Support</a><br>
>> <<a href="http://www.tp-link.us/support-contact.html#Hotline-Support" rel="noreferrer" target="_blank">http://www.tp-link.us/support-contact.html#Hotline-Support</a>><br>
>> Referrer: <a href="http://www.tp-link.us/" rel="noreferrer" target="_blank">http://www.tp-link.us/</a> <<a href="http://www.tp-link.us/" rel="noreferrer" target="_blank">http://www.tp-link.us/</a>><br>
>> Visitor geolocation: Pittsburgh, Pennsylvania, United States /<br>
>> 96.89.42.102<br>
>> Chat group: US<br>
>><br>
>> <<a href="http://twitter.com/LiveChat" rel="noreferrer" target="_blank">http://twitter.com/LiveChat</a>> <<a href="http://facebook.com/LiveChat" rel="noreferrer" target="_blank">http://facebook.com/LiveChat</a>><br>
>><br>
>> E-mail from LiveChat<br>
>> <<a href="http://www.livechatinc.com/?utm_source=livechat&utm_medium=email&utm_campaign=chat_transcript" rel="noreferrer" target="_blank">http://www.livechatinc.com/?utm_source=livechat&utm_medium=email&utm_campaign=chat_transcript</a>><br>
>><br>
>><br>
>><br>
>><br>
>> On Thu, Feb 18, 2016 at 11:10 AM, Ben West <<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a><br>
>> <mailto:<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>>> wrote:<br>
>><br>
>> Presently, Commotion is being built for TP-Link WDR3600 and<br>
>> WDR4300, among others.<br>
>> <a href="https://commotionwireless.net/docs/guides-howtos/recommended-hardware/" rel="noreferrer" target="_blank">https://commotionwireless.net/docs/guides-howtos/recommended-hardware/</a><br>
>> <a href="https://commotionwireless.net/download/routers/" rel="noreferrer" target="_blank">https://commotionwireless.net/download/routers/</a><br>
>><br>
>> Please be advised people have confirmed these very TP-Link<br>
>> products and plenty others are now appearing in the field with<br>
>> 3rd-party firmware upgrade locked out. I.e. Commotion's install<br>
>> instructions will no longer work.<br>
>><br>
>> The particular conversation with the TP-Link support rep quoted<br>
>> below also mentions 2.4GHz products being locked too, with FCC<br>
>> rulemaking cited as (incorrect) reason.<br>
>><br>
>> <a href="http://ml.ninux.org/pipermail/battlemesh/2016-February/004379.html" rel="noreferrer" target="_blank">http://ml.ninux.org/pipermail/battlemesh/2016-February/004379.html</a><br>
>> <a href="https://news.ycombinator.com/item?id=11122966" rel="noreferrer" target="_blank">https://news.ycombinator.com/item?id=11122966</a><br>
>> <a href="https://www.reddit.com/r/linux/comments/46c0t0/tplink_begins_router_lockdown_due_to_fcc_proposed/" rel="noreferrer" target="_blank">https://www.reddit.com/r/linux/comments/46c0t0/tplink_begins_router_lockdown_due_to_fcc_proposed/</a><br>
>> <a href="https://www.gofundme.com/save_wifi_round_2" rel="noreferrer" target="_blank">https://www.gofundme.com/save_wifi_round_2</a> (funding campaign<br>
>> started in response)<br>
>><br>
>> I read some hair-splitting about whether TP-Link started doing<br>
>> this in response to the FCC proposed rulemaking re: 5.8GHz<br>
>> operation, or whether they had their own reasons.<br>
>><br>
>> Precise details of the lockdown are still sketchy, but it looks<br>
>> like a serial console is needed to override it.<br>
>><br>
>> --<br>
>> Ben West<br>
>> <a href="http://gowasabi.net" rel="noreferrer" target="_blank">http://gowasabi.net</a><br>
>> <a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a> <mailto:<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>><br>
>> <a href="tel:314-246-9434" value="+13142469434">314-246-9434</a> <tel:<a href="tel:314-246-9434" value="+13142469434">314-246-9434</a>><br>
>><br>
>> _______________________________________________<br>
>> Commotion-discuss mailing list<br>
>> <a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a><br>
>> <mailto:<a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a>><br>
>> <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Commotion-discuss mailing list<br>
>> <a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a><br>
>> <mailto:<a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a>><br>
>> <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Ben West<br>
>> <a href="http://gowasabi.net" rel="noreferrer" target="_blank">http://gowasabi.net</a><br>
>> <a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a> <mailto:<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>><br>
>> <a href="tel:314-246-9434" value="+13142469434">314-246-9434</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Commotion-discuss mailing list<br>
>> <a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a><br>
>> <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
>><br>
><br>
<br>
--<br>
<a href="https://disman.tl" rel="noreferrer" target="_blank">https://disman.tl</a><br>
OpenPGP key: <a href="http://disman.tl/pgp.asc" rel="noreferrer" target="_blank">http://disman.tl/pgp.asc</a><br>
Fingerprint: 2480 095D 4B16 436F 35AB 7305 F670 74ED BD86 43A9<br>
_______________________________________________<br>
Commotion-discuss mailing list<br>
<a href="mailto:Commotion-discuss@lists.chambana.net">Commotion-discuss@lists.chambana.net</a><br>
<a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" rel="noreferrer" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Allied Media Projects<br>Detroit Digital Justice Coalition<br><br></div>
</div>