In order to setup a tunnel connection between two AREDN nodes, one needs to act as the server, and the other as the client. In this example, VA7FI-HAP-1 is the server and VE7RBE-HAP-1 is the client (and the details are made up):

On VA7FI-HAP-1's Tunnel Server page:

From left to right:

• Client: VE7RBE-HAP-1 is Robert's node name.
• A unique password is created
• Net: 172.31.39.164 is automatically assigned.
• Some optional Contact Info can be added.

VA7FI's public IP address will also need to be communicated to VE7RBE. You can quickly find it by searching for “what's my ip” in

Google	DuckDuckGo

On VE7RBE-HAP-1's Tunnel Client page:

From left to right:

• Server: 154.12.201.102 is VA7FI-HAP-1's public IP address
• Pwd: is the password created by VA7FI-HAP-1
• Network: 172.31.39.164 is the net address generated by VA7FI-HAP-1

Most residential internet services are given one dynamic IP address, which means that the address can change every few days (or when the router power cycles).