You are not logged in.
Discovered today that the latest version of NetworkManager doesn't properly add static routes sent by the OpenVPN server.
Broken version: 1.0.10-1
I could see in journalctl that the server was sending the appropriate static route info, but no static routes were being added. Setting them up by hand would result in everything working as expected, but my work has a lot of static routes for the VPN, so it really isn't an option. Downgrading networkmanager to 1.0.8-1 and restarting NetworkManager resulted in all appropriate static routes being created automatically when connecting to my VPN.
Offline
Please search before posting: https://bugs.archlinux.org/task/47535
Offline
I did search before posting.... the forums... and Google for about an hour. Sorry that the bug tracker apparently doesn't show up very high in Google results. Just figured I'd post it here as well in case anyone else, like me, doesn't go directly to the bug tracker and specifically search there.
Last edited by ardichoke (2015-12-29 02:31:54)
Offline
I did search before posting.... the forums...
and you didn't see this: https://bbs.archlinux.org/viewtopic.php?id=206740 ?
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Not so strange R00KIE that he didn't find that thread.
Very often Google ranks a forum thread that has a much more descriptive title higher than the one that contains the real solution.
Thankfully we have the link posted here now so for anyone that finds this thread, can get the information so far.
Yes, I have also been bitten by this VPN problem, my resolution for now is running OpenVPN normally, and it forwards the traffic correctly.
Offline