NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR50 OpenVPN has the right IP but cannot access Network Resources
I am trying to set up OpenVPN to Orbi Router. Using OpenVPN GUI because the updated OpenVPN Connect doesn't support TAP, and it seems Orbi Router only has the TAP configuration for download. ...
Orbi's implementation of OpenVPN Hose supports both tap and tun connections: The default is for UDP connections because they are more 'efficient':
It is not obvious (to me) why Netgear decided to create a parameter file for Windows connections with the tap specification (Level 2) and the non-Windows connections as tun (Level 3)
The OpenVPN implementation supports both. Both Apple and Android systems do not support tap, so tun is clearly the correct choice for those parameter files.
I am often confused, but my sense is that the issue is trying to locate network devices using a Windows shortcut rather than their IP address. Is the Orbi LAN in the same IP subnet as the device connected via OpenVPN? (192.168.10.x)
Unfortunately, I am not versed in OpenVPN so I can only use the OpenVPN GUI (2.5x something) since the most updated OpenVPN Connect won't import the configuration file Orbi generates.
The LAN IP the network adaptor captured is correct. It has the correct IP range, not in conflict with another device, has the right subnet mask, and has the right gateway.
The icon in the system box is also green, so by all indications, it should be correct.
But when I try to access a computer on the network it won't connect. I also cannot access the admin page of Orbi as well.
I am not sure what is going on.
To use OpenVPN Connect, one would use a text editor to change the ovpn file from tap to tun by editing these lines:
client dev tap ----- change to tun proto udp dev-node NETGEAR-VPN remote xxx.mynetgear.com 12974 ----change to 12973 resolv-retry infinite nobind persist-key persist-tun ca ca.crt cert client.crt key client.key cipher AES-128-CBC comp-lzo verb 0 sndbuf 393216 rcvbuf 393216 route-method exeAre you connecting to the Orbi web interface using the URL or IP address? 192.168.10.1
Ok. Will Give that File a Try.
Thank you very much.
There are differences between tap and tun connections (see the Wikipedia article).
Since the connection is "working" in the sense that the device appears in the Orbi Attached Devices page as a VPN connection, my guess is that the regular Windows connection practices may not function over VPN.