Open topic with navigation

TIBCO ActiveSpaces® 4.8.0

# Configuration Options when the Proxy and Client are on Different Subnets

When the realm service and proxy are running on a subnet that is different from the one on which the client application is running, the proxy might need additional configuration. This is a requirement when you are dealing with a Network Address Translation (NAT) setup as is common with cloud environments or Docker.

For example, if the realm service and proxy are on subnet `10.0.75.0/24` and the ActiveSpaces client application is on the subnet `192.168.1.0/24`, the client application often cannot route to the `10.0.75.0/24` subnet (the proxy's subnet). In such a situation, in addition to `proxy_client_listen_port`, configure the `proxy_client_listen_external_host` option.

If the port that the proxy is listening on is mapped to a different external port, use `proxy_client_listen_external_port` to specify the correct external port.

Note: If you are in a dynamic environment, use the `-e <ip:port>` command-line parameter when you run the `tibdgproxy` process. For more information, see Starting a Proxy with an External Host and Port.
Subtopics

Copyright © 2009-2022. Cloud Software Group, Inc. All Rights Reserved.