NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SleeplessInPDX
Feb 03, 2020Aspirant
ORBI OpenVPN not working with Windows 10 client
I have setup my Orbi for OpenVPN and followed the instructions closely on both the Orbi router side and client side. For Android and iOS devices, Orbi's OpenVPN is working such that a VPN session is...
- May 22, 2020I worked with Netgear tech support a few weeks ago on this. The problem is solved. Apparently, the configuration file was bad on the particular revision of Orbi firmware I was using. I had updated the firmware but not the configuration file. Tech support suggested replacing the Open VPN configuration file. When I did that it started working.
MTBBILL
Feb 24, 2020Aspirant
I am having the exact same issue. Was this ever resolved?
SleeplessInPDX
Feb 24, 2020Aspirant
> I am having the exact same issue. Was this ever resolved?
No. This issue remains open till this day. I'm open to submit a bug report to Netgear but I dont know how and I have no time to research.
- CrimpOnFeb 24, 2020Guru - Experienced User
I recently learned more about OpenVPN and found that the way Android and Windows do OpenVPN is different. Looking at the OVPN files that get downloaded from Orbi, it is clear that Android creates a "tun" connection and Windows creates a "tap" connection. There is an excellent explanation of the two VPN types here: https://buffered.com/glossary/tun-tap/
This being the case, one would expect Android (tun) devices to get an IP address in a different subnet from the primary Orbi network and Windows (tap) devices to get an IP address in the same subnet as the primary Orbi network.
Given that the Windows machine has an IP address in the same subnet as everything else connected to the Orbi, what is "No traffic"?
Can the Windows machine not reach the Internet?
Can the Windows machine not print?
- EricClarkeMar 03, 2020Guide
I too am having the same issue trying to set up VPN on an ORBI RBR50 (Firmware V2.3.5.30). I have a working version of this on an R9000 router (Firmware V1.0.5.8). I notice a couple of differences in the config files. The config file for the R9000 is as follows:
client
dev tap
proto udp
dev-node NETGEAR-VPN
remote xxxxx.xxx 12974
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert client.crt
key client.key
cipher AES-128-CBC
comp-lzo
verb 5The ORBI version adds a couple of lines at the bottom as follows:
verb 0
sndbuf 393216
rcvbuf 393216
route-method.exe
The first thing that I did was change verb from 0 to 5. Now there is lots more info in the log. The error that seems to be stopping things is something about recursive routing.
The message:
Recursive routing detected, drop tun packet to [AF_INET] xx.xx.xx.xx:12974 (The xs are, of course, my ip address.)
I've tried to remove all three of the lines at the end. It doesn't help.