Skip to main content

​
Part II — Install and operate DataRelay Link

The latest published stable release is v2.3.0. This site documents the v2.4.0 development target. For stable deployment use the immutable stable release. For v2.4 testing use an exact qualified SHA or candidate artifact.

​
6. Prepare the Ubuntu host

Review OCI Security Lists/NSGs and the Ubuntu host firewall deliberately. Do not flush firewall chains merely to make DataRelay Link work.

​
7. Install the Server

Continue with Server Installation. For a v2.4 candidate, use the exact source or artifact identity provided by qualification. For this OCI topology, Enterprise single-443 is usually the simplest public exposure model:
If Fixed TCP is enabled, expose only the separately configured Fixed TCP endpoint pool actually required.

​
8. Verify the Server

Confirm the role is DRLink Server and product version, release channel, exact Source HEAD, and Relay Engine version are truthful.

​
9. Verify reboot persistence

Reboot the OCI VM and verify the same Server identity, control-plane state, listener topology, and diagnostics return without rebuilding configuration.

​
10. Enroll the first Managed Host

On the Server:
Run the generated one-time command on the target host. Then verify on that Agent Host:
Create the first Remote Service on the Agent Host:
Remote Access policy is configured separately on the Server if the endpoint should be restricted.

​
Final checklist

  • OCI VCN, Internet Gateway, route, and public subnet are ready
  • Reserved Public IPv4 is attached
  • SSH administration is restricted appropriately
  • only listeners required by the selected deployment mode are public
  • internal single-443 backends are not publicly exposed
  • Server reports the correct role/version/source identity
  • system diagnostics has no blocking finding
  • state survives reboot
  • first Managed Host enrolls with Zero-Touch
  • Agent-owned Remote Service receives an endpoint and works
  • optional Remote Access policy is tested separately from runtime health

​
Next steps

Remote Services

Create local or LAN TCP/Fixed TCP connectivity on an Agent Host.

Remote Access

Authorize use of existing Remote Services.

Firewall & NAT

Review Direct and single-443 exposure.

Quick Start

Follow the current v2.4 Managed Host workflow.

​
Official OCI references

Last modified on September 24, 2026