1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

problems telnetting/ftping on wrt54g (newbie)

Discussion in 'Cisco/Linksys Wireless Routers' started by raahi108, Nov 28, 2004.

  1. raahi108

    raahi108 Network Guru Member

    Hi,

    1.

    I was trying to get the batbox distribution up on my WRT54G router. (Firmware version 2.02.7).
    I was successfully able to execute the WRT54G.sh script. (from the batbox distribution)

    -------------------------
    $ bash WRT54G.sh


    Installing to 192.168.1.1


    Making copy of receive tool

    Starting receive tool

    Sending bootstrap
    ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=10 tcp -> 192.168.1.1
    ttcp-t: socket
    ttcp-t: connect
    ttcp-t: 6713 bytes in 0.00 real seconds = 6555.66 KB/sec +++
    ttcp-t: 1 I/O calls, msec/call = 1.02, calls/sec = 1000.00
    ttcp-t: 0.0user 0.0sys 0:00real 0%
    Sending busybox
    ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=10 tcp -> 192.168.1.1
    ttcp-t: socket
    ttcp-t: connect
    ttcp-t: 1197410 bytes in 0.00 real seconds = 1169345.70 KB/sec +++
    ttcp-t: 147 I/O calls, msec/call = 0.01, calls/sec = 147000.00
    ttcp-t: 0.0user 0.0sys 0:00real 400%
    Sending distro.tar
    ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=10 tcp -> 192.168.1.1
    ttcp-t: socket
    ttcp-t: connect
    ttcp-t: 10239 bytes in 0.00 real seconds = 9999.02 KB/sec +++
    ttcp-t: 2 I/O calls, msec/call = 0.51, calls/sec = 2000.00
    ttcp-t: 0.0user 0.0sys 0:00real 0%
    Complete

    You may now telnet to 192.168.1.1
    You can connect a browser to http://192.168.1.1:8000/


    Administrator@mypc/batbox$
    --------------------------

    ===============================

    I also verified that the distribution was written to /tmp directory.
    (via a fake CLI interface to a WRT54G using the ping hack - by Mina Naguib)

    (--see logs at the end of the email---)


    the ping and traceroute utitlites on the router also works okie.
    I am able to use the wrt54g_put.sh script to put a file in the /tmp directory.

    But i am unable to telnet or use sscp/ftp to connect to the box.

    ----------
    Administrator@mypc/batbox$ telnet 192.168.1.1
    Trying 192.168.1.1...
    telnet: Unable to connect to remote host: Connection refused

    Administrator@mypc/batbox$
    -------------

    ~~~~~~~~~~~

    2.

    I am also facing problems using the linksys tftp utility.

    I am able to put files onto the router (I tried putting a dummy file , and
    it did successfully. But the router reloaded and possibly failed to load with that file (since it was just a dummy file) and hence loaded with the standard linksys image).

    Is it possible to put files onto router in the /tmp directory using this utility?
    Is it possible to get files from the router ? The utility supports a get command, but i was unable to get any files downloaded from the router.


    Thanks in advance,
    Raahi.



    ------LOGS------------
    WRT54G # ls -al /tmp/var
    drwxr-xr-x 1 0 0 0 Jan 1 2000 lock
    drwxr-xr-x 1 0 0 0 Jan 1 2000 log
    drwxr-xr-x 1 0 0 0 Jan 1 2000 run
    drwxr-xr-x 1 0 0 0 Jan 1 2000 tmp
    drwx------ 1 0 0 0 Jan 1 1970 spool
    drwxr-xr-x 1 0 0 0 Nov 28 00:07 bin
    drwxr-xr-x 1 0 0 0 Jan 1 2000 ..
    drwxr-xr-x 1 0 0 0 Jan 1 2000 .
    WRT54G # ls -al /tmp/var/bin
    -rwxr-xr-x 1 0 0 1197410 Nov 28 00:07 busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 cat -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 chmod -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 chroot -> /var/bin/busyb
    ox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 clear -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 cp -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 cut -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 date -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 dd -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 dmesg -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 echo -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 env -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 false -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 fgrep -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 find -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 free -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 ftpget -> /var/bin/busyb
    ox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 ftpput -> /var/bin/busyb
    ox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 grep -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 gunzip -> /var/bin/busyb
    ox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 gzip -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 head -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 httpd -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 hush -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 insmod -> /var/bin/busyb
    ox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 kill -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 ln -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 logger -> /var/bin/busyb
    ox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 ls -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 lsmod -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 mkdir -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 mknod -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 more -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 mount -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 mv -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 netstat -> /var/bin/busy
    box
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 ping -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 ps -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 pwd -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 reset -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 rm -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 rmdir -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 rmmod -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 sh -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 sleep -> /var/bin/busybo
    x
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 sort -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 strings -> /var/bin/busy
    box
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 syslogd -> /var/bin/busy
    box
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 tail -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 tar -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 telnetd -> /var/bin/busy
    box
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 test -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 top -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 true -> /var/bin/busybox

    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 umount -> /var/bin/busyb
    ox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 uptime -> /var/bin/busyb
    ox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 vi -> /var/bin/busybox
    lrwxrwxrwx 1 0 0 16 Nov 28 00:07 zcat -> /var/bin/busybox

    drwxr-xr-x 1 0 0 0 Jan 1 2000 ..
    drwxr-xr-x 1 0 0 0 Nov 28 00:07 .
    WRT54G #
    -----------------------------
     
  2. Syn0P

    Syn0P Guest

    I'm not sure about this, but do you have to change the WRT54G to Client mode as opposed to access point mode? If you haven't already, goto Wireless and then to Basic Settings and change it to client.

    I have no clue if this will help. (In fact, it probably won't....)
     
  3. raahi108

    raahi108 Network Guru Member

    Syn0p, it didn't help...
    Thnaks for the suggestion though.. :)-
     

Share This Page