Sponsored Content
Operating Systems HP-UX [SOLVED] Telnet timeout issue Post 302759031 by Tommyk on Monday 21st of January 2013 08:58:15 AM
Old 01-21-2013
[SOLVED] Telnet timeout issue

I have telnet configured in /etc/inetd.conf as below:

Code:
telnet       stream tcp6 nowait root /usr/lbin/telnetd  telnetd -b /etc/issue -n20

When i restart the service telnetd shows with only the -b option:

Code:
ps -ef|grep telnetd|grep -v grep
    root 24397     1  0 10:42:35 pts/ta    0:00 telnetd -b /etc/issue

When users try to connect via telnet they are only getting 2 seconds before being logged out of the terminal.

Can anyone point me in the right direction as to why the timeout is so short by default and why i can't set the "-n20" option to extend the timeout?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

telnet session timeout

hi, we can set something such that if the user has been idle for a while, it will auto disconnect. where to do so? thanks (6 Replies)
Discussion started by: yls177
6 Replies

2. UNIX for Dummies Questions & Answers

solaris telnet idle timeout

I have put TMOUT=1800;export TMOUT in the /etc/profile, put it does not work, by the way the root default shell is sh. but I wana every one including root to terminate the session after setting idle for 1800 seconds. thank for the help. (1 Reply)
Discussion started by: kahn630
1 Replies

3. AIX

how to change telnet timeout setting

Hi all Can any one solve my problem? I want to change the default timeout setting for telnet in aix, pls help me. (1 Reply)
Discussion started by: vjm
1 Replies

4. Solaris

Disable telnet timeout

Hi, Can someone help me how I can disable telnet timeout? I'm connecting remotely to some machines and after some time my telnet connection was closed. How can I disable this so that I'm always connected to those machines? Thanks! (2 Replies)
Discussion started by: ayhanne
2 Replies

5. Red Hat

telnet idle timeout on Redhat kernel 2.4.35.4

Hello, I've searched this forum for telnet idle timeout problem. I tried to set timeout parameters in /etc/profile readonly TMOUT=10 export TMOUT This doesn't work for Redhat kernel 2.4.35.4. It's really frustrating. Can anybody tell me what else I could try? Thanks a lot! jing (0 Replies)
Discussion started by: jing han
0 Replies

6. Forum Support Area for Unregistered Users & Account Problems

tinylogin telnet idle timeout

Hello, I have a busybox with tinylogin. How can I log user out when I found the telnet session is idle for 10 seconds? I set TMOUT=10 export TMOUT in /etc/profile I found it doesn't work for me. Can anybody help me? Thanks a lot! jing (1 Reply)
Discussion started by: jing han
1 Replies

7. Solaris

rlogin, telnet connections timeout

Hi, I have a Sun Ultra 5 desktop with Solaris 8. When I telnet/rlogin into any other host, the connection closes after few hours of inactivity. I also have another Windows box which I use rarely. But when I telnet/rlogin into the same hosts using putty, the connection stays for days without any... (5 Replies)
Discussion started by: dr_gsb
5 Replies

8. Linux

Telnet Timeout

is there a way to add a timeout parameter to telnet when connecting to any IP address? like, if this IP doesn't respond within 10 seconds, abort. thanks i'm looking for something like this: telnet gaggaga.com 443 -t 10 (3 Replies)
Discussion started by: SkySmart
3 Replies

9. IP Networking

TFTP Server Timeout issue

Hi, I'm running CentOS 5 as guest using VMware player. My host is Windows Xp. I'm running tftp server in CentOS. I have disabled firewall in both windows and CentOS. I use two different networks with different netmasks on CentOS. I'm able to ping the Centos (tftp server) from another Linux machine... (1 Reply)
Discussion started by: suryaemlinux
1 Replies

10. Shell Programming and Scripting

ping and telnet timeout

Hello, I need help, I have the following which save in the result file ping and telnet:port test. Basically the script works but I should implement a check on ping and telnet command so that ping has 5 seconds threshold and telnet (more important) 10 seconds. Over that threshold ping and... (0 Replies)
Discussion started by: marmellata
0 Replies
TELNETD(8)						    BSD System Manager's Manual 						TELNETD(8)

