[Battlemesh] [FCC] What hardware still works?

cmsv cmsv at wirelesspt.net
Wed Feb 24 22:38:42 CET 2016


Hello guys,

If it helps I am documenting here what is not working and later will
create a page about what is still supported

http://wirelesspt.net/wiki/Firmware_lockdown

cmsv

On 02/23/2016 12:04 PM, Ben West wrote:
> Is JTAG intervention now required?  I had thought I'd read that serial
> console access and/or TFTP recovery mode was sufficient, at least on
> TP-Link products being discussed.  Since we're talking about products
> costing only 50-100USD, I would gather that the amount of effort
> manufacturers are willing to invest in locking the firmware is finite,
> meaning by extension the effort required to work-around such locks
> should also be finite.
> 
> That is, all radio products with firmware presently for sale can have
> their firmware modified, given sufficient effort.  The fact that
> sufficiently determined persons can override countermeasures and mod the
> firmware doesn't appear to endanger their FCC certification.
> 
> Anyway, similar to the hardware compatibility pages on openwrt.org
> <http://openwrt.org>'s wiki, would it make sense to also record in wiki
> the list of working hardware, along with known work-arounds?
> 
> What would be a good venue for such wiki pages?  Any of these?
> 
> https://wiki.openwrt.org/
> http://battlemesh.org/
> https://wirelesspt.net/wiki/P%C3%A1gina_principal
> https://libreplanet.org/wiki/Main_Page
> 
> On Tue, Feb 23, 2016 at 10:23 AM, Philipp Borgers
> <borgers at mi.fu-berlin.de <mailto:borgers at mi.fu-berlin.de>> wrote:
> 
>     On Tue, Feb 23, 2016 at 05:08:52PM +0100, Benjamin Henrion wrote:
>     > On Tue, Feb 23, 2016 at 4:26 PM, Adam Longwill
>     > <adam.longwill at metamesh.org <mailto:adam.longwill at metamesh.org>> wrote:
>     > > We have contracts to fulfill. Can we start a discussion here about what
>     > > hardware still works? What about Ligowave who came to Battlemesh v8? They
>     > > said they gave out unlock codes. Do any of you use them? What hardware are
>     > > you STILL buying that STILL works?
>     > >
>     > > Also, is it possible to use the JTAG interface to reflash a router and erase
>     > > locked down firmware or is it the same as ethernet flashing- I've never done
>     > > it.
>     >
>     > Yes, depends on the SoC, and if the JTAG pins are properly exposed.
>     >
>     > After that, the JTAG software needs to support your flash chip.
>     >
>     > Otherwise, since nowadays most flash chips are SPI ones in SOIC8
>     > format, it is easier to just use a buspirate with a 4x2 clamp hooked
>     > on the chip, and you will be able to reflash it:
>     >
>     > http://www.dhresource.com/0x0s/f2-albu-g1-M00-CA-EB-rBVaGFQ_GG6AHCR0AAEtkRTBPOQ099.jpg/updated-ic-clamp-soic8-sop8-ic-clip-1-adapter.jpg
> 
>     Can someone give a workshop about the tools for flash reading and
>     the process
>     involved?
> 
>     Maybe we can collect some money in advance so everybody can have the
>     right tools
>     at hand?
> 
>     Best Philipp
> 
>     _______________________________________________
>     Battlemesh mailing list
>     Battlemesh at ml.ninux.org <mailto:Battlemesh at ml.ninux.org>
>     http://ml.ninux.org/mailman/listinfo/battlemesh
> 
> 
> 
> 
> -- 
> Ben West
> http://gowasabi.net
> ben at gowasabi.net <mailto:ben at gowasabi.net>
> 314-246-9434
> 
> 
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x15C4B382.asc
Type: application/pgp-keys
Size: 36221 bytes
Desc: not available
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20160224/605d46b8/attachment-0003.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://ml.ninux.org/pipermail/battlemesh/attachments/20160224/605d46b8/attachment-0001.sig>


More information about the Battlemesh mailing list