NAME

telnetd − DARPA TELNET protocol server

SYNOPSIS

in.telnetd [−debug [ port ] ] [ −h ] [ −n ] [ −D (options | report | exercise | netdata | ptydata) ]

DESCRIPTION

in.telnetd is a server which supports the Internet standard TELNET virtual terminal protocol.  in.telnetd is invoked by the internet server [see inetd(1M)], normally for requests to connect to the TELNET port as indicated by the /etc/services file [see services(4)]. 

The −debug option can be used to start up in.telnetd manually, instead of through inetd(1M).  If started up in this manner, port may be specified to run in.telnetd on this alternate TCP port number. 

The -h option stops in.telnetd printing a login banner. 

The −D option can be used for debugging purposes.  This will allow telnet to print out debugging information to the connection, thus enabling the user to see what in.telnetd is doing.  Several modifiers are available for the debugging mode:

options prints information about the negotiation of the TELNET options,

report prints the options information, as well as some additional information about what processing is going on,

netdata displays the data stream received by in.telnetd,

ptydata displays data written to the pty, and

exercise has not been implemented yet. 

The in.telnetd command operates by allocating a pseudo-terminal device [see pty(4)] for a client, thereby creating a login process which has the slave side of the pseudo-terminal serving as stdin, stdout, and stderr.  The in.telnetd command will manipulate the master side of the pseudo-terminal by implementing the TELNET protocol and by passing characters between the remote client and the login process. 

When a TELNET session is started up, in.telnetd will send TELNET options to the client side which will indicate a willingness

•to do remote echo of characters,

•to suppress go ahead,

•to do remote flow control, as well as

•to receive terminal type information,

•to receive terminal speed information, and

•to receive window size information from the remote client. 

If the remote client is willing, the remote terminal type will be propagated to the environment of the created login process.  The pseudo-terminal allocated to the client will be configured to operate in “cooked” mode, with XTABS and CRMOD enabled [see termio(4)]. 

in.telnetd is willing to do: echo, binary, suppress go ahead, and timing mark.

in.telnetd is also willing to have the remote client do: linemode, binary1, terminal type, terminal speed, window size, toggle flow control, environment, X display location, and suppress go ahead. 

SEE ALSO

telnet(1), resolv.conf(4). 
RFC 854.

NOTES

Some TELNET commands are only partially implemented. 

Because of bugs in the original 4.2 BSD telnet(1), in.telnetd performs some dubious protocol exchanges to try to discover if the remote client is, in fact, a 4.2 BSD telnet(1). 

Binary mode has no common interpretation except between similar operating systems (UNIX in this case)

The terminal type name received from the remote client is converted to lower case. 

in.telnetd never sends TELNET go ahead commands. 

It is possible for in.telnetd to respond slowly when Domain Name Service is in place and the primary nameserver is unreachable or slow to respond. If your nameserver or network is heavily loaded, refer to the resolv.conf(4) man page for details on how to configure DNS under these conditions. 

  —  TCP/IP