Simple Yet Powerful Way
To Extend Your Reach!


When you have hundreds of servers and network equipments, how do you manage them? What about the devices that cannot be accessed via the Internet? For example, a router that only allows a modem or serial port connection?

We have incorporated a brand new "Jump-point" feature to Ch1.Gateway and Token2Shell to solve the problems!

Centralize address book management

The address book created and managed in Token2Shell is also used in Ch1.Gateway. It doesn't need to be modified or converted, you simply need to set "Home Folder Path" for Jump-point to Token2Shell's home folder. When Token2Shell connects to Ch1.Gateway server and requests jump-points, the server returns the address book entries stored under this jump-point home folder.

When the connected Token2Shell requests to open a jump-point, Ch1.Gateway connects to the host assigned to the entry using the specified default connection method (ex. SSH, serial port, modem or etc.), and relays data traffics over the SSH connection created between Ch1.Gateway and Token2Shell.

Seamless integration

Ch1.Gateway sends essential information such as keyboard mappings and terminal character code to Token2Shell when a jump-point is opened. The remote Token2Shell then automatically setup a session that seamlessly matches the original session profile stored in Ch1.Gateway.

Access serial ports and analog data modems over SSH connection

Ch1.Gateway supports all the connection methods found in Token2Shell which includes SSH, TELNET, TCP direct, serial port and analog data modem connections. If Token2Shell can connect to the device from where Ch1.Gateway server is installed, the server can also connect to that device and relay session data traffics over SSH connection.

Ch1.Gateway does not require Token2Shell to make the actual connections. However, for managing address book and checking the validity of host connection settings, we recommend installing and using Token2Shell with Ch1.Gateway. (Token2Shell is not a part of Ch1.Gateway software, thus requires a separate purchase.)

Improve security when accessing servers from mobile computers

When you have hundreds of servers to manage and need to connect to one of them while on the move, you need a local copy of the server information such as address book. What happens if you lost the notebook you've been using it for managing the servers?

Making a connection via Ch1.Gateway eliminates the need for keeping a local copy of the address book. Ch1.Gateway also hides the actual connection information such as host address and auto login info when Token2Shell requests to open a jump-point. Furthermore, the connection between Ch1.Gateway and jump-point enabled Token2Shell uses SSH2 protocol that encrypts data traffics.

Using Ch1.Gateway can minimize the risk of exposing important server administration information while giving you the flexibility of managing servers and network equipments from anywhere!

Virtual File System (SFTP)

If you wish to allow access for files and folders, simply enable "Virtual File System (SFTP)" service module and select a folder, "Home Folder Path", that will be used as a top level folder, i.e., "/". Once the service is activated, any SFTP client software can be used for accessing the files and folders.

Ch1.Gateway SFTP Folder Sample

Only the files and folders below the configured "Home Folder Path" will be accessible. To allow access to a folder that's not under the "Home Folder Path", create a shortcut for that folder under the "Home Folder Path". The shortcut will be presented as an actual folder to the connected client software.

File and folder access rights will be in line with the logged on user account, unless "Only allow read permission" option is enabled. If this option is enabled, all "write-related" requests will be denied even if the logged on user has that permission.

Port Forwarding

Ch1.Gateway supports SSH port forwarding. It can be used for providing secure access to the network resources behind firewall. Ch1.Gateway also supports "Server Preset Ports".

In typical SSH port forwarding usage scenario, a client software sends a request with destination host address and port number. This requires the user of the client software to exactly know about the destination host and configure the client software accordingly.

By using "Server Preset Ports", you can eliminate those steps. The end user simply needs to add an entry for Ch1.Gateway server. When the client software makes a connection to Ch1.Gateway server, it downloads port information and setup local port forwardings automatically. (To improve security and maximize the flexibility of network resource assignments, the information about the actual port forwarding destination host is hidden from the end user.)