Publishing Services
A Service is one TCP target that an enrolled client publishes through the Data Relay Link server. One client can publish one service or many.The universal service path
The target can be on the client itself or on another LAN host the client can reach.Common service types
Pattern 1 — publish the client’s own SSH
Typical target:Pattern 2 — one client, multiple local services
Each service gets its own stable Service ID and persistent public-port reservation.Pattern 3 — use the client as a small LAN gateway
The Data Relay Link client only needs normal IP reachability to those target hosts.Practical examples from the field guide
The same client can publish its own services and services on other LAN hosts at the same time. Typical examples:
Before adding a LAN target, prove that the Data Relay Link client itself can reach it:
You do not need a separate Data Relay Link client on every LAN host. A single enrolled client can act as a small gateway for hosts it can legitimately reach, which is useful for a few to a few dozen systems. Keep the scope deliberate rather than turning it into broad network exposure.
HTTPS is passthrough
Data Relay Link does not terminate or replace the application’s TLS certificate. If users connect withfw.example.com, the target application must present a certificate valid for that hostname where applicable.
Persistent public-port lifecycle
- Disable stops publication and keeps the port reserved.
- Enable resumes on the same reserved port.
- Edit + apply changes the target without intentionally changing the reservation.
- Release returns the public port to the pool.
Security reminder
Publishing a service makes that service reachable through the assigned public endpoint. Keep the target application’s own authentication, authorization, host firewall, and access controls enabled.SSH
SSH-specific setup and checks.
HTTP & HTTPS
Web publishing and TLS passthrough.
Custom TCP & LAN
Databases, appliances, APIs, and LAN targets.