"Open tickets (11)" ohhh well.
*clicks*
OpenVPN on Ubuntu, and probably another case of NetworkManager being bad.
GNU/Linux is still the worst thing possible to support, and we support Windows (including XP) and Chrome OS.
@dashie but without it it's nearly worse
@CobaltVelvet sad but true :(
On Windows I made lvpngui that just takes care of everything. On GNU/Linux it's much harder.
DNS alone is such a mess it always goes wrong.
- NM uses the physical link's DHCP DNS instead most of the time;
- If you call openvpn directly, NM overrides /etc/resolv.conf and same, resolvconf utility becomes useless;
- without NM, you have to use a root shell and systemd to manage openvpn. Not very user-friendly.
Solution: Import into NM, edit your physical link's DNS servers, hope for the best.
nm/systemd tainted distros make everything ever so much worse.
@munin I know we all love to say that but... it wasn't so much better before either :p
They're failing at a problem we've been avoiding for long
I'm on freebsd - it's much, much easier there.
@CobaltVelvet Have you ever tried to setup openvpn connection on ChromeOS?
@Marzanna I did, I implemented that on https://vpn.ccrypto.org/ not so long ago. It's not easy but at least once the procedure is figured out it works fine.
I prefer spending a few hours on generating their .onc files than spending time every month fighting NetworkManager's half-assed openvpn config file parser and random bugs.
@CobaltVelvet NM with openvpn works flawlessly for me. And I refused to use ChromeOS because it's one huge half-working inconvenience. Partly because of terrible openvpn support.
@CobaltVelvet NetworkManager is the child of SATAN