NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
VPN not connecting
Yet another "I can't connect", but... I have tried this with windoze 10, linux (fedora 32) and my android phone (galaxy s9). I followed the instructions from the admin web page: downloaded the zi...
For the openVPN server, on android, use the openvpn connect app https://play.google.com/store/apps/details?id=net.openvpn.openvpn
It is also useful to have a dynamic dns service set up such as noip.
If you have the router behind another router, then the VPN server function will not work unless you forward the ports to on the router in front of it.
Beyond that, there are a few things to keep in mind.
- If you are currently connected to the router (on the same LAN as the router), then you will be unable to connect, as the OpenVPN server only lisens and accepts connections from the WAN side.
- On windows, the instructions are quite specific and missing steps can cause issues, e.g., if you forget to rename the adapter.
As I said, I followed the instructions from the router's admin page - exactly.- I did use the OpenVPN app from the android store. If necessary, I can post the logs from it.
- I do have a DDNS (thank you mynetgear.com).
- My connection is from the cable modem to the WAN port on the router (via a switch). No port forwarding, not connecting from the LAN.
- And, again, I did follow the instructions - without missing any steps - for windoze (use TAP, change names, etc.). And running wireshark on that system had the same result: packet sent to the router, packet returned from the router.
I have set up vpn's on linux boxes before, both client and server. So I am not a complete NOOB. And since there is no debug info from the router itself, though, I can't say what it is, or is not, doing. But all of the connections to the router and client machine are set as per specification, and from my experience, should be correct.
In that case, you will need to check the logs, also check if the client you are using is still allowing the encryption type to be used (especially needed on older routers that will be using an older version of the server).