Freelink - Convert the LinkStation into a Full-fledged Debian Linux Server - Revision history

Stallwa: /* Install Software */

Stallwa — Tue, 17 Mar 2009 19:46:17 GMT

Install Software

← Older revision		Revision as of 19:46, 17 March 2009
Line 74:		Line 74:
	<tt>apt-get update</tt>		<tt>apt-get update</tt>
	<small><font color=red>note: You might need to edit your <tt>/etc/apt/sources.list</tt> file, changing all references to "stable" with "etch" since etch is no longer the stable Debian distribution</font></small>		<small><font color=red>note: You might need to edit your <tt>/etc/apt/sources.list</tt> file, changing all references to "stable" with "etch" since etch is no longer the stable Debian distribution</font></small>
		+	<font color=red>Update:note: Definitely do change the /etc/apt/sources.lst file. If you don't your Linkstation can attempt to update to Lenny, and Lenny won't boot unless you've installed uboot and a v2.6 kernel</font>
	<br><br><br><br>		<br><br><br><br>
	'''6)''' Then install OpenSSH:		'''6)''' Then install OpenSSH:

Thenegus: /* Install Software */

Thenegus — Mon, 23 Feb 2009 11:32:28 GMT

Install Software

← Older revision		Revision as of 11:32, 23 February 2009
Line 69:		Line 69:
	<font color=red>nameserver <<DNS SERVER IP>></font>		<font color=red>nameserver <<DNS SERVER IP>></font>
	[[Image:GeneralFreeLink4.jpg\|100px\|thumb\|apt-get update]]		[[Image:GeneralFreeLink4.jpg\|100px\|thumb\|apt-get update]]
		+
		+
	'''5)''' Now we can begin installing software. Debian uses a program called [[w:Advanced Packaging Tool\| The Advanced Packaging Tool (apt)]] to manage the software on your computer. Think of it as a very advanced command line version of Windows add / remove programs. First update the apt package list and install SSH:		'''5)''' Now we can begin installing software. Debian uses a program called [[w:Advanced Packaging Tool\| The Advanced Packaging Tool (apt)]] to manage the software on your computer. Think of it as a very advanced command line version of Windows add / remove programs. First update the apt package list and install SSH:
	<tt>apt-get update</tt>		<tt>apt-get update</tt>
-	<br><br><br><br><br><br>	+	<small><font color=red>note: You might need to edit your <tt>/etc/apt/sources.list</tt> file, changing all references to "stable" with "etch" since etch is no longer the stable Debian distribution</font></small>
		+	<br><br><br><br>
	'''6)''' Then install OpenSSH:		'''6)''' Then install OpenSSH:

Argusalverde: /* Install FreeLink */

Argusalverde — Sat, 17 Jan 2009 12:45:24 GMT

Install FreeLink

← Older revision		Revision as of 12:45, 17 January 2009
Line 33:		Line 33:
	*Run the firmware updater executable <tt>HD-???LAN FWUpdate-english.exe</tt>		*Run the firmware updater executable <tt>HD-???LAN FWUpdate-english.exe</tt>
	:[[Image:GeneralFreeLink1.jpg\|300px]]		:[[Image:GeneralFreeLink1.jpg\|300px]]
