Ingress, reusing the device access location.
Choose the ingress from the Gateways currently available to your team, so you don't need to redeploy an ingress node every time you create a two-hop connection.
Add a stop in between. Choose each location separately.
Reuse your team's existing Gateways and Connectors, add a dedicated relay node to build a two-hop Relay, and arrange the ingress locations and final egress according to your business needs.
Learn about node selectionA new connection, reusing existing nodes.
For transit, choose another Connector.
Designate an existing Connector as a dedicated relay, using its location and network to connect both ends. The relay's location does not determine the final public egress.
Final egress, arranged per business needs.
The final Connector can reuse existing resources or be created new. Choose each ingress, relay, and egress, then obtain this Relay's connection configuration for the device.
The relay handles forwarding.
The egress handles access.
The relay Connector receives the first tunnel segment and sends the traffic into the second tunnel segment leading to the final Connector.
Public network NAT, Cloud Pulse forwarding, and destination access auditing are handled by the final Connector. A relay-dedicated node only forwards and cannot serve as the final egress at the same time.
Explore egress capabilities →Interconnection for two segments, configured separately.
The connection from Gateway to relay and from relay to the final egress each has its own independent interconnect settings. Choose intranet-to-intranet, intranet-to-public network, or public network-to-public network based on node addresses; for intranet-to-public network, you also need to specify which end uses an intranet address.
Interconnection settings determine the node addresses used for each segment. Traffic between AXVIA-hosted and AXVIA-owned nodes runs over dedicated lines; connections using BYOG or BYOC nodes depend on the network you provide.
In the Relay details, view both connection segments, node relationships, and health. Device configuration and upstream/downstream traffic are managed along this connection, while destination access records are viewed from the final Connector.
Explore connection observability →Frequently asked questions.
Can the relay and the final egress use the same node?
No. The relay-dedicated Connector and the final Connector require different nodes: the former only forwards to the next tunnel segment, while the latter serves as the public network egress.
Can an existing Connector be switched to a relay?
First remove the Relay associated with this Connector, then switch it to relay-dedicated use. To exit relay mode, you also need to remove the associated Relay first; only after restoring normal use can it be selected as the final egress.
To create a new dual-hop setup, do all nodes need to be redeployed?
No. For the ingress and final egress, you can select resources already available in the current team or create new ones; for the intermediate hop, select a Connector already prepared for relaying. Each segment's address must satisfy the selected interconnection method.