I'd like to second Alessandro and David, with a tap setup, network-manager-openvpn is not able to setup all the push routes that the OpenVPN server is delivering and this makes this plugin pretty much unusable.
The problem doesn't seem to be that that routes are not set up per se, but that someone (else? presumably network-manager or network-manager- openvpn) deletes them afterwards, but strangely only some of them (looks like only the routes that use the tap-device). You can nicely watch this happening using "ip monitor". In general, network-manager(-openvpn) seems to be broken by design since its inception. How hard can it be to build a GUI that is able to do what sudo /etc/init.d/openvpn <CONFIG> start does on the command line? Why invent a complicated mechanism that doesn't do anything that openvpn doesn't do better itself? Why not simply use OpenVPN config files, maybe getting a password from the user and then let openvpn do its job. But sure, it's easy to complain, when you don't actually contribute. -- OpenVPN 2.1_Rc7: Does not route properly in Ubuntu 8.04 https://bugs.launchpad.net/bugs/194487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
