TinCanTech wroteMullvad's download for Windows is an executable installer, for which, it is difficult to verify if openvpn.exe has been modified. I am
not saying they have tampered with openvpn but I am
not saying they have not.
The real problems you are facing are three fold:
- Number one is Mullvad's server configuration and what they intend to support.
You will have to take issues with their service up with them.
- Number two is the software you want to use once connected is not doing what you expect or prefer.
As above.
- Number three is that currently, Openvpn support of IPv6 is still in an incomplete state.
Openvpn devs are confident that openvpn IPv6 code (so far) is good, solid code but it is still missing some functionality. Example: Openvpn cannot set an IPv6 DNS server on windows at this time.
This is because Openvpn is Free Open Source Software created and maintained by volunteers and they have only so much time to offer.
You are in a testing phase and it is not going so well so I would recommend you try this:
- Setup your server and client on Linux; Using either a real system or a Virtual Machine, either are suitable, I run half a dozen Openvpn servers and clients on Linux VMs. Personally, I found Debian and Ubuntu to be the simplest.
- Use the Latest openvpn version (2.4) because it has the most to offer.
- Consider subscribing to the mailing list as another source of help.
- Experiment: We welcome quality feedback.
I highly recommend you read the entire
HOWTO: For OpenVPN Community Edition more than once. I refer back to it all the time.
There is also an abundance of documentation found here:
https://community.openvpn.net/openvpn/wiki/TitleIndex
And as a last resort, try using
google and their
site: feature (another tool I rely upon).
I hope that helps you find some direction.
Thank you for the reply. I have to say it begs the question why you're casting doubt about Mullvad and making allegations about their product rather than simply proving that the problem of the browser not defaulting to ipv6 and not reliably falling back to the default protocol doesn't exist in a "true" openvpn client / server. Talk is cheap. If they are at fault as opposed to "true" openvpn, why not post some results that show the browser defaulting to ipv6 and fallback working in a dual-stack client / server configuration and put this to rest. (While you're at it, post the configurations so they can be independently replicated.)
The only reason I'm trying to get a dual-stack openvpn server running is to prove or disprove whether the issues I'm experiencing with the browser default protocol and fallback are exhibited when running a "true" dual-stack openvpn server, since you're saying it won't be considered a problem unless I do that. The lack of documented examples makes this a lot more difficult than it should be to get openvpn servers running. So far, I've been able to get an ipv4 configuration working (although not very reliably), but I'm still trying to get a dual-stack configuration working. (I'm currently using windows but setting up a ubuntu server to try on linux.) Since openvpn supposedly supports dual-stack on windows and linux, you would think there would be information about setting up windows and linux servers somewhere on the openvpn website, but I haven't found anything so far. If you know of a reference, please post it. (Again, I'm not talking about the pki and the client-server connection. I have the client / server working, but the traffic from the vpn server is not routing to the gateway.)
With all due respect, the complete information required to get an ipv4-only server working isn't in the how-to for either linix or windows, let alone for a dual-stack server. The how-to and man pages cover the pki and the connection between the client and server very thoroughly, but neither address the configuration of the server to route the traffic from the vpn through the gateway. This information is what you'd expect to find the how-to section called "Routing all client traffic (including web-traffic) through the VPN", but it's not there. There's a one-line reference to iptables for linix, but nothing whatsoever about windows. I don't think anyone can reasonably claim this is well documented.
WRT windows, I found this thread
https://forums.openvpn.net/viewtopic.php?f=7&t=20765 called "[Solved] Windows 10 OpenVPN Server NAT with redirect-gateway". It mentions internet connection sharing, regedit and the Routing and Remote Access Service (RRAS), but I found that information is not accurate. I found that regedit and RRAS were not required on my system for an ipv4 server. There is another recommendation to use the advanced adapter settings to set the gateway. I tried that as well, but it didn't work at all. It would be helpful and would save users a lot of time and frustration if there was an official tutorial on this in the how-to.
WRT linux, I found this thread
https://forums.openvpn.net/viewtopic.php?f=5&t=22303&p=63931&hilit=digitalocean.com#p63931 called "Help a total noob trying to set up OpenVPN on ubuntu". The OP found the digital ocean tutorial and was attempting to get it working. Your remark was, "That is a crappy tutorial. Try arch-linux wiki for openvpn." I found the same digital ocean tutorial and I was going to use it until I found that thread. How is someone supposed to know the digital ocean tutorial is "crappy" unless they stumble over this thread? It would be helpful if there was an official tutorial on this in the how-to.
I'm really amazed that there aren't any official tutorials or examples on the openvpn website. Normally for any given software package, the official website is where you would expect to find accurate and up to date information that helps users get a system working properly and saves them from wasting their time looking elsewhere for potentially dubious information and/or reinventing the wheel.
