Description of problem: at our company we use 802.1x security for wired connections. 802.1x settings are PEAP authentication, no CA certificate, automativ PEAP version and MSCHAPv2 inner authentication. When trying to connect to the network the password dialogue pops up, when entering the password and pressing ok the password dialogue pops up again, nothing else happens. Version-Release number of selected component (if applicable): [root@midr-fedora-lap ~]# rpm -qa|grep Network NetworkManager-1.2.0-0.8.rc2.fc24.x86_64 How reproducible: always Steps to Reproduce: 1. configure 802.1x security as described above 2. connect to network 3. enter user password Actual results: user password is asked again and again Expected results: Network connection gets established Additional info: this works fine under Fedora 23. Setting 802.1x directly in the wpa_supplicant config/cli does get the connection to be established. Also the same behavior seems to take place in recent Ubuntu 16.04 where it also works in prior ubuntu release, so it looks like the might be a general NetworkManager problem in version 1.2 Some log snippets from NetworkManager I collected after setting debug output: Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4353] agent-manager: req[0x5632b9077bd0, :1.21/org.freedesktop.nm-applet/1000]: agent returned secrets for request [0x5632b8fe1a00/"802.1x"/"802-1x"] Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4402] device[0x5632b8fcc4a0] (enp0s25): activation-stage: schedule activate_stage1_device_prepare,2 (id 20154) Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4403] device[0x5632b8fcc4a0] (enp0s25): activation-stage: invoke activate_stage1_device_prepare,2 (id 20154) Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <info> [1465557484.4403] device (enp0s25): state change: need-auth -> prepare (reason 'none') [60 40 0] Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4406] device[0x5632b8fcc4a0] (enp0s25): no MAC address change needed Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4406] device[0x5632b8fcc4a0] (enp0s25): activation-stage: schedule activate_stage2_device_config,2 (id 20158) Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4406] device[0x5632b8fcc4a0] (enp0s25): activation-stage: complete activate_stage1_device_prepare,2 (id 20154) Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4408] device[0x5632b8fcc4a0] (enp0s25): activation-stage: invoke activate_stage2_device_config,2 (id 20158) Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <info> [1465557484.4409] device (enp0s25): state change: prepare -> config (reason 'none') [40 50 0] Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <info> [1465557484.4418] device (enp0s25): Activation: (ethernet) connection '802.1x' has security, but secrets are required. Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <info> [1465557484.4419] device (enp0s25): state change: config -> need-auth (reason 'none') [50 60 0] Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4436] agent-manager: req[0x5632b9077bd0, :1.21/org.freedesktop.nm-applet/1000]: agent allowed for secrets request [0x5632b90481b0/"802.1x"/"802-1x"] Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4436] device[0x5632b8fcc4a0] (enp0s25): activation-stage: complete activate_stage2_device_config,2 (id 20158) Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4442] agent-manager: req[0x5632b9077bd0, :1.21/org.freedesktop.nm-applet/1000]: agent getting secrets for request [0x5632b90481b0/"802.1x"/"802-1x"] Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4443] agent-manager: ([0x5632b90481b0/"802.1x"/"802-1x"]) request has system secrets; checking agent :1.21 for MODIFY Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4443] auth: call[175]: CheckAuthorization(org.freedesktop.NetworkManager.settings.modify.system), subject=unix-process[pid=1606, uid=1000, start=1612] Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4647] auth: call[175]: CheckAuthorization succeeded: (is_authorized=1, is_challenge=0) Jun 10 13:18:04 midr-fedora-lap NetworkManager[1189]: <debug> [1465557484.4648] agent-manager: req[0x5632b9077bd0, :1.21/org.freedesktop.nm-applet/1000]: agent [0x5632b90481b0/"802.1x"/"802-1x"] MODIFY check result YES
Update: This might be a gui only problem, must likely with the credentials part. I found that when set all 802 security options in the gui and save the connection details, and then run nmcli --ask connection up <interface> from the command line everything works fine onward.
Fixed: https://bugzilla.gnome.org/show_bug.cgi?id=769661
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.