NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Issue with OpenVPN on RAXE300
I recently had been getting ignorable errors when connecting via OpenVPN to my RAXE300 router but apparently a recent Android app update now has broken it completely. I tried downloading the .opvn se...
For reference, make sure you are testing from an internet connection outside of your LAN. If you are on a smart phone, turn off Wi-Fi and connect through your cell data. A test connection from a computer has to be Wi-Fi or Ethernet from another location away from your LAN.
Generation of the ovpn configuration file from within the user interface is dependent on the installed firmware. Netgear is extremely lax when it comes to updating and keeping their firmware up to date in this area.
I successfully connected to a Netgear router through their OpenVPN server for years from both Windows and Android. The Netgear firmware fell in a ditch a couple of years ago in response to some Windows changes. Since that time I have retired my Netgear router and now use an ASUS product.
Do some searches here in the community for OVPN. Search in both the AC router community as well as the AX router community. I recall some success stories where posters included copies of their configuration file.
My tests had been at home with my phone as a hotspot (so no connection to my home WiFi). Connecting my Chromebook and laptop to the hotspot caused the no connection issue. I then edited my phone's .opvn file and installed that with WiFi turned off - and it worked! So, I guess my issue is somehow related to use of the hotspot as the Internet connection. Not sure why but I guess I have my answer. Weirdly, using the VPN on just my phone didn't help my Chromebook connect but when I tried connecting using that app (so both the phone and Chromebook were using the VPN app) I connected instantly.
Thanks for the help but if you have any explanation as to why I had to use the app on both devices to connect I'd be all ears.
Glad you got it working. It does seems to be under odd circumstances. It may have to do with the assignment of IP addresses within the hotspot application