Relay
Reuse existing Gateways and Connectors to build single-hop or two-hop connections for different services. Traffic between AXVIA-hosted and AXVIA-owned nodes runs over dedicated lines.
Learn about node reuseRelay connectionReuse an existing Gateway and Connector.
Relay is not subscribed to separately. Gateway and Connector each have their own service period, and data usage follows the respective plan and metering rules.
Learn about subscriptions and metering →Dedicated lines connect AXVIA-hosted and AXVIA-owned nodes. Customer-provided nodes use the customer’s network; connection capacity depends on the server and provider network.
Latency is measured as the round-trip time (RTT) between nodes; packet loss results come from a 10,000-packet test, and line jitter is minimal. These figures apply to dedicated lines between AXVIA-hosted and AXVIA-owned nodes.
The device connects to the Gateway, travels through a tunnel to the final Connector, and from that region accesses public internet services.
Learn about Connector egress →A dedicated transit Connector is added between the entry and egress points, with a separate tunnel for each segment. The transit node only forwards traffic; public internet access, Cloud Pulse forwarding, and access auditing are handled by the final Connector.
Learn about dual-hop connections →Use a Gateway and Connector dedicated to port forwarding to map ingress TCP or UDP ports to designated endpoint services.
The dedicated terminal configuration establishes a service tunnel while preserving the device's original default route.
Learn about port forwarding →Employee clients use subscription links; WireGuard, RouterOS and FortiGate use their supported standalone configurations. Standalone configurations can be named, rate-limited and individually revoked when a device is disabled.
A supported standard Relay can connect the internal networks of terminals under the same Relay. Enable interconnection on both ends, check for subnet conflicts, then download and re-import the updated configuration. Public egress selection and internal network interconnection are managed separately.
View the entry, relay, and final egress from the topology; check connection status, upstream and downstream traffic, and bandwidth in the Relay and terminal details to identify nodes or configurations that need further investigation.
Relay is a connection between nodes. A single-hop path uses a Gateway and the final Connector; the additional server in a two-hop path is a transit-only Connector.
Traffic between AXVIA-hosted and AXVIA-owned nodes runs over dedicated lines. Customer-provided nodes use the customer’s server and network; connection capacity depends on the customer’s provider and network conditions.
Both the Gateway and Connector require dedicated port-forwarding firmware and a dedicated Relay. Traffic is forwarded only after you explicitly add TCP or UDP mappings and specify the listening port, target endpoint, target address and service port.
