Host web page from NSA 220+

Marvell Orion based
remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Sat Mar 12, 2011 6:52 pm

Code: Select all

Some logfile administration...
Script usb_key_func.sh version 20101109 running from /mnt/parnerkey
ffpstick started at Sat Mar 12 15:43:54 GMT 2011
Try to determine NAS type...
Type NSA220, fw 230+
Find the current usb device...
Current usb device is /dev/sdb1
Check for filesystem...
Filesystem is vfat
Check /dev/sdb for number of partitions...
/dev/sdb has 2 partitions
Copy myself to /tmp...
And execute...
/tmp/usb_key_func.sh background_polling /dev/sdb1 NSA220 "230+" &
Script usb_key_func.sh version 20101109 running from /tmp
Wait for the stick to be mounted again by the firmware...
Probe all mount points 000 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 010 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 020 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
found ffpstick on /e-data/4D7B-9045, moving logfile
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 030 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 040 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 050 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
30 seconds should be enough for anybody ;)
Will try to mount ffproot myself
mount: you must specify the filesystem type
Probe all mount points 060 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 070 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 080 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 090 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 100 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 110 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 120 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 130 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 140 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 150 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 160 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 170 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 180 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 190 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 200 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 210 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 220 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 230 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 240 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 250 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 260 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 270 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 280 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 290 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 300 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 310 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 320 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found
Probe all mount points 330 seconds...
probe /proc/bus/usb...
probe /lib/security...
probe /lib/modules...
probe /usr/local/etc...
probe /usr/local/var...
probe /usr/local/dmsf...
probe /etc/zyxel...
probe /i-data/4cddb05c...
probe /e-data/4D7B-9045...
probe /usr/local/zy-pkgs...
probe /etc/zyxel/zy-pkgs...
probe /usr/local/apache/htdocs/pkg...
No /anymountpoint/ffproot/after_booting.sh found


Mijzelf
Posts: 6207
Joined: Mon Jun 16, 2008 10:45 am

Re: Host web page from NSA 220+

Post by Mijzelf » Sat Mar 12, 2011 7:24 pm

Yes, this is the original logfile, it doesn't zip it's predecessor. But the stick already had 2 partitions (Check /dev/sdb for number of partitions... /dev/sdb has 2 partitions), so the script doesn't install FFP, as it assumes it's already there.
Do you have any idea why it has two partitions? Is it a new stick?

(BTW, is it right that you have only one disk in your NAS?)

remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Sat Mar 12, 2011 8:10 pm

Mijzelf wrote:Yes, this is the original logfile, it doesn't zip it's predecessor. But the stick already had 2 partitions (Check /dev/sdb for number of partitions... /dev/sdb has 2 partitions), so the script doesn't install FFP, as it assumes it's already there.
Do you have any idea why it has two partitions? Is it a new stick?

(BTW, is it right that you have only one disk in your NAS?)
I have now repartitioned the usb stick to one single partition or whole partition.
Yes i only have one disk in my nas

remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Sun Mar 13, 2011 2:39 am

I got it work now but when i try to perform the install in HDD instruction the first of two i get operation cannot be performed.

Is there any other way to do this??

Mijzelf
Posts: 6207
Joined: Mon Jun 16, 2008 10:45 am

Re: Host web page from NSA 220+

Post by Mijzelf » Sun Mar 13, 2011 8:21 am

You mean

Code: Select all

chmod a+x /i-data/md0/ffproot/after_booting.sh
gives 'operation cannot be performed'?

Did you create a share ffproot and did you put the files in it? Does the share exist on the appropriate place?

Code: Select all

ls -l /i-data/md0
Do the files exist:

Code: Select all

ls -l /i-data/md0/ffproot
Are you logged in as root?

I suggest you to install Midnight Commander, which is a 'grapical interface' for file operations. The command is mc.

remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Mon Mar 14, 2011 5:10 pm

Hi..

I got everything installed now only lighttpd configurering remaining.
What i want now is to know what i should do to make it possible to host mypage after configureing lighttpd??
Or which step do i have to perfrom inordr for this to be possible?

Edit: Doesnt firmeware V3.24 already contain apache server and myphpadmin packages in it? Can i use the included packages(apache and myphpadmin) to host my webpage??
I read it in the pdf file include in the zip file of the firmeware.

Thx

Mijzelf
Posts: 6207
Joined: Mon Jun 16, 2008 10:45 am

Re: Host web page from NSA 220+

Post by Mijzelf » Mon Mar 14, 2011 7:41 pm

remru218 wrote:Hi..

I got everything installed now only lighttpd configurering remaining.
What i want now is to know what i should do to make it possible to host mypage after configureing lighttpd??
Or which step do i have to perfrom inordr for this to be possible?
Is this enough information? http://wiki.dns323.info/howto:ffp#lighttpd_web_server
Doesnt firmeware V3.24 already contain apache server and myphpadmin packages in it? Can i use the included packages(apache and myphpadmin) to host my webpage??
I read it in the pdf file include in the zip file of the firmeware.
Depends. Yes, the firmware contains an apache server, and some installable packets to extend this. But the configuration possibilities are rather limited (your homepage will be in yourdomain.com/myweb/), and you don't have direct access to the apache configuration files. Further apache asks more resources than lighttpd, and a 220 is not directly over-dimensioned. And last but not least: by exposing your website you also expose your NAS login, waiting to be bruteforced.

remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Mon Mar 14, 2011 7:52 pm

Mijzelf wrote: Is this enough information? http://wiki.dns323.info/howto:ffp#lighttpd_web_server
I think this will have to do for the moment. Otherwise if its ok with you to help me if i get stack i can make a post.
Mijzelf wrote: And last but not least: by exposing your website you also expose your NAS login, waiting to be bruteforced.
What do mean by this?
That by using firmeware apache i will expose my NSA? Or that no matter what i choose to use i will expose my NSA for bruteforce attacks??

On another matter, how do i configure to only have one user that has the same access rights as root??

Mijzelf
Posts: 6207
Joined: Mon Jun 16, 2008 10:45 am

Re: Host web page from NSA 220+

Post by Mijzelf » Mon Mar 14, 2011 8:28 pm

remru218 wrote:I think this will have to do for the moment. Otherwise if its ok with you to help me if i get stack i can make a post.
That's OK.
remru218 wrote:What do mean by this? That by using firmeware apache i will expose my NSA? Or that no matter what i choose to use i will expose my NSA for bruteforce attacks??
When you use the firmware Apache, you'll expose the login of your NAS. (The box has actually only 1 webinterface, so by requesting yourdomain.com instead of yourdomain.com/myweb, you'll get the login prompt)

Using lighttpd instead is safer. At least it doesn't expose your admin webinterface. Further you have the possibility to configure it to your needs. (I host a few private websites on my 220, and in the logfiles I see lots of script attacks. But those scripts all request by ip, and not by domain. So I configured lighttpd to give a 404 for all requests by ip.)
On another matter, how do i configure to only have one user that has the same access rights as root??
In ffp you mean? You can create a user with root rights:

Code: Select all

adduser -u 0 -g 0 username
But you can't remove all other users. Some services (like ssh and mysql and maybe also lighttpd) create an own user, to be able to drop root rights as soon as they are running. You can see the list:

Code: Select all

cat /etc/passwd
Why should you want that?

remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Mon Mar 14, 2011 8:37 pm

Mijzelf wrote: Why should you want that?
I want to limit access to only one user so thats why i wanted to remove all other users, but since i cant i will have to leave it as it is.
I will now get on with lighttpd configuration and see how it goes.

Greatly appreciate all the help Mujzelf

remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Mon Mar 14, 2011 9:48 pm

Code: Select all

