Looking for some guidance with this issue. Tried googling first and reading through forum but wasn’t able to find a solution exactly.
I have a TP-Link AX10000 router that supports OpenVPN. I configured the router so it acts as the OpenVPN server and I am able to access my home LAN while away via the OpenVPN clients on my laptop and smartphone. I have a dynamically assigned public IP from my ISP. Whenever it changes, I can no longer access my home LAN via OpenVPN because the certificate generated by my router was tied to/configured for the assigned IP at the moment the certificate was generated. I enabled DDNS on the router using the TP-Link DDNS service.
I’ve found myself having to regenerate a new certificate on the router every time the IP changes. This is a pain because I have to then upload it onto each of the OpenVPN clients and configure the connection again. If the IP didn’t change so frequently then it wouldn’t be such a huge deal but I’ve noticed that since I started using OpenVPN, my IP has been changing more often, every few days vs every few weeks or even months before.
How could I set it up where when my public IP changes, it updates with the TP-Link DDNS and I can continue to access my LAN with OpenVPN? Is this possible? Or is there another/different way to accomplish what I’m trying to do?
If you open one of the VPN client config profiles in a text editor, does it show the remote directive as an IP address or the DDNS domain name?
If it’s an IP, change to the DDNS domain name, save and import on your client device. It should then connect using the DDNS domain name which your DDNS provider will forward to your current IP address
I’m pretty sure you should be able to generate your certs based around a Domain name and not the IP, I think that is what I am doing but I can’t speak for how to do it on your particular router. Look around at the option and start searching on duck duck go
Using the router’s (TP-Link) DDNS. Edited the generated certificate in Notepad to point to the DDNS domain name instead of the IP. Imported it into the client and I am able to connect. Going to assume that once the IP changes again, it should still work now that the config file has the DDNS domain name and should point to the new IP.