Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.


Running SOCKS Proxy

The SOCKS Proxy component consists of two processes:

  • ssh-socks-proxy: the Tectia SOCKS Proxy process that needs to be running before transparent tunneling connections can be made. The process can be started under USS, or by using a JCL script or started task.

  • ssh-socks-proxy-ctl: control process for the SOCKS Proxy. It can be used, for example, to view the status of the SOCKS Proxy, to reconfigure or stop the SOCKS Proxy, or to load private keys to memory.

In addition to the processes, there is an init script for re/starting and stopping the ssh-socks-proxy process:

> /opt/tectia/etc/init.d/ssh-socks-proxy

The script takes commands start, restart, stop and version. For example to force the SOCKS Proxy to stop, run:

> /opt/tectia/etc/init.d/ssh-socks-proxy stop

Once the script is defined in the JCL procedure for SSHSP (see Running ssh-socks-proxy as a Started Task), you can also run it with operator commands. For example to query the version of the SOCKS Proxy, you can run command:

== > s SSHSP, f=version