Bug 1594557

Summary: Networkmanager does not connect to wifi and keeps asking for password
Product: [Fedora] Fedora Reporter: slartibart70
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 28CC: alexl, bgalvani, dcbw, fgiudici, john.j5live, lkundrak, mclasen, rhughes, rstrode, sandmann, slartibart70
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 20:51:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logfiles none

Description slartibart70 2018-06-24 11:31:09 UTC 
Hi,

if have an rtl8712u based usb wifi adapter which was working properly in fedora27. Since upgrade to fedora28, networkmanager keeps asking for the password and does not connect to the wifi. The password is indeed correct, but it still won't connect.

dmesg indicates no problem with kernel 4.16.16

usb 2-1.2: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
usbcore: registered new interface driver r8712u
r8712u 2-1.2:1.0 wlp0s29u1u2: renamed from wlan0
IPv6: ADDRCONF(NETDEV_UP): wlp0s29u1u2: link is not ready

the outputs are the same compared to kernel 4.16.17 of fedora 27, where it connects successfully.

Even the commandline approach won't work:
nmcli d wifi connect LINKSYS password mypassword ifname wlp0s29u1u2

which gives the error message
Error: Connection activation failed: (7) Secrets were required, but not provided.

(same thing works properly in fedora27)

Any ideas what other logs i could provide?
Any chance of fixing this bug?
Comment 1 Beniamino Galvani 2018-06-27 09:50:49 UTC 
Hi,

can you please do the following:

 1. set level=TRACE in the [logging] section of
    /etc/NetworkManager/NetworkManager.conf

 2. append "-dd" to OTHER_ARGS variable in /etc/sysconfig/wpa_supplicant.
    For example: OTHER_ARGS="-u -P /var/run/wpa_supplicant.pid -s -dd"

 3. systemctl restart wpa_supplicant
 4. systemctl restart NetworkManager
 5. try to connect
 6. attach the output of:
    journalctl -u NetworkManager -u wpa_supplicant --since="2 minutes ago"

 7. attach the output of:  "iw phy0 info; lshw -c net"

Thanks!

Also, can you please try disabling PMF for the Wi-Fi connection is the following way:

 nmcli connection modify <name-of-wifi-connection> wifi-sec.pmf disable

and try to connection again?
Comment 2 slartibart70 2018-07-04 19:00:53 UTC 
please find the output attached here (data.7z)
Comment 3 slartibart70 2018-07-04 19:01:33 UTC 
Created attachment 1456599 [details]
logfiles
Comment 4 slartibart70 2018-07-04 19:17:39 UTC 
additionally, i followed your second request:

nmcli connection modify uuid 265552e7-8c7e-484b-9dfb-363b7193bdc2 wifi-sec.pmf disable

nmcli connection up uuid 265552e7-8c7e-484b-9dfb-363b7193bdc2 --ask
Passwords or encryption keys are required to access the wireless network 'WLAN-6F2848'.
Password (802-11-wireless-security.psk): 
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/13)

...and, it's working!

so, what is the fuzz about wifi-sec.pmf?
Why does disabling protected management frames help? wifi-usb-stick too old?
Comment 5 Ben Cotton 2019-05-02 21:29:08 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.
Comment 6 Ben Cotton 2019-05-28 20:51:21 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.