[OpenWrt-Devel] Offsets in TP-Link squashfs firmware images

Cristian Morales Vega cristian at samknows.com
Fri Nov 21 07:14:00 EST 2014

Most TP-Link squashfs images are created using mktplinkfw -a 0x4

The "Rootfs data offset" in the header of those images is 0x00100000. But
the rootfs actually starts at "Kernel data offset" + "Kernel data length".
As a result when extracting the rootfs with "mktplinkfw -x -i" the result
is broken.

Bug or feature? Maybe the firmware header is checked by something that
expects the "Rootfs data offset" value to be wrong? If so, could the real
offset be stored somewhere else so "mktplinkfw -x -i" can do its work?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20141121/ca0855d9/attachment.htm>
-------------- next part --------------
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list