Hi, I have Kubuntu 12.10 with kde 4.9.2.

My wired network connection is secured by 802.1x with TLS. I have all things set up properly and selected to store my private key password.

Now there is a problem, when I startup KDE / plugin my network cable a dialog appears with a password request. I double checked that - it's the same password in the preferences, of course with the password provided network is working fine.

Any clues on that ?

Can you confirm that this is a network password dialog rather than a KWallet dialog?
(The KWallet dialog will have references to opening a wallet, etc).

I think, it's not the one from kwallet, but I could be wrong, here is a screenshot: http://i.imgur.com/0NCWu.png

When I changed settings in the 'other' tab to store confidential data unencrypted that dialog does not appear but the connection is not configured then with a message in the syslog:
10/10/2012 07:38:20 piotrus-ThinkPad-W520 NetworkManager[1121] <info> (eth0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]


Additionally in the syslog, while plugging in the cable I can see the information that:
10/10/2012 07:41:21 piotrus-ThinkPad-W520 NetworkManager[1121] <info> Config: added 'private_key_passwd' value '<omitted>'

then

10/10/2012 07:40:15 piotrus-ThinkPad-W520 NetworkManager[1121] <info> Activation (eth0/wired): connection 'kabel praca' has security, but secrets are required.

and the dialog appears.

Hope that will clear things a little bit.

Thanks !

That is definitely the network password dialog.

Is the "eth0" connection a system one or a user one?
Also, can you please provide the version of NetworkManager in use?

here is the version info: 0.9.0.5 (nm09 20120930)

eth0 is configured as a system connection with autoconnect option on

Have you followed this step to configure your connection? https://bugs.kde.org/show_bug.cgi?id=279942#c25

If it is a system connection then NetworkManager is responsible for storing any secrets for the connection. That problemay should not happen.

Update: I forgout about this other bug https://bugs.kde.org/show_bug.cgi?id=308062, I think that is what is causing you troubles.

As for now the solution that worked for me was to uncheck the 'System connection' box - then I got only the dialog ( obviously not needed one ) informing me that the secure connection is about to start, but at least no password required. The second bug you mention has been created by myself.

Anyway, thanks for your help

piotrd wrote:As for now the solution that worked for me was to uncheck the 'System connection' box ...

For me, it was not enough.
I'm using version 0.9.0.8 (nm09 20130310), but can't authenticate through 802.1x.
That boring password request dialog continues appearing.
Any other tips?

Does the NetworkManager log reveal if it is failing to retrieve the password, or if actual authentication to the network is failing?
It is possible that additional packages may be needed to enable 802.1x support.

Thanks bcooksley!

See the log below.
It seems that NetworkManager don't recognize the secrets I place, neither on the network config, nor on the secrets dialog.

Furthermore, it shows a weird sequence:
connection 'Conexao 802.1x' has security, but secrets are required.

then:
connection 'Conexao 802.1x' requires no security. No secrets needed.

and so it shows me the dialog:
asking for new secrets

and again:
connection 'Conexao 802.1x' requires no security. No secrets needed.

and finishing:
need-auth -> failed (reason 'no-secrets')

