I dont actually think this is hard to setup in mageia 6
if it does not work there maybe a reason and however easy the developers make the installation process,
it will still be difficult for you when it does not work if you dont understand whats going on.
i was helping a guy from australia to install expressvpn (which i paid the 100 pounds for a sub to try it) and it simply does not work with mageia or redhat/centos full stop, unless your willing to use there custom made setup script which does horrible things like set your resolv.conf immutable so your off vpn settings wont work.
so using there money back guarrentee got my money back and stuck with torguard which is half the price and simply works.
problem is these vpn providers do non standard things to make them fast that need their propriety setup, and that just wont work with the standard openvpn setup.
mageia provides a simple tool to create a vpn entry thats basic, but my method allows you to up that to a more tailored approach.
I use it for my mobile/mageia laptop/tablet to home and torguard vpn with no problems.
try to understand whats going on , and it might be easier to see why its not working.
that could be anything form:
1. you have missed a step, or misread an instruction
2. standard openvpn not implemented by the service
3: firewall rules/restrictions preventing vpn access
4: network/routing issues in your workstation
so with that ill try and describe again what is needed for openvpn to work, without config specifics. we will use the tun method.
when you open a browser and point it at a web address , the first thing that happens is getent hostname (returns ipaddress), always check that's working first.
next a tcp connection is established via your default route (eth0 for example) to the target ip address , and this may go through multiple gateways to get there.
The data you see is passed back along the route to your browser, and rendered.
when using a vpn tun0 becomes the default route for all traffic other than local.
so your routing table will get updated with an entry for tun0, once the vpn is up.
tun0 is a device so has to be added as a passable device into your firewall rules.
tun0 is a route just like eth0, and can pass multiple concurrent tcp/udp connections.
tun0 is just the end point to an openvpn connection to a target server outside your network, and is very much the same as ssh'ing into that server outside your network. when openvpn starts given a protocol, usually udp and a target ip address it will make a connection with the destination server, and like ssh it can use publickey/privatekey (ssh keys) or like a ssl connection in a web browser to a password protected site it can use certificates.
your browser has those loaded into it, ssh you have to set them up, but for openvpn you must provide a path to them in your config file. The vpn provider will provide you with these, as a downloadable bundle.
if tun0 gets created and the openvpn process stays up then you have most likely succeeded in establishing the link with the target server.
if not something is stopping that connection to the server from being established, so work out why.
try traceroute ipaddresssuppliedbyvpnprovider
if tun0 is up but you cant pass data down it, then it could be a firewall issue in your kernel on your workstation, try disabling it.
try to use traceroute to see where the packets are heading to check that your routing is correct.
traceroute
http://www.microsoft.comshould show it going via tun0 through your vpn providers infrastructure and out the other end.
if its going via eth0 or you main nic then routing is not being correctly setup on your workstation, check the routing table with netstat -rn.
also check your dns in resolv.conf and traceroute that.
see what route that takes, if its via your main nic (eth0 for example) then choose another dns server that traceroute goes via the tun0 port.
I hope im helping, the main aim here is to make you self sufficient so dont get frustrated and blame mageia, when it has little to do with mageia why this does not work for you. This is not supposed to be a lecture, but this question comes up so often perhaps it needs a better explanation.
by the way incase its not obvious ill spell it out. to diagnose things in unix (for those who are not 30 year veterans) you need to be root in a terminal , and commands may need to be installed if they are not available in your setup.
regards peter