Bug 509773

Summary: [enh] add 'connect automatically' for VPNs
Product: [Fedora] Fedora Reporter: Matěj Cepl <mcepl>
Component: NetworkManager-vpncAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: davidz, dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-06 01:49:16 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
/var/log/messages none

Description Matěj Cepl 2009-07-06 02:35:41 EDT
Created attachment 350573 [details]
/var/log/messages

Description of problem:
not much else to add

Version-Release number of selected component (if applicable):
vpnc-0.5.3-3.fc11.x86_64
NetworkManager-gnome-0.7.1-6.git20090617.fc11.x86_64
NetworkManager-glib-0.7.1-6.git20090617.fc11.x86_64
NetworkManager-0.7.1-6.git20090617.fc11.x86_64
NetworkManager-glib-devel-0.7.1-6.git20090617.fc11.x86_64
NetworkManager-devel-0.7.1-6.git20090617.fc11.x86_64
NetworkManager-vpnc-0.7.0.99-1.fc11.x86_64
NetworkManager-openvpn-0.7.0.99-1.fc11.x86_64

How reproducible:
100% (I have never had NM-vpnc started automatically)

Steps to Reproduce:
1.In Connection Editor/VPN/RH VPN/Edit check "Connect automatically"
2.Restart network connection
3.
  
Actual results:
VPN did not started up

Expected results:
it should

Additional info:
I am not sure whom to blame, it might be whole NM thing rather than NM-vpnc problem.
Comment 2 Dan Williams 2009-11-06 01:14:56 EST
Yeah, vpn connect automatically isn't implemented yet.
Comment 3 Dan Williams 2009-11-06 01:49:16 EST

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