Bug 1665694 - Cannot connect to 5G Wireless Access Point after upgrade to FC29
Summary: Cannot connect to 5G Wireless Access Point after upgrade to FC29
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 29
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-13 01:26 UTC by JNoake
Modified: 2019-11-27 20:41 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 20:41:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description JNoake 2019-01-13 01:26:58 UTC
Description of problem:
After upgrading FC27 to FC29, Network Manager can 'see' my 5G wireless access point but is unable to negotiate a connection.

Version-Release number of selected component (if applicable):
wpa_supplicant-2.7-1.fc29.x86_64

How reproducible:
Disabling PMF with the following command :
$ nmcli connection modify MY_APNAME-5G wifi-sec.pmf disable; nmcli connection up MY_APNAME-5G

Allows connection to the 5G access point.

Re-enabling PMF with the following command:
$ nmcli connection modify MY_APNAME-5G wifi-sec.pmf default; nmcli connection up MY_APNAME-5G

Returns the failure to negotiate a connection.

Steps to Reproduce:
1. Attempt connection to a 5G access point that supports PMF with PMF enabled on the client.
2. Fail to get IP.
3.

Actual results:
Unable to connect to 5G PMF supported Wireless Access Point.

Expected results:
Should be able to connect to a 5G wireless Access Point that supports PMF with client PMF set at 'default'

Additional info:
Messages log:
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9040] device (wlp12s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9044] device (wlp12s0): Activation: (wifi) access point 'MY_APNAME-5G' has security, but secrets are required.
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9045] device (wlp12s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jan 12 21:11:38 my-hostname kdeinit5[1618]: plasma-nm: Unhandled active connection state change:  1
Jan 12 21:11:38 my-hostname kdeinit5[1618]: plasma-nm: Unhandled active connection state change:  1
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9629] device (wlp12s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9681] device (wlp12s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9707] device (wlp12s0): Activation: (wifi) connection 'MY_APNAME-5G' has security, and secrets exist.  No new secrets needed.
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9710] Config: added 'ssid' value 'MY_APNAME-5G'
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9711] Config: added 'scan_ssid' value '1'
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9713] Config: added 'bgscan' value 'simple:30:-80:86400'
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9715] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9716] Config: added 'auth_alg' value 'OPEN'
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9718] Config: added 'psk' value '<hidden>'
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9719] Config: added 'ieee80211w' value '1'
Jan 12 21:11:38 my-hostname NetworkManager[1057]: <info>  [1547327498.9890] device (wlp12s0): supplicant interface state: inactive -> scanning
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: SME: Trying to authenticate with 60:03:47:39:7e:e3 (SSID='MY_APNAME-5G' freq=5500 MHz)
Jan 12 21:11:41 my-hostname kernel: wlp12s0: authenticate with 60:03:47:39:7e:e3
Jan 12 21:11:41 my-hostname kernel: wlp12s0: send auth to 60:03:47:39:7e:e3 (try 1/3)
Jan 12 21:11:41 my-hostname NetworkManager[1057]: <info>  [1547327501.5804] device (wlp12s0): supplicant interface state: scanning -> authenticating
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: Trying to associate with 60:03:47:39:7e:e3 (SSID='MY_APNAME-5G' freq=5500 MHz)
Jan 12 21:11:41 my-hostname kernel: wlp12s0: authenticated
Jan 12 21:11:41 my-hostname kernel: wlp12s0: associate with 60:03:47:39:7e:e3 (try 1/3)
Jan 12 21:11:41 my-hostname kernel: wlp12s0: RX AssocResp from 60:03:47:39:7e:e3 (capab=0x11 status=0 aid=1)
Jan 12 21:11:41 my-hostname NetworkManager[1057]: <info>  [1547327501.6346] device (wlp12s0): supplicant interface state: authenticating -> associating
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: Associated with 60:03:47:39:7e:e3
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 12 21:11:41 my-hostname kernel: wlp12s0: associated
Jan 12 21:11:41 my-hostname NetworkManager[1057]: <info>  [1547327501.6420] device (wlp12s0): supplicant interface state: associating -> associated
Jan 12 21:11:41 my-hostname NetworkManager[1057]: <info>  [1547327501.6636] device (wlp12s0): supplicant interface state: associated -> 4-way handshake
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: WPA: Key negotiation completed with 60:03:47:39:7e:e3 [PTK=CCMP GTK=CCMP]
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: CTRL-EVENT-CONNECTED - Connection to 60:03:47:39:7e:e3 completed [id=0 id_str=]
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: WPA: Failed to configure IGTK to the driver
Jan 12 21:11:41 my-hostname kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp12s0: link becomes ready
Jan 12 21:11:41 my-hostname kernel: wlp12s0: deauthenticating from 60:03:47:39:7e:e3 by local choice (Reason: 1=UNSPECIFIED)
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: RSN: Failed to configure IGTK
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: CTRL-EVENT-DISCONNECTED bssid=60:03:47:39:7e:e3 reason=1 locally_generated=1
Jan 12 21:11:41 my-hostname wpa_supplicant[1160]: wlp12s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

Similar to bug 1599036 (FC28, closed)
and
bug 1578486 (FC28, Closed)

Comment 1 JNoake 2019-01-13 01:31:13 UTC
Further information:

Able to connect to 2.4g, but not 5g.
I have a Billion BiPAC 8800AXL R2 and it has a 5G option for :
 	
Protected Management Frames 	Disable|Capable|Required

Set to Capable, my Laptop was still was unable to connect.

Comment 2 Beniamino Galvani 2019-01-15 08:04:24 UTC
Can you please install the new NM package from the testing repository, set PMF back to 'optional' and check if you can connect?

 sudo dnf upgrade --enablerepo updates-testing NetworkManager
 sudo systemctl restart NetworkManager
 nmcli connection modify MY_APNAME-5G wifi-sec.pmf optional
 nmcli connection up MY_APNAME-5G

Comment 3 Ben Cotton 2019-10-31 20:10:22 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 4 Ben Cotton 2019-11-27 20:41:41 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.