Bug 974935

Summary: NetworkManager-openvpn: option for split tunneling does not work
Product: [Fedora] Fedora Reporter: Florian Weimer <fweimer>
Component: NetworkManager-openvpnAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: andre, bretm, choeger, dcbw, huzaifas, steve
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-05 19:53:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Florian Weimer 2013-06-17 07:49:07 UTC 
Description of problem:

The option "Use this connection only for resources on its network" has no effect.  If I check it, it is unchecked again when I visit the VPN again, and OpenVPN still does not perform split tunneling.

Adding never-default=true to the [ipv4] section in the configuration has the intended effect, though.

Version-Release number of selected component (if applicable):

NetworkManager-openvpn-0.9.6.0-2.fc19.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. Import the Red Hat VPN settings.
2. Go to the advanced settings dialog.
3. Choose the IPv4 tab.
4. Check the "Use this connection only for resources on its network" button.
5. Establish a VPN connection.

Actual results:

Split tunneling is disabled.

Expected results:

Split tunneling is enabled.
Comment 2 andre 2013-07-05 14:02:44 UTC 
Experienced the same. My workaround was to run nm-connection-editor directly and enable "Use this connection only for resources on its network".
Comment 3 Bret McMillan 2013-07-05 19:40:14 UTC 
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=952224 ?
Comment 4 Florian Weimer 2013-07-05 19:53:29 UTC 
Yes, it's a duplicate.

*** This bug has been marked as a duplicate of bug 952224 ***