Open Stock Firmware LS-VL - Revision history

Mikanuu: /* The Guide */

Mikanuu — Mon, 26 Nov 2012 19:14:24 GMT

The Guide

← Older revision		Revision as of 19:14, 26 November 2012
Line 107:		Line 107:

	If your NAS is configured to use RAID1, you may need to change the path to the share from disk1 to array1 for the copy and ssh-keygen commands to work correctly		If your NAS is configured to use RAID1, you may need to change the path to the share from disk1 to array1 for the copy and ssh-keygen commands to work correctly
		+
		+	An another possibility to receive "'''Server refuced our key'''" message is, if the unix scripts were not of unix format. When scripts are run using Windows PC format, the folder ".ssh" is actually created as ".ssh^M", and then the login with the key won't work.

	=== Firmware 1.42 Specialities ===		=== Firmware 1.42 Specialities ===

Steffstuff: /* The Guide */

Steffstuff — Sat, 24 Mar 2012 19:55:31 GMT

The Guide

← Older revision		Revision as of 19:55, 24 March 2012
Line 81:		Line 81:
	: In the next command-lines please replace the ''$IPADDR'' by the IP-address of your LS. If your NAS is configured to use RAID1, you may need to change the path to the share from ''disk1'' to ''array1''.		: In the next command-lines please replace the ''$IPADDR'' by the IP-address of your LS. If your NAS is configured to use RAID1, you may need to change the path to the share from ''disk1'' to ''array1''.

-	:* Check whether both files are there:	+	:* Check whether both files are there (replace "disk1" with "array1" if you are running in RAID mode!):
	java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password -c 'ls /mnt/disk1/share/'		java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password -c 'ls /mnt/disk1/share/'
	:* Now let acp_commander execute the script on your LS		:* Now let acp_commander execute the script on your LS

Kenatonline: /* The result */

Kenatonline — Wed, 28 Dec 2011 08:21:41 GMT

The result

