DSM-G600, DNS-3xx and NSA-220 Hack Forum

i have recompiled the webserver to have home in /mnt/HD_a2/web and run on port 88
http://upit.jtw.dk/dl/uwn/

you still have the old interface left if you fuck anything up and we can compile extra stuff in to the webserver.

If I modified the funplug start scripts to accept "start", "stop" and "status" parameters, do you guys think it's possible to add a "fun-plug'ged services" page that uses the start-scripts to shows service status and start/stop buttons?

@krh
do you've a hint how to start with such a service page? ( dummy alarm )
I've googled the last 2 hours and have no idea where to start.

Is CGI or php needed for this ? Is this only possible under lighttpd or can I use the webs Webserver ?

Last edited by spflug (2007-07-19 00:49:54)

I've already done so.

For example the FTP-Status and the start/stop buttons are called by "<% show_ftp_status();%>" in a file named ftp_settings.asp.

The only file that contains the same string is the compiled file "webs" ( I think the webserver itself ?!?).

I fear to crosscompile that file, cause I've never done that before.

On the other hand we grow with the challenge

spflug wrote:

For example the FTP-Status and the start/stop buttons are called by "<% show_ftp_status();%>" in a file named ftp_settings.asp.
The only file that contains the same string is the compiled file "webs" ( I think the webserver itself ?!?).

I don't know anything about asp, but I was hoping that you can just call shell scripts and generate HTML from an asp page without modifying the web server code. If I understood KRH correctly he's doing stuff like that already.

spflug wrote:

I searched a way to modify the web-interface so I can place a few informations on the start page ( for the moment two links to the mldonkey & twonkyvision webinterface).


Perhaps it's interesting for someone. I'm using the following script:...

spflug, I like your approach. It's similar to the approach I came up with this week. I guess the main difference is that I copy the original pages from flash every time I reboot, whether or not the copies already exist.

KRH wrote:

you still have the old interface left if you fuck anything up and we can compile extra stuff in to the webserver.

So the old webserver can be used as a failsafe? Excellent idea! This will allow us to modify the form actions in web_api.c, recompile webs, and run it in parallel with the old webs. This will allow us to fix the password restrictions (max length 8 chars, no symbol chars) on the server side instead of on the client (i.e. asp) side (for client side fix, see my new asp pages).

The no symbol chars fix can be made right inside web_api.c with just a few lines of code (basically, you just need to replicate how I did it in the asp code). However, the max length 8 chars fix might be a bit trickier (the truncation to 8 characters is done outside of web_api.c, either in busybox code, uClibc code or tinylogin code -- not sure yet).

KRH wrote:

we can not change web_api.c as we miss some of the files included.

Ah, yes, thanks for that tip. I guess these are some of the missing header files?:

#include "../../module/include/wireless.h"
#include "../../module/include/ap.h"
#include "../../module/include/mail.h"

KRH wrote:

but we can make new things just by making a new file and compile it in to webs.

You're quite right. I download the GoAhead source code directly from GoAhead.com and had a look at it. The file web_api.c is not an integral part of GoAhead. Rather, it was an implemented and added on by the NAS vendors. In theory, we should be able to reimplement web_api.c, reusing some parts of the original. It might be tedious to reimplement everything though. Perhaps we could start with a few simple mods. Again, I like your idea of running the stock webs and our custom webs in parallel.

Another important file is the NAS vendor's main.c. It does all of the mapping of form actions to c handler functions with websFormDefine.

This should be a fun way to waste time and make my wife mad and say things like "When are you getting off that stupid computer?" :-)

cyboc wrote:

Again, I like your idea of running the stock webs and our custom webs in parallel.

The bad thing about the stock webs is that it occupies port 80. Also the web interface isn't too great, so I for one wouldn't mind using a complete replacement web interface - based on goahead, lighttpd+lua, picolisp or whatever...

Hi spflug,

is the twonky server running with lighttpd as well, or have you installed an apache for that?

I'm currently running Oxyl under lighttpd on my box - which is perfect for the Pinnacle Showcenter I have right now.
But in the past I've experimented a lot with twonky and might come back to it if I ever change the client hardware.

Cheers,

Emacs

spflug wrote:

Hi
[...]
I've attached a complete package with all changes. Perhaps someone can use it.

Stefan

Hi,

Here's my wishlist for the web interface of my CH3MNAS:

In first place I'm especially interested in putting links to the other webinterfaces (transmission, twonkymedia, ...) on the front page of my CH3MNAS. I've no idea of ASP and therefore I thought your attachment might give me some hints, but I can't find it in this thread. Could you please re-post or PM?

Second I'd like to integrate configuration options for external packages (coming with funplug or the like), that originally don't have any web based configuration (dnsmasq, inadyn, Wake-On-Lan(!), ...), here, too. Most probably I will have to extract those e.g. from "freetz" (a "FritzBox" extension), or does anybody know a better source (I didn't manage to find something deliberately dedicated to funplug)?

Last but not least I'd like to have everything being served on the standard port 80. This is essential if you're often working in environments where all other ports except 80 are being blocked! However, simply reconfiguring the other servers to port 80 does not work because the NAS always takes over and displays it's own webpage. So, is that possible at all? If so, then how?

Thanks
ako673de