6.2. Tunnelling - One Firewall Closed
Prev Chapter 6. Tunnelling Scenarios Next

6.2. Tunnelling - One Firewall Closed

Tunnel Scenario 3 - Data source firewall ports closed, read-only

Primary Use  Securely access OPC UA, DA, or A&E data from outside the control network, without VPNs (monitoring only).

Configuration Configuration
OPC Client: Configure this DataHub instance as an OPC client to the OPC server.  OPC Server: Configure this DataHub instance as an OPC server for the OPC client.
Tunnel Slave: Configure this DataHub instance as a Tunnel slave, so that it initiates the connection.  Tunnel Master: Configure this DataHub instance as a Tunnel master, to receive connections.
Data Flow Direction:
Write-only
When Connection Initiated:
Override Master's values with mine
When Connection Lost:
Mark Master's data “not connected”
  

See also Tunnelling Security - Best Practices.

Tunnel Scenario 4 - Data source firewall ports closed, read/write

Primary Use  Securely access and write back to OPC UA, DA, or A&E data from outside the control network, without VPNs (monitoring and supervisory control).

Configuration Configuration
OPC Client: Configure this DataHub instance as an OPC client to the OPC server.  OPC Server: Configure this DataHub instance as an OPC server for the OPC client.
Tunnel Slave: Configure this DataHub instance as a Tunnel slave, so that it initiates the connection.  Tunnel Master: Configure this DataHub instance as a Tunnel master, to receive connections.
Data Flow Direction:
Read/Write
When Connection Initiated:
Override Master's values with mine
When Connection Lost:
Mark Master's data “not connected”
  

See also Tunnelling Security - Best Practices.

Prev Up Next
Chapter 6. Tunnelling Scenarios Home 6.3. Tunnelling - Both Firewalls Closed, with DMZ