I noticed the answer to many of my various confusions when I looked at the rest of the files in your respository...
Yet, I see no mention of those other files anywhere (release/src/Makefile, cy_conf.* etc..). I feel like a missed a day of school and there is a doc I keep stepping over?
I am one step closer to enlightenment now...
So, to be clear, it seems one needs to "patch" all the files which appear in the "trunk" of the svn respository...
This will, among other things, include openvpn, bird and make the mods needed to insert the default openvpn settings and enable telnet...
/mike
howto for the howto so far...
Getting close to being able to build from source, here is what I have so far (please, please correct me if I am wrong... ):
Step 1 - realize that there are quite a few more edits than described (in the documentation: http://cmeerw.org/dev/node/view/97) to the default linksys release and they are VERY important ;-)
Go grab the whole repository:
svn co http://svn.cmeerw.net/src/wrt54g wrt54g
Step 2 - realize that it would seem that a build from "make clean" will not work - still not quite sure why, but I run into undefined symbols in broadcom.o while trying to compile httpd (release/src/router/httpd)...
short version: until you understand why these sources would not build from clean - don't do a clean anywhere that it is not needed.. Then take some time later to understand why httpd cannot build and let us all know.
Step 3 - with that in mind, go grab/resolve all the diffs you find in:
<wrtg54g>/trunk
where <wrtg54g> is wherever you did the "svn" command...
You should see among other things that
cy_conf.h
cy_conf.mak
router/Makefile
misc/rootprep.sh
.... (and so on)
All have edits relative to the linksys source... Once you grab the whole tree it is pretty obvious that these are all the edited files to do the full build and answer my questions regarding getting from "A" to "B" (with B being compiled with openvpn added to the .bin and A being baffled and confused as to how the cmeerw.bin was created from the description in the docs - not that I am not eternally gratefull for the effort so far - I just appearently need more hand-holding :-) )....
If this was explained in a doc somewhere, please feel free to flame/label me an idiot, but kindly point me to the doc as you do to maximize the public shaming (and get me the docs I so badly need :-) - I am not too proud to beg....
Hopefully more to come soon after I figure out where ".symbols" went while compiling src/router/lib...
/mike
missing httpd files
IIRC there are indeed a few files missing in the original Linksys firmware source code in that version...
arg, I had come to that con
arg, I had come to that conclusion after some light reading...
How did you get around that?
Thanks,
/mike
missing httpd files
The latest Linksys firmware now provides the full httpd source code again.
missing source
Great (I assume this is athe 3.x I saw the last time I looked there?)
openvpn is working great, thanks again...
Now, if I had the time to figure out how to edit the the .asp forms they are using... Managed to add graphic for things like telnet enable/disable (which BTW, the default setup appears to allow telnet in from anywhere! - make sure you edit those firewall rules to keep it local!)
However, after copying the upnp_enable section of the Management.asp and changing it to telnetd_enable, I discovered there is a missing piece of the puzzle in terms of the "form" they are submitting... That is, even though I have added a section to set telnetd_enable, the "submit" for the Management.asp page does not seem to respect this (it always comes back and tells me the telnetd_enable state is as it was before the "submit"
Anyone have a good pointer/discussion/doc to decoding this? It would be great to get this to the next level of configurability from the GUI... I just have not had the time to udnerstand the structure of their forms/javascript...
Thanks,
/mike
missing documentation page
Seems I have forgotten to describe these steps in the documentation: see http://cmeerw.org/dev/book/view/135
:-) On behalf of all of us
:-) On behalf of all of us anoying, blundering, fat fingered, weekend hacking, don't really have time to play with this stuff, but do anyway and know just enough to be dangerous users out there... Thanks...
/mike
I'm still "Having Fun"
Can you email me--I'm having issues that you've gotten past--I can make the generic LINKSYS image, but walking through the steps here, I have a problem with the uCLIBC part. I skipped over the step that has me stopped, and did all other steps, and am stuck on the final make--so I have to get the uCLIBc to work.
Did you notice anything about the uCLIBc steps that may be misdocumented in Chris' excellent documentation (that I'm just being too dense to catch what I'm doing wrong)?
Any help you may have would be appreciated.
/Tom
tomj@id-company.net