Red Hat Bugzilla – Bug 582933
knetworkmanager: "Always ask for password" does not work
Last modified: 2011-03-04 04:53:00 EST
Description of problem:
I've tried to use vpnc connection with knetworkmanager, but after filling all values in configuration it does not work - it does nothing not even ask for passphrase
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.configure vpnc connection, left user passphrase "always ask" (our vpn uses rsa token generated passpwords changing every minute, so it's not possible to store password)
2.click on vpn in knetworkmanager
nothing, not even asked for vpn password
connected to vpn
"Always ask" doesn't work, this is known, Dennis Gilmore has been complaining about that for a while. (The VPN he uses also uses such an RSA token set up.)
CCing Dennis because he's encountered this one as well.
I worked around it by manually setting the password. I need to update it each time i connect to the vpn
I did not try that workaround, because waiting for rsa to show new password (so I have whole minute before it expires), change stored password for vpnc and than try to connect... it seems just crazy :)
Anyway, I don't know the answer because I did not use vpnc with knetworkmanager, but does it support the same option as gnome networkmanger:
"ipv4 : routes: [ ] Use this connection only for resources on its network" ? I can't see this setting in knetworkmanager's config options. I care about this option because I usually listen internet radio whole time and routing that CZ->USA->CZ is (at least) wasting of resources.
Is knetworkmanger going to be default for F-13 in KDE?
There is a drop down list with basic settings, Additional addresses, and routes, The new Red Hat setup doesnt allow you to use the vpn as your default route. usually if i have 2 bars on my rsa token i have plenty of time to change the password and connect to the vpn.
I also have an RSA token and I'm experiencing this problem. My workaround until this is resolved is to just use nm-applet like Fedora 12 and earlier, but this requires modifying the nm-applet.desktop file.
1. sudo yum erase 'knetworkmanager*'
2. sed '/NotShowIn=KDE/d' /etc/xdg/autostart/nm-applet.desktop \
3. Logout and login
This is a issue which needs to be reported upstream. Please file a report at
Please add upstream report info to this report. We will monitor the upstream
report for a resolution.
Thanks for the report
Fedora Bugzappers volunteer triage team
Per comment #6 , here's some safer instructions so your modifications don't get lost on pkg updatse:
(In reply to comment #7)
> This is a issue which needs to be reported upstream. Please file a report at
> Please add upstream report info to this report. We will monitor the upstream
> report for a resolution.
huh? it's already here, since this bug was reported, see "external bugs"
cool, thanks for the clarification. Let's mark this triaged then.
*** Bug 557808 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
got some builds with an experimental upstream patch to help address this. Anyone interested in testing it out?
(In reply to comment #13)
> got some builds with an experimental upstream patch to help address this.
> Anyone interested in testing it out?
> F-14: http://koji.fedoraproject.org/koji/buildinfo?buildID=205291
> F-13: http://koji.fedoraproject.org/koji/buildinfo?buildID=205292
I've tested it using vnc. I set vpnc group password (stored) and user password as always ask. It asked me for password (group password filled and input gray-disabled), so it seems it's working. But because I have my rsa token at home, I was not able to enter correct password, so I just entered 1234 as password, clicked ok and nothing has happened, no error message I'd expect. I don't know what's actual behaviour for plasma knetnowrkmanager, because I've replaced it with nm-applet a long time ago because of this bug. I'll retest with correct password and old version when I get back home to rsa token.
new and old version has the same behaviour for connected (vpn in left down says connected) and failed to connect (no error message, just connecting replaced with not connected).
Old version does not ask for password just tries to connect without second passphrase. New version asks for password. So yes, new version fixes this bug
kde-plasma-networkmanagement-0.9-0.35.20110221.fc13 has been submitted as an update for Fedora 13.
kde-plasma-networkmanagement-0.9-0.35.20110221.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kde-plasma-networkmanagement'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/kde-plasma-networkmanagement-0.9-0.35.20110221.fc13
kde-plasma-networkmanagement-0.9-0.35.20110221.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.