Enabling Telnet

Before you even try this, please be WARNED that using telnet to your DNS-323 you can very easily <hi #ffff00>brick</hi> your unit.

The first thing you need to do is to create a fun_plug. The minimum fun_plug for telnet access looks like this:

#
# Minimal fun_plug, only enables telnet
#
# Requires: /mnt/HD_a2/starttelnet.sh
#           /mnt/HD_a2/lnx_bin/busybox3
#           /mnt/HD_a2/lnx_bin/utelnetd
#
 
#
# Uncomment next line if you want "proof of concept". 
# A filem dmesg.out will be located on \\NAS\HDD_1 or 
# \\NAS\Volume_1 depnding on firmware version.
#
# dmesg > /mnt/HD_a2/dmesg.out
 
#
# Start the telnet deamon
#
/mnt/HD_a2/starttelnet.sh

Next step is to dowload the files required KRH kindly provided them for us and you can now download them from here: utelnet-kit.tar.gz. For Windows Users: Dont use WinZIP - try WinRAR instead

From this file, extract the following files:

• starttelnet.sh
• utelnetd
• busybox3

When all files are extracted you need to install them. This can be achieved in several ways covered in the fun_plug howto. The most important is that the files resides on the first disc and in the following structure and that they have rights to execute.

  ./fun_plug
  ./starttelnet.sh
  ./lnx_bin/utelnetd
  ./lnx_bin/busybox3

Note that '.' represents \\NAS\HDD_1 on a 1.01 unit and \\NAS\Volume_1 on a 1.02/1.03 unit.

The final touch of this is a reboot of your DNS-323. When the unit has started up you should have telnet access. Recommended client for Windows is PuTTY

So; now you have a telnet access and want to do something with it. Maybe a debian Sarge chroot system. Upgrade your iTunes server or make your ftp server working in a NAT'ed environment. You can even set-up your own WEB server using lighttpd.

But remember, always have fun, , and be aware that you're now in a position where you can easily <hi #ffff00>brick</hi> your unit.