[Battlemesh] TP-Link TL-WR1043ND v3 flashed to OpenWRT trunk via TFTP
adam.longwill at gmail.com
Wed Mar 16 02:01:33 CET 2016
Aw dang. Mine worked. Must have been old. Nevermind.
On Mar 15, 2016 8:40 PM, "Adam Longwill" <adam.longwill at metamesh.org> wrote:
> You must have an older version of this hardware or something. I have
> personal experience with the 3600 the image is requested from that address,
> a response is sent from .66 but the the request packet comes across the
> wire again and again.
> I actually have a brand new in box 3600,in my car. Perhaps I could test
> this tonight.
> On Mar 15, 2016 8:29 PM, "Ben West" <ben at gowasabi.net> wrote:
>> Following up from a couple requests made here on the list about a
>> suitable venue/wiki to start recording verified techniques for flashing
>> devices with countermeasures.
>> TP-Link TL-WR1043ND v3.0 (purchased from Newegg this month)
>> Stock firmware: 3.16.9 Build 151021 Rel.74655n
>> The web UI refused OpenWRT factory image on "version of the upgraded file
>> was incorrect."
>> However, a TFTP server at 192.168.0.66, with the OpenWRT trunk factory
>> image for this device under the name "wr1043v3_tp_recovery.bin" in TFTP
>> server root, did work. Specifically, I held down the reset button, powered
>> on, and then released the reset button after ~20sec.
>> No modification to the OpenWRT trunk factory image was done.
>> Again, good venue for recording these details (candidates listed below)?
>> These details are scattered everywhere on the Internets, but having
>> attention focused here could help consolidate things.
>> Hope this helps.
>> Ben West
>> ben at gowasabi.net
>> Battlemesh mailing list
>> Battlemesh at ml.ninux.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Battlemesh