Description of problem: When configuring a new VPN connectino (openvpn) to be exact via the network configuration in gnome-control-center, checking the 'Use this connection only for resources on its network' checkbox does not stay connected (and fails to then actually stop the connection being used as the default route) - HOWEVER using nm-connection-editor and then editing the connection that way (and then checking this checkbox) DOES enforce it correctly.
Just confirming this happens for me also. I set up my vpn by importing the RH vpn config file which worked OK in F18 on another machine (this is F19 fresh install) Thanks Alex for the workaround tip, worked here too! Looks like the nm-connection-editor is the same tool that was in Fedora18. Why do we have two UI's for the same thing?
Also wanted to reply this is happening to me as well with an imported RH VPN config file on F19. Alex Murray's workaround provides the fix.
I can confirm this is happening to me as well. ArchLinux X64 - 3.9.8-1-ARCH Gnome 3.8.3
*** Bug 974935 has been marked as a duplicate of this bug. ***
Confirmed on a fresh F19 installation, using OpenVPN.
(In reply to Alex Murray from comment #0) > Description of problem: When configuring a new VPN connectino (openvpn) to > be exact via the network configuration in gnome-control-center, checking the > 'Use this connection only for resources on its network' checkbox does not > stay connected (and fails to then actually stop the connection being used as > the default route) - HOWEVER using nm-connection-editor and then editing the > connection that way (and then checking this checkbox) DOES enforce it > correctly. Well, then it is a bug in gnome-control-center. Reassigning. (In reply to Tuomas Kuosmanen from comment #1) > Just confirming this happens for me also. > > I set up my vpn by importing the RH vpn config file which worked OK in F18 > on another machine (this is F19 fresh install) > > Thanks Alex for the workaround tip, worked here too! Looks like the > nm-connection-editor is the same tool that was in Fedora18. Why do we have > two UI's for the same thing? You should ask Gnome people why they reimplement all the stuff. The probably want to have control over it and have their look&feel.
Confirmed here as well on clean F-19 install, workaround works for me. NetworkManager.x86_64 1:0.9.8.2-5.fc19 control-center.x86_64 1:3.8.3-2.fc19
This option is not working for me, too. Also, when activated, my default routes are changing. Adding ignore-auto-routes=true in /etc/NetworkManager/system-connections/[connection-name] doesn't help, too.
As control-center-3.8.3-2.fc19, the option `Use this connection only for resources on its network' can be check marked but the button `Apply' is greyed out and thus disabled. Therefore, no new setting can be applied.
I'm running into this bug too using an updated FC19 installation. To work around this issue, I modified the [ipv4] section of the applicable configuration files in /etc/NetworkManager/system-connections: ... [ipv4] never-default=true ...
Button `Apply' still disabled for control-center-3.8.4.1-1.fc19.
(In reply to Christoph Frieben from comment #11) > Button `Apply' still disabled for control-center-3.8.4.1-1.fc19. The 'apply' button isn't disabled for me (recent F19 install, control-center-3.8.4.1-1.fc19), but the change to 'use this connection only for resources on its network' doesn't persist and I can't get that behavior without the workaround mentioned in c#10
This may be fixed now: https://git.gnome.org/browse/gnome-control-center/commit/?id=e165efc6f9970eed601b17d9f489c4243069a76f
This seems fixed indeed, works at least on this F21 testing machine.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.