Skip to main content

Connecting HyperPath Nodes

Overview​

HyperPath nodes automatically establish connections in a full mesh topology, meaning each node connects directly to every other node in your HyperNet. This guide explains how to verify these connections, test connectivity between nodes, and understand the different connection types that may be established.

Verifying Node Connectivity​

When you have multiple devices with HyperPath installed and activated within the same HyperNet, they will automatically discover and connect to each other. To verify these connections:

  1. Open a terminal on any HyperPath node
  2. Run the status command:
hyperpath status

This command displays comprehensive information about your node's current state and connections:

Image from Docusaurus page

Understanding the Status Output​

In the highlighted section of the status output, you'll find:

  • Remote Nodes: List of all other nodes in your HyperNet that this node has successfully connected to in the past
  • Node IPs: Each node's assigned HyperNet IP address (configured through the HyperNet IP parameter in the Admin Console)
  • Channels: The active communication channels established between nodes
  • Channel Types: Whether connections are direct P2P or relay-based
  • Network Interfaces: The network interfaces used for communication on each node (e.g. qmimux0 - enp0s5)

Testing Node Connectivity​

To confirm that nodes can communicate properly:

  1. Identify the IP address of a node you want to test from the status output
  2. Use the ping command to test basic connectivity:
ping <NODE_IP_ADDRESS>

A successful ping test confirms that packets can be sent and received between the nodes:

Image from Docusaurus page

Troubleshooting Connectivity Issues​

If nodes aren't connecting as expected:

  1. Verify Active Status: Ensure HyperPath is running on all nodes with hyperpath status and check the Admin console
  2. Check Token Configuration: Confirm all nodes are in the same HyperNet
  3. Network Restrictions: If only relay connections are established, check for restrictive firewalls or NAT configurations
  4. Interface Configuration: Verify the useable interfaces setting includes the correct network interfaces
  5. IP Conflicts: Ensure each node has a unique HyperNet IP configured

For persistent connectivity issues, examining the HyperPath logs may provide additional diagnostic information: