Skip to content

Lantronix Terminal Application

The Lantronix Control Center provides a full-featured native Terminal Application for interaction with Local Managers. The Terminal Application can be used to perform SSH, Dial, and Terminal operations. When configured, it can also automatically dial a Local Manager via its out-of-band connection.

Lantronix Control Center - Terminal App

Desktop Requirements

The Terminal Application installs as a standard Windows application on the local desktop computer. You must download and execute the native installer, on your local desktop, before the Terminal Application will launch.

Launch the Terminal Application by clicking the chevron next to the SSH button and selecting the Open native terminal option on the SSH menu.

The first time you launch the Terminal Application, you will see the following notice:

Routing Requirements

Since the Terminal Application runs locally from the user's workstation, a valid networking route must be available to SSH directly to the Local Manager. The SSH session does not originate from the Control Center by default, so even if the Control Center and Local Manager are communicating successfully, the workstation still needs to be able to route directly to the Local Manager.

To solve many routing issues, Reverse-SSH tunnels (RSSH) on the Control Center is enabled by default. When RSSH is configured, the Terminal Application client first attempts to connect using RSSH. If that fails, the Terminal Application falls back to directly connecting to the Local Manager.

No Route to Host

In cases where network configuration will not allow for direct routing, a SOCKS Proxy can be used to route the SSH session. The Terminal Application can automatically connect to the SOCKS Proxy and then initiate the connection to the Local Manager. See SS5 SOCKS Proxy for more information.

Non-Routable Networks

If the target Local Manager is behind a NAT, it will still report its private IP address to the Control Center. Upon launching the Terminal Application, the SSH session will be opened to the private address, and the connection will fail. You can configure Properties to override the Local Manager's IP address with a new one. Properties can be configured on the LM CLI or on the Control Center under Local Manager Summary > System > Properties.

The following properties are available:

  • sshIp - This property will override the reported IP address when initiating an SSH connection with the Terminal Application. For example, if the Local Manager's IP is 192.168.1.14, but sshIp is configured as 75.125.200.98, clicking on SSH will open connection to 75.125.200.98. Useful if an appliance is behind a firewall or NAT.

  • sshPort - This property overrides the default port 22 for SSH connections. Useful if the Local Manager is behind a router with port forwarding capabilities.

  • sshIpv6 - Specifies an alternate IPv6 address to be used instead of the address reported by the Local Manager.

  • sshIpOob - This property will override the reported Out of Band IP address. Useful if an appliance ends up behind a firewall or NAT when it brings up its out of band connection.

  • sshPortOob - This property overrides the default port 22 for SSH connections while the Local Manager is operating Out of Band.

  • sshIpv6Oob - Specifies an alternate IPv6 addressed to be used when the Local Manager is operating Out of Band.

Features

The Terminal, Edit, and More menus in the Terminal Application provide access to additional functionality.

Terminal

Connect - Connects to the Local Manager. Can be used after Disconnect or during an active session to restart it.

Forward - Provides forwarding of remote serial ports to local TCP ports on the workstation. For example, Port 1/1 could be forwarded to port 20001 of 127.0.0.1 (localhost). The terminal session would then be accessible by opening a Telnet connection to 127.0.0.1 on port 20001. This feature is used most often with GUI applications that require terminal access to managed devices.

Reset - If the CLI text becomes garbled during interaction with a managed device, use the Reset command to reset the terminal session.

Disconnect - Disconnects the current session.

Edit

Copy - Copies text to the clipboard.

Paste - Pastes text from the clipboard.

More

Preferences - Configure Terminal Application preferences.

  • Appearance - Change the font, style, size, and color of the Terminal text.
  • Logging - Enable debug and session logging.
  • Scrolling - Specify the buffer size for scrollback.
  • Private Key - Configure an SSH key for authentication.

About - Displays application version and other details.

Usage

The Terminal Application installs as a standard Windows application, on the local desktop computer. The installer is signed by a valid extended-verification (EV) certificate.

Users can download the Windows Installer (MSI) from their profile page on the CC.

Lantronix Control Center - Terminal App Download

Once installed, the terminal app will launch when a UNLP (or JNLP) file is downloaded and opened after clicking the SSH, Dial, or Terminal button on the CC.

To view your history of recent connections, launch the Terminal App from Windows. Double click on past connections to relaunch a session.

Lantronix Control Center - Terminal App Download

A custom protocol (unlp://) is also configured to launch the terminal app from a web browser without downloading a file.

UNLP as default terminal launch for all CC users

By default the CC will launch the native terminal application using the custom unlp:// protocol. You can view the Terminal Launch setting on the Control Center Administration page.

Lantronix Control Center - Terminal App UNLP Default

You can change the default terminal launch setting for all CC users by editing /etc/sysconfig/embassy.overrides. Please contact Lantronix Support if you have questions about changing this setting.