OMIT requirement to configure DynDNS when setting up VPN Service
I have a static IP, which my ISP requires me to obtain via DHCP. If I just type in my details as a static setting, I can't connect at all.
In Netgear firmware, there is this (in my eyes) silly limitation that requires public IP set to static OR dynDNS in order to activate VPN service. In my case, that means I NEED to set up a dynDNS which I don't even need, just to satisfy this requirement. I know of a lot of ISPs that do not allow manually setting the static IP details, but rather dynamically assigning them. So for these reasons, I'd love to see that REQUIREMENT changed to an INFORMATION. If you know about VPNs, you probably also know that you need a static means to connect to said VPN.
similar previous posts:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.