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.
SleeplessInPDX
Feb 05, 2020Aspirant
Hi CrimpOn,
Thanks for you reply. When using an Android/iOS device connect to Orbi OpenVPN via LTE network, I am able to see the connected device listed as "OPENVPN-TUN" (in "Attached Device" web page) and see Orbi assigns an IP address of 192.168.2.2 to device (note: the internal LAN subnet is 192.168.1.X). It works as expected and as you described.
However, with a Windows 10 client, Orbi assigns an IP address of 192.168.1.100 as seen in "Attached Device" web page and I can also see in "Logs" web page under "Administration" a line entry of DHCP IP address 192.168.1.100 assigned to the Windows 10 client . To be clear, the Windows 10 client is connected to LTE network. Made double sure the Windows 10 client is not connected to Orbi's LAN. It's a very basic test. No other OpenVPN client is connected.
As a test, on Windows 10 client I open a command shell to ping Orbi's IP (on LAN side, which is 192.168.1.1), the ping fails (because Orbi OpenVPN assigned the wrong IP address. It should be 192.168.2.2... just like the Android device).
(Note: In my LAN network, I configured Orbi's DHCP Server to have a start IP address of 192.168.1.100 and end IP address of 192.168.1.254. IP address range from 192.168.1.2 to 192.168.1.99 are IP address statically assigned (using the Address Reservation UI).
This issue appears on both Firmware Version 2.5.1.8 and Version 2.3.5.30. I believe this is a firmware bug in Orbi.
To Netgear Orbi team, please advise.
FURRYe38
Feb 05, 2020Guru - Experienced User
You may want to open a support ticket here and get some help on this:
https://www.netgear.com/support/#
SleeplessInPDX wrote:Hi CrimpOn,
Thanks for you reply. When using an Android/iOS device connect to Orbi OpenVPN via LTE network, I am able to see the connected device listed as "OPENVPN-TUN" (in "Attached Device" web page) and see Orbi assigns an IP address of 192.168.2.2 to device (note: the internal LAN subnet is 192.168.1.X). It works as expected and as you described.
However, with a Windows 10 client, Orbi assigns an IP address of 192.168.1.100 as seen in "Attached Device" web page and I can also see in "Logs" web page under "Administration" a line entry of DHCP IP address 192.168.1.100 assigned to the Windows 10 client . To be clear, the Windows 10 client is connected to LTE network. Made double sure the Windows 10 client is not connected to Orbi's LAN. It's a very basic test. No other OpenVPN client is connected.
As a test, on Windows 10 client I open a command shell to ping Orbi's IP (on LAN side, which is 192.168.1.1), the ping fails (because Orbi OpenVPN assigned the wrong IP address. It should be 192.168.2.2... just like the Android device).
(Note: In my LAN network, I configured Orbi's DHCP Server to have a start IP address of 192.168.1.100 and end IP address of 192.168.1.254. IP address range from 192.168.1.2 to 192.168.1.99 are IP address statically assigned (using the Address Reservation UI).
This issue appears on both Firmware Version 2.5.1.8 and Version 2.3.5.30. I believe this is a firmware bug in Orbi.
To Netgear Orbi team, please advise.
- MTBBILLFeb 24, 2020Aspirant
I am having the exact same issue. Was this ever resolved?
- SleeplessInPDXFeb 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?