<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Hi again Ben!</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Thank you so much for your reply</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Ok I see. However we might have a glimpse of hope with this little suggestion I found on the TOH:</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">
<h2 id="how_to_flash_chaos_calmer_1505_into_the_v3_version_with_the_v2_openwrt_factory_file" class="sectionedit71">How to flash Chaos Calmer (15.05) into the V3 version with the V2 OpenWRT factory file</h2>
<div class="level2">
<p>Since there is another TP-Link software installed on the V3 version of the router which does not accept the firmware file for the V2 version it is not possible to install CC on it.<br />But there is a little trick to install it anyways.</p>
<ol>
<li class="level1">
<div class="li">Download the V2 version:<a class="urlextern" title="https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/openwrt-15.05-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin" href="https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/openwrt-15.05-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin" rel="nofollow">https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/openwrt-15.05-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin</a></div>
</li>
<li class="level1">
<div class="li">Change with an Hex editor the version number in the header of the file from 02 to 03 and save the file. It is located in byte 43.<br /><a class="media" title="media:tplink:tl-wr1043:tl-wr1043nd_version_nr_in_bin_header.jpg" href="https://wiki.openwrt.org/_detail/media/tplink/tl-wr1043/tl-wr1043nd_version_nr_in_bin_header.jpg?id=toh%3Atp-link%3Atl-wr1043nd"><img class="media" src="https://wiki.openwrt.org/_media/media/tplink/tl-wr1043/tl-wr1043nd_version_nr_in_bin_header.jpg?w=200&tok=43d6aa" alt="" width="200" /></a> <br />command-line version for linux:
<pre class="code"> echo -e "\003" | dd seek=67 bs=1 count=1 conv=notrunc of=firmware_file.bin</pre>
</div>
</li>
<li class="level1">
<div class="li">Rename the file to "wr1043v3_tp_recovery.bin" and flash it via tftp how described above</div>
</li>
</ol>
</div>
</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Would this trick solve the issue even for the commotion firmware? If so, how would I compile it?</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Thank you so much! Fingers crossed! :)</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Nicolas</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">On 2016-08-15 20:50, Ben West wrote:
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">I've compiled OpenWRT trunk r49379 for the TL-WR1043N v3. My<br /> understanding is that a trunk version is required for this device,<br /> i.e. can't flash it with BB or CC.<br /> <br /> From prior experience compiling Commotion atop r3xxxx-era OpenWRT, I'd<br /> anticipate these specific difficulties:<br /> <br /> - Compiling Commotion's luci packages atop recent OpenWRT trunk. I<br /> think there is significant enough delta in the OpenWRT luci repo that<br /> current revisions won't compile cleanly with Commotion.<br /> - Compiling Commotion's olsr packages atop olsrd v0.9, which is now<br /> the version packaged with OpenWRT trunk. Similar situation.<br /> - Dealing with Commotion libcyassl dependencies, since that package<br /> appears to be gradually phasing out in favor of libpolarssl as<br /> lightweight alternative to libopenssl.<br /> <br /> Please note I can't offer availability in addressing these barriers to<br /> a clean compile, just sharing experience to help guide others.<br /> <br /> On Sun, Aug 14, 2016 at 6:22 PM, Nicolas North <<a href="mailto:star@nikksno.io">star@nikksno.io</a>><br /> wrote:<br /> <br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Hi there!<br /> <br /> I'm starting a mesh network project here in Milano, Italia, where I<br /> live, and I already have 40 nodes up and running both outside and<br /> inside<br /> peoples' houses, with both commotion and a pure openwrt + olsrd<br /> setup as<br /> described on the Metamesh website. I intend to switch to a 100%<br /> commotion network because of some potentially show stopping issues<br /> I'm<br /> encountering on Tplink routers with Metamesh's setup [I'm doing<br /> something wrong I'm sure - more details below].<br /> <br /> I WOULD IMMENSELY APPRECIATE ANY HELP IN GETTING COMMOTION COMPILED<br /> FOR THE TP-LINK TL-WR1043N/ND V3 AND IF POSSIBLE THE TP-LINK ARCHER<br /> C7 V2 [WHICH IS DUAL BAND AC SO I ONLY HAVE TWO OF THEM AS A TEST<br /> FOR NOW].<br /> <br /> In the past I was able to compile openwrt on a linux<br /> vm with a lot of trial and error but was never able to access the<br /> command line config menu for the commotion compiler. I also ran into<br /> svn<br /> tutorials for commotion but only ever found git repos. Also I don't<br /> know<br /> the specs to compile for my speficic hardware, are those available<br /> on<br /> the owrt toh? How can I avoid using the trunk version of openwrt if<br /> there's no stable version listed for the WR1043N/ND v3? I have very<br /> little experience with software compilation so<br /> any help would be fantastic.<br /> <br /> I've had a very lengthy back and forth conversation that started<br /> here on<br /> the list and then went private with Josh and Ben and Adam over at<br /> Metamesh who have all been extremely nice and helpful and I thank<br /> them<br /> if the project is where it is today. But now I need your help in<br /> ensuring this doesn't all just collapse in front of us because of<br /> these<br /> issues. For the record, Metamesh is amazing, Adam, has been great,<br /> and<br /> I'm sure their setup works, and I'm doing something wrong, but after<br /> reading Josh's message about the future of commotion, I want all my<br /> nodes on commotion for the future of the project.<br /> <br /> ANY HELP IS OF VITAL IMPORTANTANCE FOR OUR PROJECT. ABOUT 100 PEOPLE<br /> ARE<br /> WAITING FOR THIS TO WORK EVERY DAY. PLEASE HELP. THANK YOU VERY<br /> MUCH IN ADVANCE.<br /> <br /> Nicolas<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" target="_blank" rel="noreferrer">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a> [<a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" target="_blank" rel="noreferrer">1</a>]</blockquote>
<br /> <span class="sig">-- <br /> <br /> Ben West<br /> <a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a><br /> <br /> <br /> Links:<br /> ------<br /> [1] <a href="https://lists.chambana.net/mailman/listinfo/commotion-discuss" target="_blank" rel="noreferrer">https://lists.chambana.net/mailman/listinfo/commotion-discuss</a></span></blockquote>
</div>
</body></html>