WireGuard Client VPN Issue

Routers
,
1

I am trying to use the WireGuard client feature on my Route10, however, devices don’t get network access when you access from outside the network over another (say cellular or public WiFi) network.

The WireGuard server settings seem to be correct - I think I’ve narrowed it down to the Alta DDNS providing the NAT IP address and not the public IP address. I was looking around for a setting but don’t seem to be able to find anything. I know there is a setting for that if you make your own DDNS record via one of the supported DDNS providers, but I can’t find that for the built-in Alta one.

I know my settings are configured correctly because if I change the DDNS domain name in the WireGuard profile settings on the device to one of the other ones I have configured to relay the public IP, the connection succeeds and network access works.

This can also be verified by pinging the Alta DDNS which results in my 192.168.254.x NAT IP being returned.

If I ping my other configured DDNS it sends back the actual public IP address.

Thanks!

2

Sorry that we missed this. We recently added the public. prefix for our DDNS hostnames, so if you add that to the peer address then it will resolve to the external public IP. Obviously this will only work if NAT and or firewall is properly configured, but it sounds like it is as you said it works with the direct IP. Hope that helps.

1 Like
3

Thank you for following up! I can confirm this works. Might I suggest the WireGuard profile generator include that as an option or at least a note to add that for accessing outside the network?

3 Likes