Telnet in v2.3r63

Discussion in 'Cisco/Linksys Network Storage Devices' started by steve007, Nov 21, 2006.

  1. steve007

    steve007 LI Guru Member

    I just stumbled across this. I'm wondering if someone with more experience of the nslu2 can put this to good use to locate a telnet command.


    this seems to confuse the device into giving a dump of a file from the OS that among other things tells me this:
    no/etc/CGI_ds.confstatusaction/tmp/tmpfile.XXXXXXrt/etc/inetd.conftelnet_enablenetworkwttelnetdtelnet stream tcp nowait root /usr/sbin/telnetd /bin/mv -f %s %s 2>/dev/null/etc/rc.d/rc.xinetd

    Anyway, this got me thinking that telnet.cgi still actually exists. Truth is that it does seem to be there. If you try to use it in the same way as setup.cgi ie. by passing it a parameter it doesn't have an error.

    http://IPoftheNSLU2/Management/telnet.cgi - this causes an error implying that it has been removed, but

    http://IPoftheNSLU2/Management/telnet.cgi?enable=true - while not actually enabling it it proves that telnet.cgi is present and therefore if someone could locate telnet.cgi in the firmware download and see what parameters it is looking for maybe we could actually use telnet again...

    I look forward to anything anyone is able to find out about this. Good luck!
  2. jksmurf

    jksmurf Network Guru Member


    I was in a similar situation a while back and wrote up something on it, but not for R63 or R&2. Somoene else mentioned it was there but couldn't get it going.

    Have a wee look at this post, it might be of help to you to get it working with an older f/w.

  3. steve007

    steve007 LI Guru Member

    Thanks Tony, yes I'd read your posts (on this and my other thread) before posting mine. As I have this in an office situation (not just me using it) and need stability I really don't want to use anything other than the latest official release of the firmware so I'm loathe to go back to the older firmware.

    I'm hopeful that with the discovery we need to use parameters someone will work out how to do it - it seems to me that the original telnet.cgi did not require that.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice