How to use telnetd

[Rahul Jain]

For me, telnetd gives the following options:

# telnetd --help
BusyBox v1.2.2 (2007.03.11-00:56+0000) multi-call binary

Usage: telnetd (inetd mode) [OPTION]

Telnetd uses incoming TELNET connections via inetd.
Options:
        -l LOGIN        exec LOGIN on connect (default /bin/sh)
        -f issue_file   Display issue_file instead of /etc/issue


The problem is that I cannot recompile busybox, I have to use
MontaVista Dev Rocket and so am stuck with the RPM package that is
provided by MontaVista. However, I got ssh to work so it is not
necessary for me to get telnet to work.

Thanks for the help though, I wish I could have compiled busybox in stead. :)

Cheers
Rahul Jain

On Mon, Aug 4, 2008 at 11:01 PM, Denys Vlasenko
<vda.linux at googlemail.com> wrote:
> On Monday 04 August 2008 10:03, Rahul Jain wrote:
>> Hi,
>>
>> I am a bit confused about telnetd which is provided by busybox. I want
>> to run it as a daemon on my virtual machine so that I can access my
>> virtual machine from my host machine. However, each time I type
>> telnetd I am presented with the following login screen, where if can
>> login as root. (I do not have a user on my virtual machine.)
>>
>> # telnetd
>> ����������
>>
>> MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774)
>> Linux/armv5tejl 2.6.18_pro500-versatile926ejs
>>
>> 10.0.2.15 login: root
>
> Looks like you didn't set CONFIG_FEATURE_TELNETD_STANDALONE=y
> in your .config when you built busybox, and thus your telnetd
> lacks daemon mode. It always runs as inetd service.
>
>> However, this is not what I want.  So, if someone could tell me how to
>> use telnet as a daemon, it would be helpful.
>
> telnetd itself can be of help:
>
> # telnetd --help
> BusyBox v1.12.0.svn (2008-07-24 06:16:59 CEST) multi-call binary
>
> Usage: telnetd [OPTION]
>
> Handle incoming telnet connections
>
> Options:
>        -l LOGIN        Exec LOGIN on connect
>        -f issue_file   Display issue_file instead of /etc/issue
>        -K              Close connection as soon as login exits
>                        (normally wait until all programs close slave pty)
>        -p PORT         Port to listen on
>        -b ADDR         Address to bind to
>        -F              Run in foreground
>        -i              Run as inetd subservice
>
> Recompile busybox with CONFIG_FEATURE_TELNETD_STANDALONE=y,
> and it will stop behaving as if -i is always specified.
> --
> vda
>