[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2019-10-16 Thread Torsten Bronger
I reported it at . ** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues #40 https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/40 -- You received this bug notification because you are a member of

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2019-10-15 Thread Torsten Bronger
[Re-posted because I accidentally clicked on “Post Comment”. Sorry for that.] Confirmed with Ubuntu 19.04. An push "route 134.94.0.0 255.255.0.0 net_gateway" is ignored. The pushed route is mentioned in the NetworkManager log: NetworkManager[893]: […] Data: Static Route: 134.94.0.0/16

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2019-10-15 Thread Torsten Bronger
Confirmed with Ubuntu 19.04. An push "route 134.94.0.0 255.255.0.0 net_gateway" is ignored. The pushed route is mentioned in the NetworkManager log: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2018-05-14 Thread Roman
$ sudo systemctl restart NetworkManager also fixed pushed routes from server. Thanks author of comment #14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1603600 Title:

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2018-04-06 Thread WalterNicholls
Confirmed, just setting up new Xubuntu virtual machine 17.10 - after all updates. Architecture: amd64 network-manager-openvpn and network-manager-openvpn-gnome both Version: 1.2.10-0ubuntu2 I originally started with a config downloaded from pfSense. As usual, openvpn from command line is

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2018-03-17 Thread Andrey Arapov
The same issue :-/ Ubuntu 16.04.4 LTS network-manager-openvpn 1.1.93-1ubuntu1.1 network-manager-openvpn-gnome 1.1.93-1ubuntu1.1 I am usually setting: VPN connection settings -> IPv4 Settings -> Routes... -> [x] Use this connection only for resources on its

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-11-02 Thread Dan Mick
This is *still* happening in Artful, nm 1.8.4-1ubuntu3, nm-openvpn 1.2.10-0ubuntu2. Seriously, this needs to be fixed. How do I get someone's attention? I have tried and cannot follow the path of the code through the dbus amazingness. -- You received this bug notification because you are a

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-09-06 Thread Marco Witte
as parasit-go2 said: Within cli, works: $ sudo openvpn --config file.ovpn verify connection and check "ps" of openvpn now disconnect. Now start via gui. Verify connection and check "ps" of openvpn See the differences? -- You received this bug notification because you are a member of Desktop

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-07-11 Thread Miika Vesti
Temporary workaround that can be used instead of reboot: $ sudo systemctl restart NetworkManager This works for me. After restarting NetworkManager all pushed routes are correctly set. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-07-05 Thread Matthew Darwin
Issue is reproducible for me on Ubuntu (Kubuntu) 17.04: network-manager-openvpn 1.2.6-2ubuntu1 openvpn 2.4.0-4ubuntu1.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-07-03 Thread Parasit
Same problem with newest stable version: network-manager-openvpn/now 1.2.6-2ubuntu1 amd64 network-manager-openvpn-gnome/now 1.2.6-2ubuntu1 amd64 In logs i see many routes but only one or two (??!!) of them are really added to routing table. P.S. Guys... this very annoing bug in next days will

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-07-03 Thread Adam Donnison
Update on the above - after a reboot the routes were correctly added. So it seems that changing the config can upset the ability to create routes until a reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-07-03 Thread Adam Donnison
I am also affected, although this was working when using OpenVPN over the default port 1194 on UDP. I had to regenerate keys and in the process decided to move to port 443 TCP to better handle firewalls, and after this could see the "Data: Static Route:" information in the log, but no route was

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-04-26 Thread Parasit
Hello, I am also affected. Ubuntu 16.04 network-manager-openvpn-gnome 1.1.93-1ubuntu1.1 The same config file used from bash, works fine, in GUI ignores most of pushed routes. There are lots logs like: Apr 26 20:54:21 dell NetworkManager[1170]: [1493232861.9544]

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-03-21 Thread Ben
Hi, I am also affected by this bug. Any chance to ask maintainers to upgrade both packages? https://wiki.gnome.org/Projects/NetworkManager https://git.gnome.org/browse/network-manager-openvpn -- You received this bug notification because you are a member of Desktop Packages, which is

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-03-07 Thread Dan Mick
hlavki, I can't imagine that the misbehaving client is even aware of other clients on the same network segment. Surely this is coincidental. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu.

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-03-05 Thread Michal Hlavac
I tested this behaviour and discovered this: Routes are pushed correctly with "Use this connection only for resources on its network" settings when there is only one client from same network connected to openvpn server. If there are more than one clients connected from same network (router) it

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-02-09 Thread Dan Mick
Any chance of getting a backport to xenial? This is a severe issue for those with OpenVPNs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1603600 Title:

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2016-10-31 Thread Alberto Salvia Novella
** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1603600 Title: NetworkManager ignores

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2016-10-29 Thread Maximilian Federle
After some digging around I found that installing the new upstream releases of both network-manager (1.4.2) and network-manager-openvpn (1.2.6) fixed this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2016-10-29 Thread Maximilian Federle
I can confirm this bug. network-manager 1.2.2-0ubuntu0.16.04.3 network-manager-openvpn 1.1.93-1ubuntu1 The pushed routes are totally lacking, as are the DNS servers if one doesn't use the VPN as the default gateway for all traffic (i.e. by activating "Use this connection only for resources on