NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
KngDa
Nov 10, 2025Aspirant
OpenVPN connects to router when clients on Ethernet but not on Wifi
I am having difficulty getting OpenVPN to work to connect to my RS300 router with my Windows 11 computers. I have a Dell XPS 16 9640 and a Microsoft Surface Pro 2103 both running Windows 11 Pro. Both...
CrimpOn
Nov 10, 2025Guru - Experienced User
Thanks for the response. It might be easier to put the Ethernet and WiFi log files on cloud storage and post Links to them?
Each Netgear WiFi family seems to implement VPN connections differently.
- The original WiFi5 Orbi systems put VPN connections in a subnet "one up" from the primary IP subnet. i.e.
If the primary subnet is the default (192.168.1.x) then VPN connections receive IPs in 192.168.2.x - The WiFi6 Orbi systems put VPN connections in 192.168.254.x. I have an RBR750 that has a primary IP subnet of 10.10.0.x
When a device connects to the RBR750 over VPN, it gets an IP in 192.168.254.x
Alas, I have no experience with the RS product line. Perhaps Netgear decided to place devices connecting via VPN into the primary IP subnet (in this case 192.168.1.x)
Another consideration is the 'mode'. OpenVPN supports two types of connections: tap (for "network tap") and tun (for "tunnel")
Do an internet search for details. AI summary:
The default configuration file for Windows computers is tap, using UDP port 12974. With the latest versions of OpenVPN, I have been more successful manually changing the configuration to tun, port 12973. i.e.:
client
dev tun
proto udp
remote xxxxxxx.mynetgear.com 12973- StephenBNov 11, 2025Guru - Experienced User
CrimpOn wrote:
With the latest versions of OpenVPN, I have been more successful manually changing the configuration to tun, port 12973
KngDa - I also found I needed to do this (though with an Orbi system, not the RS300). Might be worth a try (though in my case I needed it to connect to remote servers connected with ethernet, so my symptoms were a bit different).
CrimpOn wrote:
In addition, it marked three of them as SPAM.
FWIW, ReadyNAS log snippets are often marked as SPAM by the automated filter. That was also the case with the old forum software. I wish they'd adjust the filter to fix that.