-	*After finding your LinkStation, press the "Renew Firmware" button, and wait. Have patience, and keep ~~your~~ calm. If you think the Firmware updater is acting strange, do not try to disconnect the LinkStation or abort the update in another way.	+	*After finding your LinkStation, press the "Renew Firmware" button, and wait. Have patience, and keep calm. If you think the Firmware updater is acting strange, do not try to disconnect the LinkStation or abort the update in another way. You may see an error from the firmware updater when the process is complete. Don't panic right away. This is because the updater can no longer reach the Linkstation since the IP address has probably changed. Don't panic, move on to the next step.
-	*After flashing connect your LinkStation up to ~~the~~ network with ~~subnet~~ 192.168.1.XXX ~~. To be clear here,~~ your ~~machine will lose its previos IP~~ config ~~and will not respond as a LinkStation to firmware updated~~. ~~Don't panic, this is ok.~~ Your linkstation is trying to get its IP address through DHCP~~, figure~~ out what it is using and telnet to that IP address.	+	*After flashing connect your LinkStation up to a network with a DHCP server so that it can get an IP address on your network. For many people this might default to 192.168.1.XXX depending on your existing network config.
-	*Find your LinkStation on the network and [[w:Telnet\|Telnet]] to it with [[w:PuTTY\|PuTTYtel]] You will be at the root shell.	+	*Find your LinkStation on the network: Your linkstation is trying to get its IP address through DHCP. Figure out what IP it is now using and telnet to that IP address. [[w:Telnet\|Telnet]] to it with [[w:PuTTY\|PuTTYtel]] (or your favorite telnet client.) You will be at the root shell.

	{{Warning\| '''The MIPSel version of FreeLink does not have telnet enabled as a default''' but rather [[w:SSH\|SSH]]. Use [[w:PuTTY\|PuTTY]] to open a SSH session to: <tt>192.168.11.150</tt> (it has a static IP).<br>login as: <tt>'''root'''</tt> , password: <tt>'''freelink'''</tt>}}		{{Warning\| '''The MIPSel version of FreeLink does not have telnet enabled as a default''' but rather [[w:SSH\|SSH]]. Use [[w:PuTTY\|PuTTY]] to open a SSH session to: <tt>192.168.11.150</tt> (it has a static IP).<br>login as: <tt>'''root'''</tt> , password: <tt>'''freelink'''</tt>}}

Argusalverde: /* Install FreeLink */

Argusalverde — Sat, 17 Jan 2009 12:38:12 GMT

Install FreeLink

← Older revision		Revision as of 12:38, 17 January 2009
Line 34:		Line 34:
	:[[Image:GeneralFreeLink1.jpg\|300px]]		:[[Image:GeneralFreeLink1.jpg\|300px]]
	*After finding your LinkStation, press the "Renew Firmware" button, and wait. Have patience, and keep your calm. If you think the Firmware updater is acting strange, do not try to disconnect the LinkStation or abort the update in another way.		*After finding your LinkStation, press the "Renew Firmware" button, and wait. Have patience, and keep your calm. If you think the Firmware updater is acting strange, do not try to disconnect the LinkStation or abort the update in another way.
-	*After flashing connect your LinkStation up to the network with subnet 192.168.1.XXX	+	*After flashing connect your LinkStation up to the network with subnet 192.168.1.XXX . To be clear here, your machine will lose its previos IP config and will not respond as a LinkStation to firmware updated. Don't panic, this is ok. Your linkstation is trying to get its IP address through DHCP, figure out what it is using and telnet to that IP address.
	*Find your LinkStation on the network and [[w:Telnet\|Telnet]] to it with [[w:PuTTY\|PuTTYtel]] You will be at the root shell.		*Find your LinkStation on the network and [[w:Telnet\|Telnet]] to it with [[w:PuTTY\|PuTTYtel]] You will be at the root shell.

Publicspam: /* Install FreeLink */

Publicspam — Wed, 09 Jul 2008 10:13:52 GMT

Install FreeLink

← Older revision		Revision as of 10:13, 9 July 2008
Line 25:		Line 25:
	\|}		\|}

-	Note: The HS-DGL300 was tested to be flushed to latest stock firmware for the HS (1.62, Jul 2008). After this the HG freelink firmware was flashed using the Firmware-Updater.exe from the stock firmware distribution (you must copy the exe to the freelink directory). The box must be restarted and the HG freelink firmware must be re-applied using the Firmware-Updater.exe from the HG freelink distribution. The IP address prior to this update will be retrieved by DHCP, as the box is in emergency mode and therefore shows up as "-EM" in the Firmware updater (using the Firmware-Updater.exe from the HG freelink distribution). Finally, after flashing and reboot, the IP address will be retrieved by DHCP by the debian system and you could telnet to it and proceed as described below.	+	Note: The HS-DGL300 was tested to be flushed to latest stock firmware for the HS (1.62, Jul 2008). After this the HG freelink firmware was flashed using the Firmware-Updater.exe from the stock firmware distribution (you must copy the exe to the freelink directory). The box must be restarted and the HG freelink firmware must be re-applied using the Firmware-Updater.exe from the HG freelink distribution. The IP address prior to this update will be retrieved by DHCP, as the box is in emergency mode and therefore shows up as "-EM" in the Firmware updater (using the Firmware-Updater.exe from the HG freelink distribution). Finally, after flashing and reboot, the IP address will be retrieved by DHCP by the debian system and you could telnet to it and proceed as described below. See also [http://buffalo.nas-central.org/forums/viewtopic.php?f=41&t=3553]

	'''2) ''' Flash The [[The LinkStation firmware flasher]]		'''2) ''' Flash The [[The LinkStation firmware flasher]]

Publicspam: /* Install FreeLink */

Publicspam — Wed, 09 Jul 2008 09:30:43 GMT

Install FreeLink

← Older revision		Revision as of 09:30, 9 July 2008
Line 25:		Line 25:
	\|}		\|}

		+	Note: The HS-DGL300 was tested to be flushed to latest stock firmware for the HS (1.62, Jul 2008). After this the HG freelink firmware was flashed using the Firmware-Updater.exe from the stock firmware distribution (you must copy the exe to the freelink directory). The box must be restarted and the HG freelink firmware must be re-applied using the Firmware-Updater.exe from the HG freelink distribution. The IP address prior to this update will be retrieved by DHCP, as the box is in emergency mode and therefore shows up as "-EM" in the Firmware updater (using the Firmware-Updater.exe from the HG freelink distribution). Finally, after flashing and reboot, the IP address will be retrieved by DHCP by the debian system and you could telnet to it and proceed as described below.

	'''2) ''' Flash The [[The LinkStation firmware flasher]]		'''2) ''' Flash The [[The LinkStation firmware flasher]]

