Your browser does not allow storing cookies. We recommend enabling them.


Connecting via Different TCP/IP Stacks with Tectia Clients

Note that running multiple Tectia clients simultaneously under the same user ID using different TCP/IP stacks will not work, because they use the same run-on-demand Connection Broker. The Connection Broker opens a socket on a particular TCP/IP stack; the clients (sftpg3, scpg3, sshg3) use local UNIX sockets to the Connection Broker.

If you want the clients to open connections to particular stacks, you have to run separate Connection Brokers on each stack, defined using the _BPXK_SETIBMOPT_TRANSPORT environment variable:

> env _BPXK_SETIBMOPT_TRANSPORT=TCPIPB ssh-broker-g3 -a /tmp/ssh-usernameB/ssh-broker

The ssh-broker-g3 option -a starts the Connection Broker so that it listens to the Connection Broker connections on the local address /tmp/ssh-usernameB/ssh-broker. If the /tmp/ssh-usernameB/ directory does not already exist, you have to first create it:

> mkdir /tmp/ssh-usernameB

If you want to set the TCP/IP stack permanently, you can do it by setting the _BPXK_SETIBMOPT_TRANSPORT environment variable to the stack name in the client's .profile file.

Use the SSH_SECSH_BROKER environment variable to point to the UNIX socket the Connection Broker is listening on:

> env SSH_SECSH_BROKER=/tmp/ssh-usernameB/ssh-broker sshg3 User@Server

You can use the netstat command to display all active connections for TCPIPB:

> netstat -a -p TCPIPB




What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.

    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH

    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now