HP (Hewlett-Packard) Digital NetRider Network Card User Manual


 
Configuring and Managing Interactive Devices 11-21
Configuring Individual Telnet Client Session Characteristics
Configuring Individual Telnet Client Session
Characteristics
Modifying Telnet Session Characteristics
You can modify the Telnet client session characteristics in two ways: at the port level
or for the individual session using the SET SESSION command. Modifying the
characteristics at the port level enables those values for Telnet client sessions at that
port when sessions are created. Also, you can save the characteristics in the permanent
database. The values you set with the SET SESSION command are lost once you log
out of the session.
Specifying ECHO Characteristics
The user can specify whether characters entered at the port device are echoed at the
access server (LOCAL) or at the remote Internet host (REMOTE). The factory-set
default is REMOTE. The Example: Specifying ECHO Characteristics shows how to
set ECHO CONTROL to LOCAL on port 5.
Example: Specifying ECHO Characteristics
Local> CHANGE PORT 5 TELNET CLIENT ECHO LOCAL
You can suppress local echoing by either selecting ECHO LOCAL and then selecting
the BINARY profile or by selecting ECHO LOCAL and then using the toggle ECHO
character (See Specifying ECHO Characteristics in this chapter).
Specifying the BINARY Characteristic
The BINARY characteristic allows the user to enable BINARY communication in
either one or both directions (to or from the Internet host). The TRANSMIT
characteristic enables BINARY communication in the access server to the Internet
host direction. The RECEIVE characteristic enables BINARY communication in the
Internet host to the access server direction. The DUPLEX characteristic enables
BINARY communication in both directions.
The following example shows how to enable BINARY communication in the transmit
direction on port 5:
Example: Enabling BINARY Characteristics
Local> CHANGE PORT 5 TELNET CLIENT BINARY TRANSMIT
Enabling the BINARY characteristic does some, but not all, of what a user might
require to send and receive BINARY files over the Telnet connection. For BINARY
transfers, you should use the BINARY profile instead of the BINARY characteristic.