Scenario 2 - Meshed Networks

Figure 1. Meshed networks


In this scenario the targets and controllers are distributed over several locations, all of which are protected by a firewall. The firewalls prevent the controllers from connecting directly to the target in remote locations, but they do allow the gateways to connect to gateways and gateways only, in remote locations. The existing HTTP Proxy servers, allow the targets to connect to the server.

In this scenario, all of the gateways have the same roles:

  • Create a control connection to the 3 other gateways.
  • Accept control connections from the 3 other gateways.
  • Accept requests from the controllers in the local network.
  • Locate endpoints in the local network.

Therefore the configuration file for the gateways will contain the following entries:

Inbound.1.ConnectionType = Inbound

Inbound.1.PortToListen = 8881

# Optional:

# Inbound.1.BindTo = 0.0.0.0

# Inbound.1.RetryDelay = 45

# Inbound.1.Passphrase =

Inbound.1.AllowGateways = true

Inbound.1.AllowEndpoints = true

Then for each of the gateways it has to connect to:

Gateway.X.ConnectionType = Gateway

Gateway.X.DestinationAddress = gatewayX_ipaddress

Gateway.X.DestinationPort = 8881

# Optional:

# Gateway.X.BindTo = 0.0.0.0

# Gateway.X.SourcePort = 0

# Gateway.X.RetryDelay = 45

# Gateway.X.KeepAlive = 900

# Gateway.X.Timeout = 90

# Gateway.X.Passphrase =

Endpoint.1.ConnectionType = Endpoint

# Optional

# Endpoint.1.SubnetAddress = 0.0.0.0

# Endpoint.1.SubnetMask = 0.0.0.0

# Endpoint.1.BindTo = 0.0.0.0

# Endpoint.1.SourcePort = 0

# Endpoint.1.Timeout = 90

In this scenario also, all of the gateways will be added to the server.