Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extract Firmware - WebGui Edit #9

Closed
GoogleCodeExporter opened this issue Nov 1, 2015 · 2 comments
Closed

Extract Firmware - WebGui Edit #9

GoogleCodeExporter opened this issue Nov 1, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Cant find to edit the GUI pages or it is not extracted


What is the expected output? What do you see instead?
Everything runs fine

What version of the product are you using? On what operating system?
Ubuntu 

Please provide any additional information below.

Everything is extracted/build correctly, I dont know were to go now after
extrating the firmware (never extrated ddwrt before), my guess is that 1mb
file on
/root/ddwrt/firmware-mod-kit-read-only/trunk/firm/image_parts/squashfs-lzma-imag
e-3_0
is an lzma file, do I add the extension .lzm and attempt to extract it ?

Original issue reported on code.google.com by ad...@athacks.com on 5 Dec 2009 at 5:57

@GoogleCodeExporter
Copy link
Author

If everything ran fine, the squashfs image was properly extracted and you 
shouldn't need to extract it manually. You can't find the Web pages because 
they are actually compiled into the httpd binary in DD-WRT. Don't ask me why.

Original comment by heffne...@gmail.com on 29 Aug 2011 at 11:54

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

Since hffnercj is too polite to say why the web pages are compiled into the 
httpd binary, I will: The reason why is because Brainslayer claimed the web UI 
as 'his' and made it closed source, despite the fact that it is a GPL 
derivative work from the original Broadcom->Linksys->Sveasoft line. This 
protects DD-WRT's web UI from modification. For a long time after the initial 
development of the FMK, he kept initially breaking compatibility of the 
squashfs signature as well, to prevent use of the FMK. Go ask him why ;)

Original comment by jeremy.collake@gmail.com on 30 Aug 2011 at 12:39

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant