Specifications

Configuring for Secure Telnet Sessions
6-22
Configuring for Secure Telnet Sessions
This section describes how to configure Secure Shell for secure Telnet sessions with a
RoamAbout R2. For additional information on Secure Shell, refer to Secure Telnet
Sessions on page 2-21. The following describes the Secure Shell parameters:
Host Key Type: The key type is RSA or DSA, along with the size of the key in bits,
which can be 512, 768, 1024, 2048, and 3072. Select the key type that is supported by
the SSH client applications, which will be connecting to the AP.
Generate New Host Key: Use this function to create a new host key. Be aware that it
will take several minutes to hours, depending on the size of the key, for the R2 to
generate a new key. During that time, the R2 will continue to function except that it
will not accept any additional management commands, such as a reset.
It may take a few minutes for an SSH application to connect to the AP when using a
larger key.
Idle Timeout: The maximum period of inactivity allowed before the session is
automatically logged out. The allowed values are 0-1440 minutes. A zero effectively
disables idle timeouts.
Authentication Timeout: The maximum period of inactivity between initiating the
session and entering the user name and password. The allowed values are 1-60
minutes.
Authentication Attempts: The maximum number of attempts to enter a correct
username and password before closing the session. The allowed values are 1 to 10.
If you generate a new key, you need to Reset With Current Settings to implement the key.
To enable or disable Secure Shell using the AP Manager, click on Interfaces in the main
window.
To enable or disable Secure Shell using the R2 console port, select Secure Shell from the
Main Menu. If creating a new certificate, select the host key type then choose Generate
Host Key at the bottom of the SSH configuration screen. You do not need to use Apply.
To enable or disable Secure Shell using the R2 web interface, open Secure Shell in the
navigation tree and click on SSH.
NOTE: The ability to connect to the R2 using Telnet can be disabled, as
described in Configuring the Console Port for Security on page 6-24.