NAME
telnetd -- DARPA telnet protocol server SYNOPSIS
/usr/sbin/in.telnetd [-hns] [-a authmode] [-D debugmode] [-L loginprg] [-S tos] [-X authtype] [-edebug] [-debug port] DESCRIPTION
The telnetd program is a server which supports the DARPA telnet interactive communication protocol. Telnetd is normally invoked by the internet server (see inetd(8)) for requests to connect to the telnet port as indicated by the /etc/services file (see services(5)). The -debug option may be used to start up telnetd manually, instead of through inetd(8). If started up this way, port may be specified to run telnetd on an alternate TCP port number. The telnetd program accepts the following options: -a authmode This option may be used for specifying what mode should be used for authentication. Note that this option is only useful if telnetd has been compiled with support for authentication, which is not available in the current version. The following values of authmode are understood: debug Turns on authentication debugging code. user Only allow connections when the remote user can provide valid authentication information to identify the remote user, and is allowed access to the specified account without providing a password. valid Only allow connections when the remote user can provide valid authentication information to identify the remote user. The login(1) command will provide any additional user verification needed if the remote user is not allowed automatic access to the specified account. other Only allow connections that supply some authentication information. This option is currently not supported by any of the existing authentication mechanisms, and is thus the same as specifying valid. none This is the default state. Authentication information is not required. If no or insufficient authentication information is provided, then the login(1) program will provide the necessary user verification. off This disables the authentication code. All user verification will happen through the login(1) program. -D debugmode This option may be used for debugging purposes. This allows telnetd to print out debugging information to the connection, allowing the user to see what telnetd is doing. There are several possible values for debugmode: options Prints information about the negotiation of telnet options. report Prints the options information, plus some additional information about what processing is going on. netdata Displays the data stream received by telnetd. ptydata Displays data written to the pty. exercise Has not been implemented yet. -edebug If telnetd has been compiled with support for encryption, then the -edebug option may be used to enable encryption debugging code. -h Disables the printing of host-specific information before login has been completed. -L loginprg This option may be used to specify a different login program. By default, /bin/login is used. -n Disable TCP keep-alives. Normally telnetd enables the TCP keep-alive mechanism to probe connections that have been idle for some period of time to determine if the client is still there, so that idle connections from machines that have crashed or can no longer be reached may be cleaned up. -s This option is only enabled if telnetd is compiled with support for SecurID cards. It causes the -s option to be passed on to login(1), and thus is only useful if login(1) supports the -s flag to indicate that only SecurID validated logins are allowed. This is usually useful for controlling remote logins from outside of a firewall. -S tos Sets the IP type-of-service (TOS) option for the telnet connection to the value tos. -X authtype This option is only valid if telnetd has been built with support for the authentication option. It disables the use of authtype authentication, and can be used to temporarily disable a specific authentication type without having to recompile telnetd. If the file /etc/issue.net is present, telnetd will display its contents before the login prompt of a telnet session (see issue.net(5)). Telnetd operates by allocating a pseudo-terminal device (see pty(4)) for a client, then creating a login process which has the slave side of the pseudo-terminal as stdin, stdout, and stderr. Telnetd manipulates the master side of the pseudo-terminal, implementing the telnet proto- col and passing characters between the remote client and the login process. When a telnet session is started up, telnetd sends telnet options to the client side indicating a willingness to do the following telnet options, which are described in more detail below: DO AUTHENTICATION WILL ENCRYPT DO TERMINAL TYPE DO TSPEED DO XDISPLOC DO NEW-ENVIRON DO ENVIRON WILL SUPPRESS GO AHEAD DO ECHO DO LINEMODE DO NAWS WILL STATUS DO LFLOW DO TIMING-MARK The pseudo-terminal allocated to the client is configured to operate in cooked mode, and with XTABS CRMOD enabled (see tty(4)). Telnetd has support for enabling locally the following telnet options: WILL ECHO When the LINEMODE option is enabled, a WILL ECHO or WONT ECHO will be sent to the client to indicate the current state of terminal echoing. When terminal echo is not desired, a WILL ECHO is sent to indicate that telnetd will take care of echo- ing any data that needs to be echoed to the terminal, and then nothing is echoed. When terminal echo is desired, a WONT ECHO is sent to indicate that telnetd will not be doing any terminal echoing, so the client should do any terminal echoing that is needed. WILL BINARY Indicates that the client is willing to send a 8 bits of data, rather than the normal 7 bits of the Network Virtual Termi- nal. WILL SGA Indicates that it will not be sending IAC GA, go ahead, commands. WILL STATUS Indicates a willingness to send the client, upon request, of the current status of all TELNET options. WILL TIMING-MARK Whenever a DO TIMING-MARK command is received, it is always responded to with a WILL TIMING-MARK WILL LOGOUT When a DO LOGOUT is received, a WILL LOGOUT is sent in response, and the TELNET session is shut down. WILL ENCRYPT Only sent if telnetd is compiled with support for data encryption, and indicates a willingness to decrypt the data stream. Telnetd has support for enabling remotely the following TELNET options: DO BINARY Sent to indicate that telnetd is willing to receive an 8 bit data stream. DO LFLOW Requests that the client handle flow control characters remotely. DO ECHO This is not really supported, but is sent to identify a 4.2BSD telnet(1) client, which will improperly respond with WILL ECHO. If a WILL ECHO is received, a DONT ECHO will be sent in response. DO TERMINAL-TYPE Indicates a desire to be able to request the name of the type of terminal that is attached to the client side of the con- nection. DO SGA Indicates that it does not need to receive IAC GA, the go ahead command. DO NAWS Requests that the client inform the server when the window (display) size changes. DO TERMINAL-SPEED Indicates a desire to be able to request information about the speed of the serial line to which the client is attached. DO XDISPLOC Indicates a desire to be able to request the name of the X windows display that is associated with the telnet client. DO NEW-ENVIRON Indicates a desire to be able to request environment variable information, as described in RFC 1572. DO ENVIRON Indicates a desire to be able to request environment variable information, as described in RFC 1408. DO LINEMODE Only sent if telnetd is compiled with support for linemode, and requests that the client do line by line processing. DO TIMING-MARK Only sent if telnetd is compiled with support for both linemode and kludge linemode, and the client responded with WONT LINEMODE. If the client responds with WILL TM, the it is assumed that the client supports kludge linemode. Note that the [-k] option can be used to disable this. DO AUTHENTICATION Only sent if telnetd is compiled with support for authentication, and indicates a willingness to receive authentication information for automatic login. DO ENCRYPT Only sent if telnetd is compiled with support for data encryption, and indicates a willingness to decrypt the data stream. issue.net(5)). FILES
/etc/services, /etc/issue.net SEE ALSO
telnet(1), login(1), issue.net(5), STANDARDS
RFC-854 TELNET PROTOCOL SPECIFICATION RFC-855 TELNET OPTION SPECIFICATIONS RFC-856 TELNET BINARY TRANSMISSION RFC-857 TELNET ECHO OPTION RFC-858 TELNET SUPPRESS GO AHEAD OPTION RFC-859 TELNET STATUS OPTION RFC-860 TELNET TIMING MARK OPTION RFC-861 TELNET EXTENDED OPTIONS - LIST OPTION RFC-885 TELNET END OF RECORD OPTION RFC-1073 Telnet Window Size Option RFC-1079 Telnet Terminal Speed Option RFC-1091 Telnet Terminal-Type Option RFC-1096 Telnet X Display Location Option RFC-1123 Requirements for Internet Hosts -- Application and Support RFC-1184 Telnet Linemode Option RFC-1372 Telnet Remote Flow Control Option RFC-1416 Telnet Authentication Option RFC-1411 Telnet Authentication: Kerberos Version 4 RFC-1412 Telnet Authentication: SPX RFC-1571 Telnet Environment Option Interoperability Issues RFC-1572 Telnet Environment Option BUGS
Some TELNET commands are only partially implemented. Because of bugs in the original 4.2 BSD telnet(1), 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. Telnetd never sends TELNET IAC GA (go ahead) commands. The source code is not comprehensible. Linux NetKit (0.17) December 29, 1996 Linux NetKit (0.17)
All times are GMT -4. The time now is 04:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy