rtelnet

SOCKS client version of telnet

Syntax:

rtelnet [-8] [-a] [-D] [-d] [-e escape_char] 
        [-n tracefile] [[-l user] host [port]]

Options:

-8

Allow an eight-bit input data path at all times. Without this option, parity bits are stripped whenever the remote side's stop and start characters are ^S and ^Q.

-a

Attempt automatic login. Currently, this sends the username via the USER variable of the ENVIRON option if supported by the remote system. The name used is that of the current user (as returned by getlogin()) if that name agrees with the current user ID. Otherwise, the name used is the one associated with the user ID.

-D

Disable telnet escape character.

-d

Enable debugging.

-e escape_char

Set the initial telnet escape character to escape_char (default is Ctrl -] ). This character lets you switch to telnet's command mode.

-l user

When connecting to the remote system, if the remote system understands the ENVIRON option, send user to the remote system as the value for the variable USER. This option implies the -a option and may may also be used with the open command.

-n tracefile

Record trace information in the specified file.

host

The official name, an alias, or the Internet address of a remote host.

port

A port number (address of an application). If a number isn't specified, the default telnet port is used.

Description:

The rftp and rtelnet utilities provide the well-known functionalities to hosts within a firewall. Normally, when a firewall is constructed, IP-accessibility across the firewall is cut off to reduce security risk to hosts within the firewall. As a result, inside hosts can no longer use many of the well-known tools directly to access the resources outside the firewall.

These utilities restore the convenience of the well-known tools while maintaining the security requirement. Though the utilities differ very much from their counterparts in the use of the communication scheme, they should behave almost indistinguishably to the users.

These are ``versatile'' clients - they can be used for connections to inside hosts directly and to outside hosts via SOCKS proxy servers. So they can be used as replacements of their traditional counterparts.

When rtelnet starts, it prints to stderr its version number and the name or IP address of its default SOCKS proxy server. It then consults the configuration file (/etc/socks.conf) to determine whether a request should be allowed or denied based on the requesting user, the destination host, and the requested service.

For allowable requests, the configuration file also dictates whether direct or proxy connection should be used to the given destination, and optionally the actual SOCKS servers to use for the proxy connection. See socks.conf.

You can use the environment variable SOCKS_NS to set the nameserver for domain name resolutions. Be sure you use the IP address of the nameserver you want to use, not its domain name. If SOCKS_NS doesn't exist, the IP address defined by the symbol SOCKS_DEFAULT_NS at compile time is used if the programs were compiled with that symbol defined. Otherwise the nameservers specified in /etc/resolv.conf are used.

All the client processes log their activities using syslog() with facility daemon and level notice.

Although sockd (the Unix SOCKS server) isn't shipped with the QNX TCP/IP implementation, you'll find a free (unsupported) version in the TCP/IP area on QUICS.

Environment variables:

SOCKS_SERVER

If defined, specifies the name or IP address of the SOCKS proxy server host to use, overriding the default server compiled into the programs.

SOCKS_NS

If defined, specifies the IP address of the domain nameserver that should be used for name resolution, overriding both the definition of symbol SOCKS_DEFAULT_NS and the file /etc/resolv.conf.

See also:

telnet