← Older revision		Revision as of 08:21, 28 December 2011
Line 135:		Line 135:
	Because ''mount_DataDisks_sub'' is ignoring the third parameter (that would be the filesystem), I replaced the line with:		Because ''mount_DataDisks_sub'' is ignoring the third parameter (that would be the filesystem), I replaced the line with:
	mount -t ${USERLAND_FS} ${DEV1} /mnt/disk1		mount -t ${USERLAND_FS} ${DEV1} /mnt/disk1
		+
		+	=Speciality of the LS-CHL-V2=
		+	For some reasons, the LS-CHL-V2 is excluded (by Buffalo) from the boxes supporting SSH connections.<br>
		+	The "exclusion" is done via the sanity application and prevents us from changing the SUPPORT_SFTP variable in the file "nas_feature" (and it doesn't matter if we patch the flash environment or not).<br>
		+	Therefore one needs to remove the following lines from the /etc/init.d/sshd.sh:
		+	if [ "${SUPPORT_SFTP}" = "0" ] ; then
		+	echo "Not support sftp on this model." > /dev/console
		+	exit 0
		+	fi
		+	And one needs to link the /etc/init.d/sshd.sh into the /etc/rc.d/extensions.d directory for automatic start at bootup (do '''not''' mess around with /etc/init.d/rcS):
		+	ln -s /etc/init.d/sshd.sh /etc/rc.d/extensions.d/S99sshd

	[[Category:LS-AVL]]		[[Category:LS-AVL]]

Kenatonline: /* Is this guide working for the LS-VL only? */

Kenatonline — Wed, 28 Dec 2011 07:42:55 GMT

Is this guide working for the LS-VL only?

← Older revision		Revision as of 07:42, 28 December 2011
Line 19:		Line 19:
	LS-XHL		LS-XHL

-	Alternatively you can use the guide from the [[Open Stock Firmware LS-XHL\|LS-XHL]], which is more complicated.	+	Alternatively you can use the guide from the [[Open Stock Firmware LS-XHL\|LS-XHL]], which is more complicated.<br>
		+	See the last chapter for a speciality of the LS-CHL-V2.

	=What will be done?=		=What will be done?=

Lsuser1985: enhanced sed command (idea from http://forum.buffalo.nas-central.org/viewtopic.php?f=68&t=23919)

Lsuser1985 — Sun, 21 Aug 2011 12:07:00 GMT

enhanced sed command (idea from http://forum.buffalo.nas-central.org/viewtopic.php?f=68&t=23919)

← Older revision		Revision as of 12:07, 21 August 2011
Line 67:		Line 67:

	### Enable root login for SSH		### Enable root login for SSH
-	# Backup	+	# Backup sshd_config
-	mv /etc/sshd_config /etc/sshd_config.orig	+	cp -p /etc/sshd_config /etc/sshd_config.orig
-	# ~~Remove~~ all ~~references to~~ PermitRootLogin ~~and create a new sshd_config~~	+	# Replace all "PermitRootLogin no" by "PermitRootLogin yes"
-	~~grep~~ -v PermitRootLogin /~~etc~~/~~sshd_config.orig >~~ /~~etc~~/~~sshd_config~~	+	sed -i '/PermitRootLogin/s/no/yes/' /etc/sshd_config
-	~~# Add the PermitRootLogin Yes into the new sshd_config file~~	+
-	~~echo PermitRootLogin yes >>~~ /etc/sshd_config	+
	chmod 600 /etc/sshd_config		chmod 600 /etc/sshd_config
	# Verify		# Verify
-	~~tail~~ /etc/sshd_config	+	grep PermitRootLogin /etc/sshd_config

	# Last we restart the sshd.		# Last we restart the sshd.

Kenatonline: /* The Guide */

Kenatonline — Sat, 18 Jun 2011 13:16:56 GMT

The Guide

← Older revision		Revision as of 13:16, 18 June 2011
Line 108:		Line 108:

	If your NAS is configured to use RAID1, you may need to change the path to the share from disk1 to array1 for the copy and ssh-keygen commands to work correctly		If your NAS is configured to use RAID1, you may need to change the path to the share from disk1 to array1 for the copy and ssh-keygen commands to work correctly
		+
		+	=== Firmware 1.42 Specialities ===
		+	If you have problems establishing a ssh connection, it could be possible that this is caused by a missing file of the PAM configuration.<br>
		+	By comparing 1.42 with 1.36, there is no "/etc/pam.d/sshd" anymore.<br>
		+	You can add this file yourself by copying this content (1:1 copy of 1.36) to the file:
		+	auth required pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
		+	#auth required pam_smb_auth.so debug
		+	#auth required pam_unix.so nullok
		+	auth required pam_unix.so
		+	#auth required pam_winbind.so debug
		+	account required pam_unix.so
		+	#account required pam_winbind.so
		+	session required pam_unix.so
		+	Assuming that you put the content into a file named "sshd" on your share "share", you can use this command to copy the file to its final destination:
		+	java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password -c 'cp /mnt/disk1/share/sshd /etc/pam.d/sshd'

	=The result=		=The result=

Kenatonline: /* The Guide */

Kenatonline — Sun, 22 May 2011 09:19:25 GMT

The Guide

← Older revision		Revision as of 09:19, 22 May 2011
Line 94:		Line 94:
	ACP="java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw $PASSWD"		ACP="java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw $PASSWD"

-	smbclient '\\'$IP'\share' '' -c "put $HOME/.ssh/authorized_keys authorized_keys"	+	smbclient '\\'$IPADDR'\share' '' -c "put $HOME/.ssh/authorized_keys authorized_keys"
-	smbclient '\\'$IP'\share' '' -c "put open-ls.txt open-ls.txt"	+	smbclient '\\'$IPADDR'\share' '' -c "put open-ls.txt open-ls.txt"
-	smbclient '\\'$IP'\share' '' -c "dir"	+	smbclient '\\'$IPADDR'\share' '' -c "dir"

	$ACP -c "ls /mnt/$DISK/share/"		$ACP -c "ls /mnt/$DISK/share/"
	$ACP -c "sh -x /mnt/$DISK/share/open-ls.txt"		$ACP -c "sh -x /mnt/$DISK/share/open-ls.txt"
-	ssh root@$IP	+	ssh root@$IPADDR

Kenatonline: /* The Guide */

Kenatonline — Mon, 16 May 2011 06:36:40 GMT

The Guide

← Older revision		Revision as of 06:36, 16 May 2011
Line 83:		Line 83:

	:* Check whether both files are there:		:* Check whether both files are there:
-	java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password 'ls /mnt/disk1/share/'	+	java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password -c 'ls /mnt/disk1/share/'
	:* Now let acp_commander execute the script on your LS		:* Now let acp_commander execute the script on your LS
-	java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password 'sh -x /mnt/disk1/share/open-ls.txt'	+	java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password -c 'sh -x /mnt/disk1/share/open-ls.txt'

	As an alternative, here is a Unix/Linux script to ease copying the files and execute the copied script. There is no need to save it onto a file, simply copy and paste line by line into you shell, while adapting to your needs.		As an alternative, here is a Unix/Linux script to ease copying the files and execute the copied script. There is no need to save it onto a file, simply copy and paste line by line into you shell, while adapting to your needs.

Lsuser1985: /* The Guide */

Lsuser1985 — Tue, 10 May 2011 12:46:25 GMT

The Guide

← Older revision		Revision as of 12:46, 10 May 2011
Line 50:		Line 50:
	Look below for a Linux/Unix script easing the next three steps.		Look below for a Linux/Unix script easing the next three steps.

-	# Put your public key in a file named ''authorized_keys'' and put the file ~~onto~~ the share "share" (do not use a subdirectory).	+	# Put your public key in a file named ''authorized_keys'' and put the file into the share "share" (do not use a subdirectory to make this guide work).
	# Put the lines below into a a file named ''open-ls.txt'' and put it in the same place.		# Put the lines below into a a file named ''open-ls.txt'' and put it in the same place.
	#!/bin/bash		#!/bin/bash

Lsuser1985: /* The Guide */

Lsuser1985 — Tue, 10 May 2011 11:28:42 GMT

The Guide

← Older revision		Revision as of 11:28, 10 May 2011
Line 87:		Line 87:
	java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password 'sh -x /mnt/disk1/share/open-ls.txt'		java -jar acp_commander.jar -t $IPADDR -ip $IPADDR -pw password 'sh -x /mnt/disk1/share/open-ls.txt'

-	As an alternative, here is a Unix/~~Linix~~ script to ease copying the files and execute the copied script:	+	As an alternative, here is a Unix/Linux script to ease copying the files and execute the copied script. There is no need to save it onto a file, simply copy and paste line by line into you shell, while adapting to your needs.

	IPADDR=192.168.110.4		IPADDR=192.168.110.4