Topology

OrpheLink provides several core capabilities for building secure and flexible connections across different network environments:

• Site-to-Site Connection: Establishes secure connections between different sites.
• LAN-to-LAN Connection: Connects local networks across different locations.
• Exit Node: Designates a specific node as a traffic exit so other nodes can route traffic through it.

All connections between nodes use TLS 1.3 and QUIC.

To let administrators move from the overall network down to an individual node's connections, OrpheLink uses a three-layer topology. The first layer manages sites, the second shows the nodes inside a site, and the third focuses on a single node's neighbors and routing behavior. The following sections walk through these layers in order.

Layer 1: Site Topology

Site Topology is the first layer of OrpheLink's three-layer topology. Use it to create the overall site structure, assign nodes, configure Tunnel IPs and Exit Nodes, track inter-node tunnels, and view discovered local networks. Click Edit to change node behavior, advanced routing policies, and network bypass rules.

The main settings available at this layer are:

In the site topology, the following icons distinguish sites, exit nodes, regular nodes, and clients:

Type	Icon
Site
Exit node
Node
Clients

Layer 2: Nodes in Site

Nodes in Site is the second layer of OrpheLink's three-layer topology. Click Nodes in Site to list every managed node assigned to the site. Hover over or select a node to view its live status, and click Edit to configure node behavior, advanced routing policies, and network environment rules.

The main node settings available at this layer are:

Layer 3: Neighbor of Node

Neighbor of Node is the third layer of OrpheLink's three-layer topology and focuses on a single node's connections. Use it to inspect peers, configure Route to Exit, select a route mode, and apply custom DNS settings.

The main connection and routing settings available at this layer are:

Setup Scenario

After understanding the three topology layers, the following cross-site example shows how they come together in an actual deployment. Consider devices in different locations, even across different countries, whose clients are behind NAT and use private IP addresses. Using OrpheLink, these devices can communicate securely through a tunnel, enabling direct data transfer across NAT boundaries.

Configuration Steps

1. Log in to OrpheLink and open Inventory.
2. Verify that your OrpheAgent devices are listed.
3. Click the OrpheLink icon to configure links.

   !NOTE Any OrpheAgent devices that have not yet been configured will be placed in the Ungroup site by default.

4. Click on the Ungroup icon to see the number of OrpheAgent devices inside.
5. Click Add site.
6. Add four sites named HQ, Lab, Factory, and Portable, then click Save.
7. Click the HQ site and then click the Edit icon to add a node.
8. Click Add Node to add an OrpheAgent device and configure its connections.
9. Choose FAE-1164-208 from the OrpheAgent list.
10. Set the Tunnel IP to Auto and select a tunnel subnet.
11. Click Add neighbors to choose which OrpheAgent nodes to connect to.
12. Click Add LANs and select the appropriate networks from the dropdown list. This configures a LAN-to-LAN connection, allowing endpoint devices to access remote OrpheAgent devices.
13. Click the Save icon.
    The connection between the HQ site and the Ungroup site occurs because node FAE-1164-208 is assigned to HQ, while its neighbors (FAE-Dongle1, KSH-4010, and FAE-PC-205) remain in the Ungroup site.
14. Configure the remaining sites and nodes using the same procedure:
    • Lab: Add node KSH-4010. Add neighbor nodes and configure LAN connections.
    • Factory: Add node FAE-PC-205. Add neighbor nodes.
    • Portable: Add node FAE-Dongle1. Add neighbor nodes and configure LAN connections.

Final Configuration Summary

After completing the setup, the resulting site topology is displayed as follows:

The Tunnel IP and LAN settings for each configured site are listed below:

Once this setup is completed, the devices are fully connected and ready to communicate.