Specifications

Managing Remote Login
24-2
Rlogin Features
The following is a list of Rlogin features implemented in this release of the
Cabletron Network Access Software:
• Rlogin runs over TCP/IP. Once a TCP/IP connection to the target system is
established, the Rlogin client sends two frames to the Rlogin server. The first
consists of a null. The second contains the username at the client side, the
username at the server side, and the terminal type and speed. The server
responds with a request for the terminal window display size at the client side,
and then begins sending data (usually the banner a user sees once logged in).
The client side replies to the window size request, then starts transmitting data,
character by character.
• Rlogin conforms to all urgent data commands specified in RFC 1282, namely:
— Flush (02)
— RAW mode (10)
— COOKED mode (20)
— Request for window size (80)
• A Rlogin session operates in one of two modes. The Rlogin server controls
when the session is in RAW or COOKED mode. In RAW mode, all user input
is passed directly to the Rlogin server. In COOKED mode, the Access Server
processes XON/ XOFF flow control chargers (STOP is Ctrl/S and START is
Ctrl/Q) and does not pass them on to the Rlogin server. For this to work
properly, turn off the XON/ XOFF flow control on your terminal.
• Security Realm permissions added for Rlogin include RLOGIN and
NORLOGIN.
• Support for RADIUS-specified Rlogin sessions — If the login type is 1 (Rlogin)
or the vendor specific attribute (VSA) is detected, the user will see a Rlogin
session upon authentication.
• Existing port counters are used to indicate if data is lost while suspending
input to the Rlogin server.
• The meaning of the Access Server’s port setting of default protocol ANY is
extended to include Rlogin. The CONNECT command attempts to connect to
the server in this order: LAT, Telnet, and Rlogin.