Enzo: /* DHCP IP Address for LS2 */

Enzo — Tue, 12 Feb 2008 05:36:09 GMT

DHCP IP Address for LS2

← Older revision		Revision as of 05:36, 12 February 2008
Line 202:		Line 202:


-	== DHCP IP Address for LS2 ==	+	== DHCP IP Address for LS2 running the 2.4 Kernel==
-	The dhcp-client package that provides DHCP for LS2 does not work as some of the necessary values ~~for~~ the kernel are not predefined. So, instead of using dhcp-client, we ~~will be using~~ pump, which is ~~bot~~ a BOOTP and DHCP client written by RedHat.	+	The dhcp-client package that provides DHCP for LS2 does not work; as some of the necessary values in the 2.4 kernel are not predefined. So, instead of using dhcp-client, we can use pump, which is both a BOOTP and DHCP client written by RedHat.

	'''1)''' Uninstall dhcp-client:		'''1)''' Uninstall dhcp-client:

Enzo: /* DHCP IP Address for LS2 */

Enzo — Tue, 12 Feb 2008 05:32:59 GMT

DHCP IP Address for LS2

← Older revision		Revision as of 05:32, 12 February 2008
Line 211:		Line 211:
	apt-get install pump		apt-get install pump

-	'''3)''' Use the normal dhcp configuration in /etc/network/interfaces	+	'''3)''' Use the normal dhcp configuration in '''''/etc/network/interfaces''''' and '''''/etc/resolv.conf'''''

Enzo: /* DHCP IP Address for LS2 */

Enzo — Tue, 12 Feb 2008 05:30:40 GMT

DHCP IP Address for LS2

← Older revision		Revision as of 05:30, 12 February 2008
Line 203:		Line 203:

	== DHCP IP Address for LS2 ==		== DHCP IP Address for LS2 ==
-	The dhcp-client package that provides DHCP for LS2 does not work as some of the necessary values for the kernel are not predefined. So, instead of using dhcp-client, we will be using pump, which is a BOOTP/DHCP client written by RedHat.	+	The dhcp-client package that provides DHCP for LS2 does not work as some of the necessary values for the kernel are not predefined. So, instead of using dhcp-client, we will be using pump, which is bot a BOOTP and DHCP client written by RedHat.
		+
		+	'''1)''' Uninstall dhcp-client:
		+	apt-get remove dhcp-client
		+
		+	'''2)''' Install pump:
		+	apt-get install pump
		+
		+	'''3)''' Use the normal dhcp configuration in /etc/network/interfaces

Enzo: /* Static IP Address */

Enzo — Tue, 12 Feb 2008 05:23:29 GMT

Static IP Address

← Older revision		Revision as of 05:23, 12 February 2008
Line 200:		Line 200:
	[[Category:Hacking]]		[[Category:Hacking]]
	[[Category:FreeLink]]		[[Category:FreeLink]]
		+
		+
		+	== DHCP IP Address for LS2 ==
		+	The dhcp-client package that provides DHCP for LS2 does not work as some of the necessary values for the kernel are not predefined. So, instead of using dhcp-client, we will be using pump, which is a BOOTP/DHCP client written by RedHat.