Description of problem: I am using a Cisco group VPN and although I specify "not required" in the User password field, the vpn connection fails. Specifying any password works, but then I must also specify the optional username (neither of which should be necessary). Version-Release number of selected component (if applicable): NetworkManager-vpnc-0.7.996-4.git20090921.fc12.i686 vpnc-0.5.3-4.fc12.i686 How reproducible: Always Steps to Reproduce: 1. Setup VPN w/o user password or user name 2. Attempt to start vpn w/ nm-applet 3. fails Actual results: fails Expected results: should work Additional info:
I fixed the username thing upstream last night, the failure case for that is that the first connection will work, but subsequent ones will fail. Of course, if your Xauth username is different than your login name, you'll *always* need to set the password manually in the configuration. To debug the connection problem further, please set the password back to "Always ask" and in a root terminal: 1) killall -TERM nm-vpnc-service 2) /usr/libexec/nm-vpnc-service 3) try to connect from nm-applet Then grab the output of the nm-vpnc-service and paste it in here; it shouldn't contain any sensitive information.
If there's no user password needed, you shouldn't need a username either (logically). But it looks like one is still required by vpnc: [root@targee ~]# /usr/libexec/nm-vpnc-service ** Message: <info> vpnc started with pid 8768 /usr/sbin/vpnc: missing Xauth username ** (process:8763): WARNING **: <WARN> vpnc_watch_cb(): vpnc exited with error code 1 Did the packages get updated? I don't see anything newer than the following in rawhide or 12 updates: [root@targee ~]# rpm -qa |grep -i vpnc NetworkManager-vpnc-0.7.996-4.git20090921.fc12.i686 vpnc-0.5.3-4.fc12.i686
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
It looks like vpnc requires both the xauth password and the xauth username: if (!config[CONFIG_XAUTH_USERNAME]) error(1, 0, "missing Xauth username"); if (!config[CONFIG_XAUTH_PASSWORD] && !config[CONFIG_XAUTH_INTERACTIVE]) error(1, 0, "missing Xauth password"); which would be a bug in vpnc if your configuration does not need them; but I believe I fixed a bug in the last year or so that caused the default VPN username not to be sent down to vpnc; it would be good to try this again with latest packages of NetworkManager and NetworkManager-vpnc and see if you can still reproduce the "missing Xauth username" thing again.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.