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

No Telnet command inside the Busy Box ?

Discussion in 'HyperWRT Firmware' started by Tregge, May 23, 2005.

  1. Tregge

    Tregge Network Guru Member

    Hi all,
    first..sorry for my english.

    I own a WRT54G v. 2.2
    First i use Alchemy Firmware on it and there i can connect via telnet to the router and then connect with the telnet-command to the dsl-modem Xentrix. (i gave the routert a second ip with "ifconfig vlan1")

    After some tests with other firmwares, only HyperWRT and Linksys-Firmware work correctly.
    No way back to the former correctly working alchemy. Dont know why.

    But i like HyperWRT too, theres only one thing. The busy box don´t know the "telnet" command, which i use on alchemy , to connect to the modem.

    Has anyone an idea ?
  2. Guyfromhe

    Guyfromhe Network Guru Member

    you could copy the telnet executable from another distro onto it or see if it has netcat.
  3. Tregge

    Tregge Network Guru Member

    No Netcat.

    I think , the built-in Busy-Box is the Demo-version. and therefore no network commands. :-(
  4. littlewhoo

    littlewhoo Network Guru Member

    there is nothing like a Busy-Box Demo-version. If there is some stuff missing, Linksys (and therefore Hyperwrt) are probably just including a subset of the Busy-Box commands.

    You can either copy the whole busybox executable from Alchemy to Hyperwrt and create a link for telnet to this busybox version (it's big - I think about 1MB.
    Or you can try crosscompiling just Telnet for the MIPS platform.
  5. Tregge

    Tregge Network Guru Member

    can you please tell me where the busybox executable is located in the firmware ?

    think, i´ll find a way to destroy my WRT54G :mrgreen:
  6. littlewhoo

    littlewhoo Network Guru Member

    On Alchemy at /bin/busybox
  7. davidsonf

    davidsonf Network Guru Member

    Busybox is a program that includes a whole raft of the normal unix system utilities. When it is configured at compile time each utility can be separately included or excluded, hence with any given binary distribution you may or may not have any given utility. For utilities that are included, linking the appropriate filename to the busybox binary is the way they are accessed. But if it isn't compiled in, that will have no effect.

    There are two programs associated with telnet that are potentially part of the busybox binary, which is normally located in the /bin directory. The user program, "telnet",makes a connection from the host running it to another host. The "telnetd" system program must be running on the distant host. The telnetd program on the WRT54G is what allows you to telnet into the WRT54G.

    It happens that other telnetd programs can be compiled for the WRT54G too, and might in fact be prefered. I've stripped down another version, compiled it, and have it running on my WRT54G units. The reason I do that is because the standard telnetd binary cannot disable XON/XOFF flow control. (I don't much like the vi editor and have a small version of emacs running on my WRT54G, but it needs to disable XON/XOFF so that I can use ^S and ^Q.)

    If anyone wants either the source code or a binary for either
    the telnetd (a 51K binary) or the emacs (116K binary) I'd be happy to put them on my web site. I'm more or less in the final stages of polishing them up to make available anyway, so a beta tester or two might be useful.

Share This Page