Telnetting into NSLU2 Firmware V2.3_R72

Discussion in 'Cisco/Linksys Network Storage Devices' started by sluggo, Nov 30, 2006.

  1. sluggo

    sluggo Guest

    Hi all,


    I've just purchased a NSLU2 that's been upgraded to firmware version V2.3R72 and am having trouble telneting into it from linux. Haven't tried telnetting while loaded with any earlier firmware versions.

    I have no trouble accessing the features that are offered via web interface. However I wish to Unslung it and before doing so I want to know that I can telnet into it, just in case my first attempt to Unslung doesn't work (Unslung instructions are very clear in saying that the user should make sure they can telnet into the unit *before* making the attempt to Unslung, just in case there are complications).

    As I understand it from, the NSLU2 believes itself to have an ipaddress of for the first few seconds after first being turned on; it is during this time that attempts to gain access to gain Telnet access can be made at address

    However, immediately after hitting the 'on' switch', I hit 'return' on the line 'arping -f; telnet 9000' and get:

    [root@localhost andrew]# arping -f; telnet 9000
    connect: No such device
    telnet: connect to address No route to host
    telnet: Unable to connect to remote host: No route to host
    [root@localhost andrew]#

    So this doesn't get me far at all.

    If instead of doing the above I wait till the unit boots to the ipaddress that I've set ( and then enter the line 'arping -f; telnet 9000' I *do* at least get a response:

    [root@localhost andrew]# arping -f; telnet 9000
    ARPING from eth0
    Unicast reply from [00:04:5A:0F:DE:0B] 2.809ms
    Sent 1 probes (1 broadcast(s))
    Received 1 response(s)
    telnet: connect to address Connection refused
    telnet: Unable to connect to remote host: Connection refused
    [root@localhost andrew]#

    However no luck getting a RedBoot> prompt.

    So I'm wondering if there might be something that I'm doing wrong here, or is this to be expected with the Firmware Version V2.3_R72 ?


  2. spoonernash

    spoonernash LI Guru Member

    Your problem may be the space between the ip address and the 9000 port. I think you need a ":" there, ie: ipadress:port
  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