General NAS-Central Forums

Welcome to the NAS community
It is currently Mon Sep 25, 2017 2:44 am

All times are UTC




Post new topic Reply to topic  [ 149 posts ]  Go to page 1, 2, 3, 4, 5 ... 10  Next
Author Message
PostPosted: Fri Oct 07, 2011 11:26 am 
Offline

Joined: Wed Dec 16, 2009 9:57 pm
Posts: 134
Script to create a custom capsule: http://downloads.lacie.nas-central.org/Users/andreus/scripts/lacieos/create_capsule.sh_v7.txt

In version 7 you can create a custom capsule with:
  • SFTP/SSH Root access (through port 2222)
  • TwonkyMedia Server Web browse and configuration access (through port 9000)
  • Transmission Web Interface access (through port 9091)
  • Add HTTP(S) username/password authentication security (if you need to access your NAS from a external network and you have configured port forwarding in your router, see http://forum.nas-central.org/viewtopic.php?f=240&t=4669)

This method should work in the following products/versions:
  • Network Space 2: Up to version 2.2.5
  • Network Space MAX: Up to version 2.2.3
  • d2 Network 2: Up to version 2.2.5
  • 2Big Network 2: Up to version 2.2.8
  • 5Big Network 2: Up to version 2.2.3

If you use it please post here the results. Already tested:

2Big Network 2
  • Custom capsulebuilt on | Original firmware version (rooted/not rooted) | Custom firmware version (rooted) | Got root access?
  • LacieOS | 1.3.6 (after factory reset) | 2.0.5.1 | Yes
  • LacieOS | 2.0.5 | 2.0.5.1 | Yes
  • LacieOS | 2.0.5 | 2.0.6.1 | Yes
  • LacieOS | 2.0.5 (rooted) | 2.0.5.1 | Yes
  • LacieOS | 2.0.5 (rooted) | 2.0.6.1 | Yes
  • LacieOS | 2.0.6 (rooted) | 2.0.6.1 | Yes
  • LacieOS | 2.0.6.1 (rooted) | 2.1.2.1 | Yes (on update, no root, restart it again and then root as enabled)
  • LacieOS | 2.1.2.1 (rooted) | 2.1.3.1 | Yes (on update, no root, restart it again and then root as enabled)
  • LacieOS | 2.1.3.1 (rooted) | 2.2.3.1 | Yes (on update, no root, restart it again and then root as enabled)
  • LacieOS | 2.2.3.1 (rooted) | 2.2.8.1 | Yes (on update, no root, restart it again and then root as enabled)
  • Ubuntu | 2.0.6 | 2.0.6.1 | Yes (by rmar)
  • Ubuntu | 2.0.6 | 2.1.2.1 | Yes (by rmar)
  • Ubuntu (VM) | 2.0.6 | 2.0.6.1 | No (by Lumpsack)
  • Ubuntu (VM) | 2.1.2 | 2.1.2.1 | Yes (by Lumpsack)
  • Ubuntu (VM) | 2.1.3 | 2.1.3.1 | Yes (by pvdveen)

5Big Network 2
  • Custom capsulebuilt on | Original firmware version (rooted/not rooted) | Custom firmware version (rooted) | Got root access?
  • Unknown | 2.1.2 | 2.2.3.1 | Yes (by JFM)

Network Space 2
  • Custom capsulebuilt on | Original firmware version (rooted/not rooted) | Custom firmware version (rooted) | Got root access?
  • Mandriva 2010.1 | 1.2.6 | 2.0.5.1 | Yes (by Mijzelf)
  • Ubuntu (VM) | 1.2.93 | 2.1.2.1 | Yes (by Jamcar)
  • Parted Magic (VM) | 1.2.9 (after factory reset) | 2.1.2.1 | Yes (by ngrcld)
  • Unknown | 2.0.6 | 2.1.1.1 | Yes (by astaldo1977)
  • Unknown | 2.1.2 | 2.1.2.1 | No (by kamelie1706)
  • Unknown | 1.2.93 (after factory reset) | 2.1.2.1 | Yes (by kamelie1706)
  • Unknown | 1.0.2 (after factory reset) | 2.2.3.1 | Yes (by rimoth)
  • LacieOS | 2.0.5 | 2.2.4.1 | Yes (by cyberdog)
  • LacieOS | 2.2.5 | 2.2.5.1 | Yes (by metronomadic)
  • Ubuntu 11.10 | 2.2.4 | 2.2.4.1 | Yes (by svenpap)
  • CenttOS 5.7 | Unknown | 2.2.5.1 | Yes (by ragnar)
  • Xbuntu 11.10 | 2.2.4 (rooted) | 2.2.5.1 | Yes (by frikzy)
  • Debian 5 (VM) | 2.2.4.1 (rooted) | 2.2.5.1 | Yes (by sawadee)
  • Ubuntu 11.10 | Unknown | 2.2.3.1 | Yes (by klaafstra99)

Network Space MAX
  • Custom capsulebuilt on | Original firmware version (rooted/not rooted) | Custom firmware version (rooted) | Got root access?
  • ArchLinux | 2.0.4 (rooted) | 2.2.3.1 | Yes (by croma25td)

This is an firmware "update" so you know the risks. Read the wiki for more information.
Wiki: http://lacie.nas-central.org/wiki/Category:2big_Network_2#Custom_capsule

Update: updated with version 3 of the script. Script is much more automatic now.
Update 2: updated with version 4 of the script. Minor bug fixes and more simple.
Update 3: updated with version 5 of the script. Code improvements and options to open twonky and transmission web managers.
Update 4: updated with version 6 of the script. Corrected a bug identified by 'rmar', added various tests (paths, old folders, etc) for reducing the error probability and improve debugging.
Update 5: updated with version 6.1 of the script. Corrected a path compability problem identified by 'Mijzelf'.
Update 6: updated with version 7 of the script. More path compability with non LacieOS systems (suggested by 'Mijzelf'). Option to had HTTP autentication security for protecting when HTTP access is open through port forwarding (suggested by 'Mijzelf').

Important notes:
  • You have to run the custom capsule script in a linux system with root or superuser permissions
  • When you have the custom capsule i advice to use "Update Method 3 - Manual Force Update" (http://lacie.nas-central.org/wiki/Category:2big_Network_2#3._Manual_Force_Update). I also advice you to reboot from the dashboard
  • If after the update for some reason don't have root access, reboot it again
  • After updating, if you're using transmission web interface don't forget to change the download path after each reboot.
  • After updating, if you're using twonky web interface don't forget to change the shares path after each reboot.


Last edited by andreus on Sat Apr 28, 2012 7:14 pm, edited 47 times in total.

Top
 Profile  
 
PostPosted: Mon Oct 10, 2011 9:14 pm 
Offline

Joined: Wed Dec 16, 2009 9:57 pm
Posts: 134
The output of the script in Linux should look something like this:
Code:
-------------------------------------------------
       Custom Capsule Creator Script v7
-------------------------------------------------

Analysing your system:
- directory exists ..........no
  Do you want to create '/home/lacie' directory? [y/n]: y
  OK (done)
- lzma installed ..........yes (/usr/lzma)
- wget installed ..........yes (/usr/bin/wget)
- sha1sum installed ..........yes (/usr/bin/sha1sum)
- tar installed ..........yes (/bin/tar)
- curl installed ..........yes (/usr/bin/curl)
- LaCie hardware:  ..........not found
- LaCie firmware version:  ..........not found

Choose what to customize:
- Choose LaCie hardware you want to customize:
  1. Network Space 2
  2. Network Space MAX
  3. d2 Network 2
  4. 2big Network 2
  5. 5big Network 2
  Choose one option: 4
- Choose original capsule version to download and customize:
  1. Version 1.2.6
  2. Version 1.3.3
  3. Version 1.3.6
  4. Version 2.0.5
  5. Version 2.0.6
  Choose one option: 4
- Do you want to have root access? [y/n]: y
- Do you want to access TwonkyMedia server web configuration and browse? [y/n]: y
- Do you want to access Transmission Web Interface? [y/n]: y
- Do you want to secure access from a external network? [y/n]: y
  HTTP authentication Username: xxxx
  HTTP authentication Password: yyyy

Preparing:
- Deleting old files ..........OK (done)

Downloading original capsule:
- Downloading 2big Network 2 2.0.5 capsule
Connecting to 2bignetwork2-update.lacie.com (88.198.15.210:21)
2bignetwork2_2.0.5.c 100% |*********************************************************************************| 57130k --:--:-- ETA
  OK (done)

Extracting capsule:
- Extracting original (2.0.5) capsule ..........OK (done)
- Unpacking original (2.0.5) capsule tarball ..........OK (done)
- Unpacking original (2.0.5) rootfs tarball (can take up to 5 minutes) ..........OK (done)

Duplicating capsule:
- Duplicating to custom (2.0.5.1) capsule folder ..........OK (done)
- Duplicating to custom (2.0.5.1) rootfs folder (can take up to 3 minutes) ..........OK (done)

Customizing capsule:
- Enabling root access:
  - Enabling sshd in default.runlevel ..........  OK (done)
  - Downloading custom 'sshd.i'
Connecting to downloads.lacie.nas-central.org (140.211.169.172:80)
sshd.i               100% |*********************************************************************************|  2077  --:--:-- ETA
    OK (done)
- Enabling TwonkyMedia Server Web Interface. Downloading custom 'twonkymedia.i'
Connecting to downloads.lacie.nas-central.org (140.211.169.172:80)
twonkymedia.i        100% |*********************************************************************************|   953  --:--:-- ETA
  OK (done)
- Enabling Transmission Web Interface. Downloading custom 'transmission.i'
Connecting to downloads.lacie.nas-central.org (140.211.169.172:80)
transmission.i       100% |*********************************************************************************|  1285  --:--:-- ETA
  OK (done). Web access enabled (whitelist disabled).
- Enabling security for external access. Downloading custom '/etc/initng/http.i'.
Connecting to downloads.lacie.nas-central.org (140.211.169.172:80)
http.i       100% |*********************************************************************************|  1285  --:--:-- ETA
  OK (done). External access security enabled (username: xxxx | password: yyyy)

Packing capsule:
- Packing custom (2.0.5.1) rootfs tarball (can take up to 30 minutes, depending on compression level) ..........OK (done)
- Changing custom capsule description:
  - Original 'rootfs.tar.lzma' sha1sum: 07bcb6484e3fb7315aaf52c71db9273ca1d37b9f
  - New 'rootfs.tar.lzma' sha1sum: b5f622c118e68c47ec63d4ff5174e56dae0d11d1
  - Replacing sha1sum in 'description.xml'
  - Replacing capsule version with new capsule version in 'description.xml' ..........OK (done)
  - Adding 2.0.5 version to upgradeble versions ..........OK (done)
- Updating 'description.sha1' ..........OK (done)
- Rebuilding capsule file ..........OK (done)

---------------------------------------------

New capsule built: '/home/lacie/2bignetwork2_2.0.5.1.capsule'
After upgrading you can:
- use SSH/SFTP with root privileges with your Lacie NAS with login 'root' (login: root | password: [same as admin password] | Port: 2222)
- use TwonkyMedia Server Web Interface (url: http://YOUR.LACIE.NAS.IP:9000/)
- use Transmission Web Interface (url: http://YOUR.LACIE.NAS.IP:9091/transmission/web/)
  Don't forget to change the transmission download path.
- access, after configuring port forwarding in your router, from a external network:
  - Lacie Dashboard: http://YOUR.NETWORK.EXTERNAL.IP/
  - TwonkyMedia Server: http://YOUR.NETWORK.EXTERNAL.IP:9000/
  - Transmission Web Interface: http://YOUR.NETWORK.EXTERNAL.IP:9091/transmission/web/
  Use username 'xxxx' and password 'yyyy' for HTTP authentication


Last edited by andreus on Sun Oct 16, 2011 10:31 am, edited 5 times in total.

Top
 Profile  
 
PostPosted: Tue Oct 11, 2011 7:26 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
I've just upgraded my Networkspace2 from 1.2.6 to 2.0.5.1 using your script (v6). The script run on Mandriva 2010.1, and the upgrading succeeded.

On the Networkspace you can't create a share 'Share' (at least, I can't find a way using the dashboard), but just putting the capsule in MyShare/Update/ worked.

One little annoyance: the script insists on installing in /media/internal_1, which makes no sense (on a non-Lacie). On my box /media doesn't have enough diskspace. I edited the script to use /tmp/internal_1 instead. I suggest to use curdir/<whatever> instead, when you detect it's not a Lacie.
On my NS2 it would have failed either. There is no /media/internal_1, so it would have resided in sda9, which has only 500MB free, while the script took about 750MB.
Code:
/dev/sda2 on /media/internal_6 type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/tmp type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/var type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/torrent_dir type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/autoupdate type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/afp_db type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /shares/MyShare type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /shares/OpenShare type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
It should have been /media/internal_6, but /lacie/tmp also works. Don't know if that would also work on your device.


Top
 Profile  
 
PostPosted: Tue Oct 11, 2011 8:15 pm 
Offline

Joined: Wed Dec 16, 2009 9:57 pm
Posts: 134
Mijzelf,

As usual, you're comments are useful.

Quote:
I've just upgraded my Networkspace2 from 1.2.6 to 2.0.5.1 using your script (v6). The script run on Mandriva 2010.1, and the upgrading succeeded.

Great! And twonky and transmission worked ok?

Quote:
On the Networkspace you can't create a share 'Share' (at least, I can't find a way using the dashboard), but just putting the capsule in MyShare/Update/ worked.

Updated the wiki http://lacie.nas-central.org/wiki/Category:2big_Network_2#3._Manual_Force_Update

Quote:
One little annoyance: the script insists on installing in /media/internal_1, which makes no sense (on a non-Lacie). On my box /media doesn't have enough diskspace. I edited the script to use /tmp/internal_1 instead. I suggest to use curdir/<whatever> instead, when you detect it's not a Lacie.
On my NS2 it would have failed either. There is no /media/internal_1, so it would have resided in sda9, which has only 500MB free, while the script took about 750MB.
Code:
/dev/sda2 on /media/internal_6 type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/tmp type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/var type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/torrent_dir type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/autoupdate type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /lacie/afp_db type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /shares/MyShare type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)
/dev/sda2 on /shares/OpenShare type xfs (rw,nosuid,nodev,noatime,usrquota,prjquota,grpquota)

It should have been /media/internal_6, but /lacie/tmp also works. Don't know if that would also work on your device.

In the 2big Network 2 the path '/lacie/tmp' also exists. Replaced '/media/internal_1' by this path in the script for more compability.

However, the path can always be changed inside the script in the varible 'internal_disk_path='

Quote:
I suggest to use curdir/<whatever> instead, when you detect it's not a Lacie.

Will analyse that.


Top
 Profile  
 
PostPosted: Wed Oct 12, 2011 10:44 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
andreus wrote:
Great! And twonky and transmission worked ok?
There is a twonky interface on port 9000, which looks as if it's intended to look the way it does. I have no idea if twonky is actually working, as I don't have an appropriate client. There is no transmission interface, but there is no transmission running either. I suppose it will be started when I start a (torrent) download. I'll try to see if the transmission interface is available then.

BTW, did you consider to use the proxy capabilities of lighttpd to redirect it to port 80 (and 442)? Could be useful to access the pages from the internet.

Quote:
In the 2big Network 2 the path '/lacie/tmp' also exists. Replaced '/media/internal_1' by this path in the script for more compability.
I suppose /lacie/tmp also points to the datapartition on the 2Big2?


Top
 Profile  
 
PostPosted: Wed Oct 12, 2011 11:25 am 
Offline

Joined: Wed Dec 16, 2009 9:57 pm
Posts: 134
Mijzelf wrote:
andreus wrote:
Great! And twonky and transmission worked ok?
There is a twonky interface on port 9000, which looks as if it's intended to look the way it does. I have no idea if twonky is actually working, as I don't have an appropriate client. There is no transmission interface, but there is no transmission running either. I suppose it will be started when I start a (torrent) download. I'll try to see if the transmission interface is available then.

In Twonky if you see the Twonky web page is because it is working and you have access to web interface.
Yes, you have to start transmisison in the dashboard first. By default the service is stoped.

Mijzelf wrote:
BTW, did you consider to use the proxy capabilities of lighttpd to redirect it to port 80 (and 442)? Could be useful to access the pages from the internet.

No. What's your idea?

Mijzelf wrote:
andreus wrote:
In the 2big Network 2 the path '/lacie/tmp' also exists. Replaced '/media/internal_1' by this path in the script for more compability.
I suppose /lacie/tmp also points to the datapartition on the 2Big2?

Yes, it's true. You can see in 'cat /proc/mounts' here http://lacie.nas-central.org/wiki/Category:2big_Network_2#Product_information


Top
 Profile  
 
PostPosted: Wed Oct 12, 2011 1:27 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
andreus wrote:
No. What's your idea?
When you add the lines
Code:
$HTTP["url"] =~ "^/twonky($|/)" {
   proxy.server = ( "" =>
      ( (
          "host" => "127.0.0.1",
          "port" => 9000
      ) )
   )
}
to an appropriate place in lighttpd.conf, then accessing http://<ip-of-nas>/twonky will show the twonky page over port 80. So if you forwarded port 80 (or 442) in your router to be able to access your dashboard from outside, you can also access twonky. Don't know if that is useful, as I don't know twonky, but it can certainly be useful for transmission.

There is a security issue, as this page won't be protected by the dashboard password, but lighttpd can also handle that. But I don't know if the needed modules are installed.


Top
 Profile  
 
PostPosted: Wed Oct 12, 2011 3:24 pm 
Offline

Joined: Wed Dec 16, 2009 9:57 pm
Posts: 134
Mijzelf wrote:
andreus wrote:
No. What's your idea?
When you add the lines
Code:
$HTTP["url"] =~ "^/twonky($|/)" {
   proxy.server = ( "" =>
      ( (
          "host" => "127.0.0.1",
          "port" => 9000
      ) )
   )
}
to an appropriate place in lighttpd.conf, then accessing http://<ip-of-nas>/twonky will show the twonky page over port 80. So if you forwarded port 80 (or 442) in your router to be able to access your dashboard from outside, you can also access twonky. Don't know if that is useful, as I don't know twonky, but it can certainly be useful for transmission.

I tested and that work ok on transmission, but not so good on Twonky. Twonky puts absolutes URL's. I tried but with not great success.
Transmission
Code:
$HTTP["url"] =~ "^/transmission($|/)" {
   proxy.server = ( "" =>
      ( (
          "host" => "127.0.0.1",
          "port" => 9091
      ) )
   )
}


Twonky
Code:
url.rewrite-once = ( "^/twonky($|/)(.*)" => "/webbrowse$1$2" )
$HTTP["url"] =~ "^/(twonky|webbrowse)($|/)" {
   
   proxy.server = ( "" =>
     ( (
          "host" => "127.0.0.1",
          "port" => 9000
      ) )
   )
}

In the case of twonky, I think you also have to configure twonky ini file (http://www.twonkyforum.com/viewtopic.php?f=2&t=9497) with this settings
Code:
remoteaccess=1
httpremoteport=9100
dyndns=xxxxxxx.dyndns.org


Mijzelf wrote:
There is a security issue, as this page won't be protected by the dashboard password, but lighttpd can also handle that. But I don't know if the needed modules are installed.

I don't see mod_auth in httpd the conf file
Code:
server.modules              = (
#  "mod_redirect",
#  "mod_cgi",
  "mod_expire",
  "mod_compress",
  "mod_proxy",
  "mod_fastcgi",
  "mod_rewrite",
)


Last edited by andreus on Sun Oct 16, 2011 12:14 am, edited 1 time in total.

Top
 Profile  
 
PostPosted: Wed Oct 12, 2011 6:48 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
Transmission doesn't work out-of-the-box. After starting the 'Download Machine' (yeah), asking for http://networkspace2/9091 gives:
Code:
403: Forbidden
Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.

I looked in the json file, and 127.0.0.1 and 192.168.*.* were whitelisted. My lan uses another range, so that is the problem. Changed the whitelist, and it works.
Tried also the proxy option, which gave me
Code:
409: Conflict
Your request had an invalid session-id header.
To fix this, follow these steps:
1- When reading a response, get its X-Transmission-Session-Id header and remember it
2- Add the updated header to your outgoing requests
3- When you get this 409 error message, resend your request with the updated header
This requirement has been added to help prevent CSRF attacks.
X-Transmission-Session-Id: ekaNqp7KM6V5dzgMCDn9pQLl0vQtBxSa1f5ST3gvgQE3A7Me

A google told me that the url had to be <ip-of-nas>/transmission/web/ including the last slash. That worked indeed. And this way the server is accessed from 127.0.0.1, which is on the whitelist.


Top
 Profile  
 
PostPosted: Sat Oct 15, 2011 10:50 pm 
Offline

Joined: Wed Dec 16, 2009 9:57 pm
Posts: 134
After trying several possible solutions i don't think using lighttpd proxy is the best way to do this.

I think the best way is port forward the several ports (http://forum.nas-central.org/viewtopic.php?f=240&t=4669) depending on what you want to access from an external network.

And regarding external security, you have to create a password file (/etc/lighttpd/.passwd) for lighttpd mod_auth and had the following code at the end of /etc/lighttpd/lighttpd.conf.

Code:
server.modules += ( "mod_auth" )
auth.debug = 2
auth.backend = "htdigest"
auth.backend.htdigest.userfile = "/etc/lighttpd/.passwd"

$HTTP["remoteip"] != "127.0.0.1" {
$HTTP["remoteip"] != "10.0.0.0/8" {
$HTTP["remoteip"] != "172.16.0.0/12" {
$HTTP["remoteip"] != "192.168.0.0/16" {
auth.require = ( "/" => ( "method" => "digest",   "realm" => "Password Protected Area", "require" => "valid-user"   ) )
}
}
}
}


This way, in your network, the browser won't ask another password, but in a external network it will ask for login and password.

Updated the script to v7 with the security part


Top
 Profile  
 
PostPosted: Thu Nov 03, 2011 10:50 am 
Offline

Joined: Sat Oct 23, 2010 7:06 pm
Posts: 7
I just updated my NS2 2.0.6 to 2.1.1 using this script.
And I have root access now.

Please can you tell me why i have port 22 AND port 2222 open, but I can only authorize correctly on 2222?

BTW:
I had some special characters in my admin password (#) blocking me from authorizing myself. I had to use a plaintext password.
(Now im using keyFiles for more security)

EDIT:
Can i remove the sshd.i file when I only want to authorize with my keyfiles?


Top
 Profile  
 
PostPosted: Thu Nov 03, 2011 12:32 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6039
Ports 22 and 2222 are both open because proftpd is running on 22 (to provide scp sessions), so sshd had to move.

No, you can't remove sshd.i. It's the startscript which launches sshd. If you want to disable password logins, edit /etc/ssh/sshd_config.


Top
 Profile  
 
PostPosted: Thu Nov 03, 2011 1:57 pm 
Offline

Joined: Sat Oct 23, 2010 7:06 pm
Posts: 7
Ok thanks a million!
Your script works like a charm.


Top
 Profile  
 
PostPosted: Tue Nov 29, 2011 9:16 am 
Offline

Joined: Tue Nov 29, 2011 9:13 am
Posts: 5
I am a total newbie, so could you please tell me how to run this script without root access?

I have Network Space 2 firmware 2.0.6 WITHOUT root access. I have tried to get root access but had 404 not found error. So is there someway how I can run this Custom Firmware script without having root access? I have Windows XP.

regards, Jamcar


Top
 Profile  
 
PostPosted: Tue Nov 29, 2011 12:28 pm 
Offline

Joined: Wed Dec 16, 2009 9:57 pm
Posts: 134
You can use regular Linux

If you don't have linux installed in your PC use UBuntu Live CD or USB PenDisk (http://www.ubuntu.com/download/ubuntu/download) to boot linux on your computer


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 149 posts ]  Go to page 1, 2, 3, 4, 5 ... 10  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 5 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:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group