If you'd like your node to be able to act as a Tunnel Server and allow other nodes to connect to you, you will need to make sure that your node is available over the Internet. This includes configuring a dynamic DNS entry, and making some firewall or port forwarding settings.

Most residential internet services are given a single dynamic IP address, which means that the address can change every few days or so (or when the router power cycles). This means that when a server node suddenly gets a new public IP address, the client node can't find it anymore.

One solution is to use a Dynamic_DNS service like No-IP. These services query your dynamic IP address, and translate it into a static hostname. It's that hostname that you then give the AREDN client (instead of your public IP address).

However, the No-IP service needs to be “told” when your dynamic IP address changes. This can be done by installing a small program that notifies them of the change, or alternatively, some routers have that function already built in. For example, the No-IP account can be entered in the Telus T3200M router here:

Advanced Setup → Dynamic DNS

With this setup, every time Telus gives me a new public IP address, the router notifies No-IP, which updates it so that myfancyhostname.ddns.net continues to point to my router.

Port 5525 has to be forwarded to the hAP. There are two steps to this:

Just like Telus gives the router a dynamic WAN IP address, the router gives the home devices dynamic LAN IP addresses. The first step is to force the router to always give the same IP address to the hAP. On the T3200M this is done in:

Advanced Setup → DHCP Reservation

• Select the MAC address of the hAP from the list.
• Choose an IP address to assign it.
• Disconnect the hAP from the router and reconnect it to clear the IP.

Now that the hAP's LAN IP address is fixed, we can forward a port to it:

Firewall → Port Forwarding

• Select the hAP's IP address from the list
• Enter 5525 as the start and 5535 as the end (if you want to give 10 tunnels)
• Select TCP

Now we can go back to AREDN and add a server:

1. add your DNS name
2. select Wireguard Server and click the +
3. enter the name of the client
4. the rest of the information will auto populate
5. click the clipboard icon and copy the information, which you'll need to send to the client.
6. click Done
7. select Commit