cd /mnt/HD_a2
What do i do to solve the problem caused by this command?
Because when i enter the command i get an error telling me that
"-sh: cd: can't cd to /mnt/HD_a2"

remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Mon Mar 14, 2011 10:51 pm

remru218 wrote:

Code: Select all

cd /mnt/HD_a2
What do i do to solve the problem caused by this command?
Because when i enter the command i get an error telling me that
"-sh: cd: can't cd to /mnt/HD_a2"
Managed to solve the problem by making a directory with tow subdirectories:
www/pages and www/logs in /ffp/etc and configured lighttpd.conf to point to these directiries instead of /mnt/HD_a2/.
Now the problem is that i cant upload a page to www/paes.
Im getting an error saying that there is no space when i try to upload a page to /ffproot/ffp/etc/www/pages (ffproot is on the internal HDD).

Any idea on how to solve this?

Mijzelf
Posts: 6207
Joined: Mon Jun 16, 2008 10:45 am

Re: Host web page from NSA 220+

Post by Mijzelf » Tue Mar 15, 2011 8:41 am

Because when i enter the command i get an error telling me that
"-sh: cd: can't cd to /mnt/HD_a2"
Ah yes, sorry. Should have read the instruction before. /mnt/HD_a2 is the place where the harddisk is mounted on the DNS-323. On the NSA-220 the corresponding directory is /i-data/md0 (if the symlink works. If not, it's /i-data/<some-hex-code>. Apply a 'ls /i-data' to get the hex-code.
Managed to solve the problem by making a directory with tow subdirectories:
www/pages and www/logs in /ffp/etc and configured lighttpd.conf to point to these directiries instead of /mnt/HD_a2/.
While that should work, it's not recommended. /etc (or /ffp/etc) is reserved for configuration files. Stuff like userdata is supposed to live in /home/<username> (or /ffp/home/<username>) and webpages are normally placed in /var/www/<domainname>, (or ../pages). (In your case /ffp/var/www/<domainname>. Better keep everything in /ffp, unless you have good reasons to do something else)
Now the problem is that i cant upload a page to www/paes.
Im getting an error saying that there is no space when i try to upload a page to /ffproot/ffp/etc/www/pages (ffproot is on the internal HDD).
Strange. I suppose you are trying to upload via the share ffproot? Maybe you don't have write permission via samba for your newly created directory. Try a 'chmod a+w /full/path/to/pages' This command makes 'pages' world-writable. a+w: all + write.

remru218
Posts: 26
Joined: Sat Mar 12, 2011 12:42 am

Re: Host web page from NSA 220+

Post by remru218 » Thu Mar 17, 2011 10:55 am

Hi.

I now manage to config lightttpd as explained on the link and by you.
What i did was create a main directory in /i-data/md0 with to subdirectories pages and logs. This directories can be accessed outside in nsa web interface.
Now the problem is that i can access the webpage internally via nsa ip:8080 but not externally mypage.com.

For sovling the external problem i tried to configure my domain dns settings to point to my nsa ip:8080 which didnt work.
For the moment mydomain.com is pointing to my nsa via www and ftp using mydns.dyndns.org.

My question is how do i fix this??
Do i create a new mydns.dyndns.org to point to the right ip address(web server)?
How do i configure mydomain.com dns so it can point to mypage(web server)?
Do i have to do any routing forwarding in order for this to work and if so what do i exactly need to do??

Thank you

Mijzelf
Posts: 6207
Joined: Mon Jun 16, 2008 10:45 am

Re: Host web page from NSA 220+

Post by Mijzelf » Thu Mar 17, 2011 9:04 pm

A DNS translates a domain name into an IP address. So when you 'ping yourdomain.com', it's really pinging your (public) ip address.
Now you have a webserver on port 8080 of an internal address, which needs to be accessible over port 80 of your external address. Then you have to configure your router to forward port 80 to port 8080 of your NAS.

Post Reply