Loading ...
Loading ...
Loading ...
102
6. SSH Tunnels and SDT Connector
6.1 Configuring for SSH Tunneling to Hosts
To set up the console server for SSH tunneled access a network attached host:
• Add the new host and the permitted services using the Serial & Network: Network Hosts menu as detailed in section 4.4
Network Hosts. Only these permitted services will be forwarded by SSH to the host. All other services (TCP/UDP ports) will
be blocked.
Note: Some TCP Ports used by SDT in the console server include:
22 SSH (All SDT tunneled connections)
23 Telnet on local LAN (forwarded inside tunnel)
80 HTTP on local LAN (forwarded inside tunnel)
3389 RDP on local LAN (forwarded inside tunnel)
5900 VNC on local LAN (forwarded inside tunnel)
73XX RDP over serial from local LAN – where XX is the serial port number (i.e. 7301 to 7348 on a 48-port console server)
79XX VNC over serial from local LAN – where XX is the serial port number
• Add new Users using the Serial & Network: Users & Groups menu as detailed in 4.4 Network Hosts. Users can
be authorized to access the console server ports and specified network-attached hosts. To simplify configuration, the
Administrator can first set up Groups with group access permissions, then assign Users to those Group(s).
6.2 SDT Connector Client Configuration
The SDT Connector client works with all Tripp Lite console servers. Each of these remote console servers have an embedded
OpenSSH-based server, which can be configured to port forward connections from the SDT Connector client to hosts on
their local network, as detailed in the previous chapter. The SDT Connector can also be pre-configured with access tools and
applications available to be run when access to a particular host has been established.
SDT Connector can connect to the console server using alternate OOB access. It can also access the console server itself and
access devices connected to serial ports on the console server.
Loading ...
Loading ...
Loading ...