Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Wed Nov 26, 2014 1:28 am

All times are UTC [ DST ]




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: Mon Dec 27, 2010 9:42 pm 
Offline
Newbie
User avatar

Joined: Fri Dec 03, 2010 6:22 am
Posts: 9
Location: Atlanta, GA USA
I am trying to replace the webaxs stuff with an ordinary web server, i.e. listens on port 80 and serves index.html.

This is on a mostly-stock Linkstation Pro Duo LS-WTGL/R1-V3 running Buffalo's 3.10 firmware. I've opened it with acp_commander and installed dnsmasq, but have done very little else.

The 3.10 firmware uses Apache for the configuration interface. I've moved that to port 8000 by adding a "Listen 8000" line to httpd.conf, and that works and survives restarting.

I've built a custom lighttpd.conf (with a different name) and changed webaxs.sh to use the new config file. When lighttpd is started using webaxs.sh, it listens on port 80 and serves the index.html file I've placed in the document root. However, when the Linkstation is restarted, lighttpd is back on port 9000 and serves Buffalo's Webaxs file list page. In other words, it appears to have been started with the original config file.

Edit: It appears that some, perhaps all, configuration changes made using the Web interface also restart lighty using the original configuration. Grepping in www doesn't find anything, either. (Edit added 2010-12-29.)

Checking rcS finds no reference to webaxs.sh. That's no surprise, because if rdS were running webaxs.sh, it would be using my configuration file. (Webaxs.sh is not getting overwritten/rebuilt on restart.) No amount of grepping finds any reference to lighttpd other than in webaxs.sh.

I am stumped! Does anyone know how Lighty gets started on boot under Version 3 (3.10) firmware?


Top
 Profile  
 
PostPosted: Wed Dec 29, 2010 8:11 pm 
Offline
Newbie
User avatar

Joined: Fri Dec 03, 2010 6:22 am
Posts: 9
Location: Atlanta, GA USA
Well, I found it. Sort-of. /modules/webaxs/www/cgi-bin/module contains seven perl modules that "do stuff" with webaxs. I could slog through them, but they sure look complicated. (At least the comments are in English; they appear to be in Japanese in other sections of the code.)

I think I'm going to punt and try a different approach: Turn Web Access off using the configurator, make a new lighttpd.conf in /opt, make a lighttpd.sh to start lighttpd and call if from rdS. I'm thinking that, even if someone turns Web Access back on, all will be OK. There will be two instances of lighty running, but on different ports. There might be problems with mutexs, but no one but me is likely to use the web interface, especially since it's moved to port 8000.


Top
 Profile  
 
PostPosted: Sat Jan 01, 2011 9:14 pm 
Offline
Newbie
User avatar

Joined: Fri Dec 03, 2010 6:22 am
Posts: 9
Location: Atlanta, GA USA
OK... so I'm talking to myself. But I did get this to work, so maybe this will help someone else.

I...
  • Moved Apache to port 8000 by adding a "Listen 8000" line to httpd.conf
  • Turned off Web Access using the Buffalo web configuration interface.
  • Thought about renaming /etc/init.d/webaxs/sh but decided that was useless.
  • Created a very cut down lighttpd.conf in /opt/local/lib; used port 80 and changed document root.
  • Built a lighttpd.sh in /etc/init.d by copying and modifying sshd.sh
  • Added lighttpd.sh to rcS. For some reason, lighttpd would not start if added to Step 3 or Step 4 lists, so I just added it at the bottom of rcS.

I now have a local "traditional" web server that survives reboots and configuration changes.

I also added an "internal" hosts record to allow the internal web server to be reached by the name "internal."


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC [ DST ]


Who is online

Users browsing this forum: Google [Bot] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:

Protected by Anti-Spam ACP
Protected by Anti-Spam ACP Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group