Code: Select all

Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) starting connection 'Conexao 802.1x'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0/wired): connection 'Conexao 802.1x' has security, but secrets are required.
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0): device state change: config -> need-auth (reason 'none') [50 60 0]
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0/wired): connection 'Conexao 802.1x' requires no security. No secrets needed.
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0) supports 0 scan SSIDs
Jul  2 07:30:24 machine NetworkManager[1324]: <warn> Trying to remove a non-existant call id.
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0): supplicant interface state: starting -> ready
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: added 'password' value '<omitted>'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: added 'key_mgmt' value 'IEEE8021X'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: added 'eapol_flags' value '0'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: added 'eap' value 'PEAP'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: added 'fragment_size' value '1300'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: added 'phase1' value 'peapver=0'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: added 'phase2' value 'auth=MSCHAPV2'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: added 'identity' value 'user'
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0): supplicant interface state: ready -> inactive
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0) supports 0 scan SSIDs
Jul  2 07:30:24 machine NetworkManager[1324]: <info> Config: set interface ap_scan to 0
Jul  2 07:30:24 machine wpa_supplicant[1458]: eth0: Associated with 01:80:c2:00:00:03
Jul  2 07:30:24 machine NetworkManager[1324]: <info> (eth0): supplicant interface state: inactive -> associated
Jul  2 07:30:49 machine NetworkManager[1324]: <warn> Activation (eth0/wired): association took too long.
Jul  2 07:30:49 machine NetworkManager[1324]: <info> (eth0): device state change: config -> need-auth (reason 'none') [50 60 0]
Jul  2 07:30:49 machine NetworkManager[1324]: <info> Activation (eth0/wired): asking for new secrets
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jul  2 07:30:57 machine NetworkManager[1324]: <info> (eth0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jul  2 07:30:57 machine NetworkManager[1324]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Activation (eth0/wired): connection 'Conexao 802.1x' requires no security. No secrets needed.
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jul  2 07:30:57 machine NetworkManager[1324]: <info> (eth0) supports 0 scan SSIDs
Jul  2 07:30:57 machine NetworkManager[1324]: <warn> Trying to remove a non-existant call id.
Jul  2 07:30:57 machine NetworkManager[1324]: <info> (eth0): supplicant interface state: starting -> ready
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: added 'password' value '<omitted>'
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: added 'key_mgmt' value 'IEEE8021X'
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: added 'eapol_flags' value '0'
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: added 'eap' value 'PEAP'
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: added 'fragment_size' value '1300'
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: added 'phase1' value 'peapver=0'
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: added 'phase2' value 'auth=MSCHAPV2'
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: added 'identity' value 'user'
Jul  2 07:30:57 machine NetworkManager[1324]: <info> (eth0): supplicant interface state: ready -> inactive
Jul  2 07:30:57 machine NetworkManager[1324]: <info> (eth0) supports 0 scan SSIDs
Jul  2 07:30:57 machine NetworkManager[1324]: <info> Config: set interface ap_scan to 0
Jul  2 07:30:57 machine wpa_supplicant[1458]: eth0: Associated with 01:80:c2:00:00:03
Jul  2 07:30:57 machine NetworkManager[1324]: <info> (eth0): supplicant interface state: inactive -> associated
Jul  2 07:31:22 machine NetworkManager[1324]: <warn> Activation (eth0/wired): association took too long.
Jul  2 07:31:22 machine NetworkManager[1324]: <info> (eth0): device state change: config -> need-auth (reason 'none') [50 60 0]
Jul  2 07:31:22 machine NetworkManager[1324]: <info> Activation (eth0/wired): asking for new secrets
Jul  2 07:31:32 machine NetworkManager[1324]: <warn> No agents were available for this request.
Jul  2 07:31:32 machine NetworkManager[1324]: <info> (eth0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Jul  2 07:31:32 machine NetworkManager[1324]: <info> Marking connection 'Conexao 802.1x' invalid.
Jul  2 07:31:32 machine NetworkManager[1324]: <warn> Activation (eth0) failed for connection 'Conexao 802.1x'
Jul  2 07:31:32 machine NetworkManager[1324]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jul  2 07:31:32 machine NetworkManager[1324]: <info> (eth0): deactivating device (reason 'none') [0]


1 Jul 2 07:30:24 machine wpa_supplicant[1458]: eth0: Associated with 01:80:c2:00:00:03
2 Jul 2 07:30:24 machine NetworkManager[1324]: <info> (eth0): supplicant interface state: inactive -> associated
3 Jul 2 07:30:49 machine NetworkManager[1324]: <warn> Activation (eth0/wired): association took too long.
4 Jul 2 07:30:49 machine NetworkManager[1324]: <info> (eth0): device state change: config -> need-auth (reason 'none') [50 60 0]
5 Jul 2 07:30:49 machine NetworkManager[1324]: <info> Activation (eth0/wired): asking for new secrets

By what I can see in those lines it associates in line 1 and 2. In line 3 NetworkManager reaches a 15s timeout. I am not sure what that timeout is used for. If it is the dhcp client timeout then maybe your dhcp server is being too slow to send the configuration and that can explain why the connection is being dropped. NetworkManager usually "thinks" the password is wrong there an error in the connection activation, so it usually asks for new secrets (line 5) when any error happens.

Thanks lamarque!

At the very beginning I thought the problem was at the server side, but other people got it using Ubuntu and Windows 7, using the same server, so I focused on the KDE NetworkManager.
Is there another way to test it (through CLI or another GUI)?

Looking at NetworkManager's source code that timeout should be 25s not 15s. Anyway, that is a supplicant timeout, then wpa_supplicant must be having problems to complete the activation in despite of the "(eth0): supplicant interface state: inactive -> associated" message. Which wpa_supplicant version do you use? That timeout is really old, from 2008 according to NetworkManager's git log, so it is probably a problem with wpa_supplicant, not NetworkManager.

Thanks lamarque,

My wpasupplicant version is 1.0-3ubuntu1.
I think it's the original one, from Kubuntu 13.04, unless it has been changed by another application.
I saw there is a new version (2.0), but is it the stable one?

I think it is. That is the wpa_supplicant version I use.