Configuring gateway connections

About this task

Gateway connections are used to configure a gateway to establish a permanent control connection with another gateway. You can configure multiple gateway connections and must define a prefix for each connection parameter so that the gateway can find all required settings for each connection. If a gateway connection is down or cannot be reached, it tries to get connected as it must have a permanent connection.

for example
 Gateway.1.ConnectionType
 G2.ConnectionType

See the Notes in Configuring inbound connections for rules for defining prefixes.

Gateway connections are configured by using the following parameters:
ConnectionType
Defines the type of connection. Must be set to Gateway. For example: gateway.1.ConnectionType=Gateway.
DestinationAddress
Defines the IP address of the remote gateway that the connection is being made to. The gateway with this address must also be configured to accept inbound connections. This parameter is required.
DestinationPort
Defines the TCP port that the other gateway is listening on. This parameter is required.
BindTo
This parameter is optional. Use this parameter to configure the gateway to establish the outgoing gateway connection from a specific network interface. For example, if a firewall on the network is configured to allow only 1 of the gateway's interfaces through. Defines the IP address of the network interface through which the connections are made. For example: gateway.1.BindTo=192.168.74.1 Default is 0.0.0.0.
SourcePort
Defines the port that the outgoing gateway connections are using. This parameter is optional. Default is 0.
RetryDelay
Defines the time in seconds between attempts to establish the control connection. This parameter is optional. Default is 45 seconds.
KeepAlive
Defines the time in seconds between keepalive requests. This parameter is optional. Default is 900.
Timeout
The time, in seconds, to wait before a connection attempt is considered to be timed out. Default is 90.
Passphrase
Defines a secret passphrase if the remote gateway requires it for authentication. For security purposes, the passphrase is automatically encrypted when you start the gateway. For more information, see Automatic passphrase encryption.