Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hello, I managed to install funplug via http://nas-tweaks.net/CH3SNAS:Tutorials/fun_plug and have tried to Telnet into the NAS with Putty as well as Absolute Telnet. Under Hostname I give the IP address of my NAs: 192.168.1.25 and select Telnet port 23. The terminal window briefly pops-up, but closes a second later. It gives me an error connection refused.
Does anyone have a suggestion?
Thanks.
JJ
Offline
Try checking the the FFP log file, to see if the telnet executable is starting correctly.
Offline
do you know that the ffp install was successful?
are you running ntpd ? This often crashes and I think with the default order of things it runs before telnetd - so when that crashes on startup telnetd is never loaded. I changed the running order on mine so telnet/sshd are always run before ntpd so a crash doesn't lock you out of terminal access
you can also try a port scan to see if port 23 is open, but yes, first check ffp.log
Last edited by luusac (2009-06-24 01:01:33)
Offline
Thanks. Here is the contents of my Log file:
tar: WARNING: Converting hard link to symlink
tar: WARNING: Converting hard link to symlink
tar: WARNING: Converting hard link to symlink
tar: WARNING: Converting hard link to symlink
tar: WARNING: Converting hard link to symlink
tar: WARNING: Converting hard link to symlink
tar: WARNING: Converting hard link to symlink
* OK
* Running /ffp/etc/fun_plug.init ...
* Running /ffp/etc/rc ...
* /ffp/start/syslogd.sh inactive
* /ffp/start/SERVERS.sh inactive
* /ffp/start/portmap.sh inactive
* /ffp/start/unfsd.sh inactive
* /ffp/start/nfsd.sh inactive
* /ffp/start/ntpd.sh inactive
* /ffp/start/LOGIN.sh inactive
* /ffp/start/telnetd.sh ...
Starting /ffp/sbin/telnetd -l /ffp/bin/sh
* /ffp/start/sshd.sh inactive
* /ffp/start/rsyncd.sh inactive
* /ffp/start/mediatomb.sh inactive
* /ffp/start/kickwebs.sh inactive
* /ffp/start/lighttpd.sh inactive
* /ffp/start/inetd.sh inactive
* OK
Does this mean thet Telnet is started and what else could be the problem?
Regards,
JJK
Last edited by jjk (2009-06-24 20:21:38)
Offline
it looks like the ffp.log hasn't been updated since ffp was installed. If you reboot the box there should be a new 'section' in the log with similar entries (-the warnings) appended to the end of the log. If that isn't there, i.e. if after shutdowns/reboots there are no new entries then maybe ffp is not running at all (check that fun_plug is still in the root and open it to check contents). If the entries are there then it could be a firewall between your machine and the 323 is blocking telnet. If you do a port scan then you will be able to see if port 23 is available (if not, then check for firewall and check to see if telentd is actually running). Is your nas on a static or dynamic IP? i.e. do you know for sure what the ip address is, if in doubt login to your router/switch/hub and see what the IP of the nas is. Have you looked at the ffp tutorial here http://dns323.kood.org/howto:ffp
Note the part where it says "To enable login for telnet, edit the telnetd.sh start script and remove the '-l /ffp/bin/sh' option. You can do this from the command line like this: ....."
my ffp log just says
* /ffp/start/telnetd.sh ...
Starting /ffp/sbin/telnetd
It doesn't make reference to the "-l /ffp/bin/sh" that yours does.
Last edited by luusac (2009-06-24 22:00:24)
Offline