All 14 tunnel servers that are setup in my hAP Lite have stopped working. Upon investigating, I found that the tunnel server network starting IP address has changed in its third and fourth octet. I want to avoid having to delete all of the existing tunnels and then recreate them, which will require sending new credentials to all my clients. So, I would prefer to change the 'changed' tunnel server network starting IP address back to the 'old' address. According to the latest docs, the tunnel server network starting IP address "...is calculated automatically and should not be changed unless there is a specific reason why the default will not work for your situation". It seems that I do have a specific reason to change the address. So, what is the procedure for changing a tunnel server network starting IP address?
Thanks,
Paul -- KA5TYW
Thanks,
Paul -- KA5TYW
You can set the IP range to use (it's actually the starting address, I think.
Hope this helps.
Orv W6BI
73,
Paul -- KA5TYW
Can you edit and save the Network:Port in your tunnel server to my HAP-FB from your HAP1?? Now I have 172.31.14.226:5528 in my client.
That may be the easiest way to get the tunnels to come up.
--Tim K5RA
According to the Docs, a Wireguard tunnel server IP:port for a client is generated automatically by the software when a server is created and it is based on the Wireguard Tunnel Server Network starting IP address, which is also generated automatically by the software. So, apparently, neither the server starting IP nor the IP:port is editable by the user in the current AREDN GUI. Perhaps the AREDN software developers should be consulted about providing a user capability to "revert" a server starting IP to match what existing tunnels are using, in case the server starting IP gets changed unintentionally and without the users awareness...until tunnels stop working.
Thanks,
Paul -- KA5TYW