Posts Tagged ‘reverse ssh’

A Console Server with Reverse SSH Capabilities Provides Additional Options for Out-of-Band Communication

Friday, May 1st, 2015

In most out-of-band management applications, a console server is connected to a secondary network, cellular router or wireless router and deployed at a remote site in order to allow remote access to console port command functions when primary network communication is not available. This works well in most cases, but if out-of-band access via both Ethernet and console port is required, a console server that supports reverse SSH connections can be used in place of a basic console server.


Communicating with Devices on an Isolated LAN via Reverse SSH

Tuesday, April 28th, 2015

Isolated LANs are often found in applications where either the remote nature of the site makes contact via outside network impractical and in applications where an outside network connection to the LAN might jeopardize network security. In cases like this, one of the few options for outside maintenance access to devices on the isolated LAN is often a console server that supports both dial-up access and the ability to create reverse SSH connections.


Using Reverse SSH to Manage Remote Network Elements

Monday, April 20th, 2015

In addition to providing a secure, encrypted alternative to Telnet communication, SSH (or Secure Shell Protocol,) can also be used for communication with remote devices located at distant network equipment facilities. Reverse SSH commands can simplify the process of communicating with devices protected by firewalls and also allow communication with isolated LAN segments that are normally only accessible via dial-up or local command port.


A Console Access Server with Outbound SSH/Telnet Support Provides More Alternatives for Communication

Tuesday, April 26th, 2011

In out of band management applications that rely on a console access server ( for communication with remote network devices, reverse/outbound SSH/Telnet can be an extremely useful feature. In addition to providing a means to communicate with other network devices, outbound SSH/Telnet is also extremely handy in cases where an equipment rack is not connected to your main network, and the only way to communicate with devices in the rack is via dial-up or satellite modem.


Why Does a Console Server Need Outbound SSH or Outbound Telnet Capabilities?

Monday, June 14th, 2010

A console server that provides secure, remote access is key element in managing your network efficiently and effectively. What happens, though, when the router goes down and the console port cannot be accessed via IP? If your serial console server includes outbound SSH or outbound Telnet capabilities this provides yet another way to maximize up-time of network devices and to ensure that there will be less time when the network devices cannot be accessed.

Consider the following situation …