Bug 340543 - openvpn is configured to connect automatically when wifi is connected, but fails because VPN secrets are unavailable, and this causes the WIFI connection to drop, and it will never connect until WIFI is manually disconnected and connected again.
Summary: openvpn is configured to connect automatically when wifi is connected, but fa...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networking in general (show other bugs)
Version: master
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-01 00:18 UTC by rolandu
Modified: 2024-12-23 18:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description rolandu 2014-11-01 00:18:47 UTC 
Main reason seems to be this... [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.


Nov  1 01:58:52 curiosity NetworkManager[1324]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov  1 01:58:52 curiosity NetworkManager[1324]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Nov  1 01:58:52 curiosity avahi-daemon[1034]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.91.
Nov  1 01:58:52 curiosity avahi-daemon[1034]: New relevant interface wlan0.IPv4 for mDNS.
Nov  1 01:58:52 curiosity avahi-daemon[1034]: Registering new address record for 192.168.1.91 on wlan0.IPv4.
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> Policy set 'MUPO' (wlan0) as default for IPv4 routing and DNS.
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> Writing DNS information to /sbin/resolvconf
Nov  1 01:58:53 curiosity dnsmasq[2863]: setting upstream servers from DBus
Nov  1 01:58:53 curiosity dnsmasq[2863]: using nameserver 192.168.1.1#53
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Nov  1 01:58:53 curiosity avahi-daemon[1034]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::224:d7ff:fe78:e63c.
Nov  1 01:58:53 curiosity avahi-daemon[1034]: New relevant interface wlan0.IPv6 for mDNS.
Nov  1 01:58:53 curiosity avahi-daemon[1034]: Registering new address record for fe80::224:d7ff:fe78:e63c on wlan0.*.
Nov  1 01:58:53 curiosity NetworkManager[1324]: <error> [1414799933.477121] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request.
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> Policy set 'MUPO' (wlan0) as default for IPv4 routing and DNS.
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> (wlan0): device state change: secondaries -> failed (reason 'secondary-connection-failed') [90 120 54]
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> NetworkManager state is now DISCONNECTED
Nov  1 01:58:53 curiosity NetworkManager[1324]: <warn> Activation (wlan0) failed for connection 'MUPO'
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> (wlan0): deactivating device (reason 'none') [0]
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 16303
Nov  1 01:58:53 curiosity avahi-daemon[1034]: Withdrawing address record for fe80::224:d7ff:fe78:e63c on wlan0.
Nov  1 01:58:53 curiosity avahi-daemon[1034]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::224:d7ff:fe78:e63c.
Nov  1 01:58:53 curiosity avahi-daemon[1034]: Interface wlan0.IPv6 no longer relevant for mDNS.
Nov  1 01:58:53 curiosity kernel: [219673.382129] wlan0: deauthenticating from bc:ae:c5:eb:88:31 by local choice (reason=3)
Nov  1 01:58:53 curiosity wpa_supplicant[1448]: wlan0: CTRL-EVENT-DISCONNECTED bssid=bc:ae:c5:eb:88:31 reason=3 locally_generated=1
Nov  1 01:58:53 curiosity avahi-daemon[1034]: Withdrawing address record for 192.168.1.91 on wlan0.
Nov  1 01:58:53 curiosity avahi-daemon[1034]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.91.
Nov  1 01:58:53 curiosity kernel: [219673.392989] cfg80211: Calling CRDA to update world regulatory domain
Nov  1 01:58:53 curiosity avahi-daemon[1034]: Interface wlan0.IPv4 no longer relevant for mDNS.
Nov  1 01:58:53 curiosity NetworkManager[1324]: <warn> DNS: plugin dnsmasq update failed
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> Removing DNS information from /sbin/resolvconf
Nov  1 01:58:53 curiosity dnsmasq[2863]: setting upstream servers from DBus
Nov  1 01:58:53 curiosity kernel: [219673.398026] cfg80211: World regulatory domain updated:
Nov  1 01:58:53 curiosity kernel: [219673.398035] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Nov  1 01:58:53 curiosity kernel: [219673.398040] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  1 01:58:53 curiosity kernel: [219673.398045] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  1 01:58:53 curiosity kernel: [219673.398049] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Nov  1 01:58:53 curiosity kernel: [219673.398084] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  1 01:58:53 curiosity kernel: [219673.398095] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Nov  1 01:58:53 curiosity NetworkManager[1324]: <warn> Connection disconnected (reason -3)
Nov  1 01:58:53 curiosity NetworkManager[1324]: <info> (wlan0): supplicant interface state: completed -> disconnected
Nov  1 01:58:53 curiosity NetworkManager[1324]: <warn> Connection disconnected (reason -3)
Nov  1 01:58:53 curiosity wpa_supplicant[1448]: wlan0: CTRL-EVENT-SCAN-STARTED 
Nov  1 01:58:55 curiosity avahi-daemon[1034]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::224:d7ff:fe78:e63c.
Nov  1 01:58:55 curiosity avahi-daemon[1034]: New relevant interface wlan0.IPv6 for mDNS.
Nov  1 01:58:55 curiosity avahi-daemon[1034]: Registering new address record for fe80::224:d7ff:fe78:e63c on wlan0.*.
Nov  1 01:58:56 curiosity NetworkManager[1324]: <info> Auto-activating connection 'MUPO'.
Nov  1 01:58:56 curiosity NetworkManager[1324]: <info> Activation (wlan0) starting connection 'MUPO'


Reproducible: Always

Steps to Reproduce:
1. configure wifi connection
2. configure openvpn using the GUI
3. set openvpn to connect automatically when wifi is connected
4-5. put laptop to standby and then wake laptop from standby (also seems to happen when logging in after system boot)
6. wait a few moments, so wifi will try to connect


Actual Results:  
network manager seems to get into somekind of loop with connect... disconnect.. connect.. disconnect.

Will only get out of this loop when pressing "disconnect" and "connect" on the wifi interface

Expected Results:  
wifi gets connected and after that openvpn also
Comment 1 Jan Grulich 2014-11-03 08:37:02 UTC 
What version of plasma-nm do you have? Where do you have stored secrets, is that in KWallet?
Comment 2 rolandu 2014-11-03 08:45:17 UTC 
(In reply to Jan Grulich from comment #1)
> What version of plasma-nm do you have? 
Application: plasma-nm/editor
Version: 0.9.3.3

Using NM version: 0.9.8.8

> Where do you have stored secrets, is that in KWallet?

Yes, I looked in kde wallet manager, shows vpn entries under 'Network management / Maps'.
Comment 3 Jan Grulich 2014-11-26 10:50:33 UTC 
This is unfortunately behavior of NetworkManager. It keeps trying to activate your connections again and again until you stop it. Another problem is that when you tie a VPN connection with another connection then when it fails to activate that VPN connection it also automatically fails to activate the connection used as a base for the VPN connection. This is something we can't fix on our side. 

What I see as a problem on our side is the one with failing to get secrets for your VPN connection.  Would it be possible for you to update to the latest version of plasma-nm? There were many fixes regarding storing/loading secrets and so on.
Comment 4 Jan Grulich 2015-02-13 14:06:46 UTC 
I believe that this issue is already solved, password storing/loading has been improved since plasma-nm 0.9.3.3. Reopen this bugzilla if you are able to reproduce this issue with plasma-nm 0.9.3.5.
Comment 5 Ben Cooksley 2024-12-23 18:23:44 UTC 
Bulk transfer as requested in T17796