Bug 1767446 - Unable to connect to WiFi network after upgrade to fedora 31
Summary: Unable to connect to WiFi network after upgrade to fedora 31
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wpa_supplicant
Version: 31
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-31 13:33 UTC by Florian Wallner
Modified: 2020-11-24 17:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 17:38:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Florian Wallner 2019-10-31 13:33:41 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Build Identifier: 

wpa_supplicant is unable to establish a connection to our company wifi since updating to fedora 31. It used to work before. According to the logs authentication works just fine and there is a problem following authentication. The relevant lines from the journal:

wpa_supplicant[2333]: EAP-MSCHAPV2: Authentication succeeded
wpa_supplicant[2333]: EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed
wpa_supplicant[2333]: wlp58s0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
wpa_supplicant[2333]: wlp58s0: FT: AP did not use AES-128-CMAC
wpa_supplicant[2333]: wlp58s0: FT: AP did not use AES-128-CMAC
wpa_supplicant[2333]: wlp58s0: FT: AP did not use AES-128-CMAC
wpa_supplicant[2333]: wlp58s0: CTRL-EVENT-DISCONNECTED bssid=b0:b8:67:e1:9f:11 reason=3 locally_generated= wpa_supplicant[2333]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3



Reproducible: Always

Steps to Reproduce:
1.select the WiFi network from the list of available networks
2.try to connect to it
3.
Actual Results:  
The WiFi connection cannot be established

Expected Results:  
The connection can be established.

Comment 1 Florian Wallner 2019-11-06 22:28:39 UTC
A downgrade to the package wpa_supplicant-2.7-5 rebuild from fedora 30 source rpm fixes the problem and wifi is working again.
The access points of the wifi network in question support AES-CBC and AES-CTR to the IT department. So I guess a change in the upgrade broke the functionality.

Comment 2 Ben Cotton 2020-11-03 16:54:10 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-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 '31'.

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 31 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 3 Ben Cotton 2020-11-24 17:38:57 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.


Note You need to log in before you can comment on or make changes to this bug.