- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
RBR50 V2.7.3.22 as VPN server can not connect with OpenVPN Client on 2.5.3 Win 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RBR50 V2.7.3.22 as VPN server can not connect with OpenVPN Client on 2.5.3 Win 10
RBR50 V2.7.3.22 as VPN server can not connect with OpenVPN Client on 2.5.3 Win 10
Any help with this configuration would be much appriciated.
I have also tried openVPN client versions 2.4.8 and 2.4.7
Thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RBR50 V2.7.3.22 as VPN server can not connect with OpenVPN Client on 2.5.3 Win 10
@Tim61 wrote:RBR50 V2.7.3.22 as VPN server can not connect with OpenVPN Client on 2.5.3 Win 10
Any help with this configuration would be much appriciated.
I have also tried openVPN client versions 2.4.8 and 2.4.7
The issue you are having is with the OpenVPN Connect Client. The default configuration for OpenVPN on Windows is tap. (on other platforms it is tun.) The OpenVPN Connect package does not support tap.
I found a post on the OpVPN forum explaining the issue:
https://forums.openvpn.net/viewtopic.php?f=29&t=28944
This is a better one showing how to fix OpenVPN Connect Client rather than download a different OpenVPN version:
https://community.spiceworks.com/topic/2307998-failed-to-import-profile-openvpn
I made these changes tap->tun, port 12974->12973 OpenVPN Connect works on Windows 10.
Because I regularly VPN into several systems, I have been using the tunXten appliation for Windows which makes switching VPN hosts easy. tunXten supports both tap and tun modes on Winidows 10.
tun and tap are quite a bit different, so it is probably worth a few minutes to understand the differences:
This is a good explanation:
https://security.stackexchange.com/questions/46442/openvpn-tap-vs-tun-mode
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RBR50 V2.7.3.22 as VPN server can not connect with OpenVPN Client on 2.5.3 Win 10
Thank you CrimpOn,
I reviewed the supporting docs and also tried tunXten without Joy.
I resolved various issues and ended with "TLS Error: TLS key negotiation failed to occur "
I believe my issue is likely with the server side now. I will have to work that side in the near future.
Thank you again for your help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: RBR50 V2.7.3.22 as VPN server can not connect with OpenVPN Client on 2.5.3 Win 10
I am pretty certain that the Orbi OpenVPN host is working correctly, supporting tun connections on udp port 12973 and tap on port 12974.
I got OpenVPN Connect Client 3.3.1 (2222) on Windows 10 to work with a tun connection on port 12973.
tunXten worked with a tap connection on port 12974.
Android OpenVPN Connect tun on port 12973 works. (Android and Apple cannot do tap)
Linux VPN tun on port 12973 works.
I cheerfully admin that I am on firmware 2.7.2.104, but OpenVPN has worked consistently on every firmware from v2.3.5.0 to the present. I have it working on two different Orbi systems, one on 2.3.5.0 and this one on 2.7.2.104.
Windows is the only platform that supports tap connections. As the VPN articles point out, tap is only useful in certain situations. tun works for most people, most of the time.
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more