Bug 1399892

Summary: Failure switching between wireless networks with NetworkManager
Product: [Fedora] Fedora Reporter: Lucious <malucious81>
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 25CC: dcbw, dowdle, fgiudici, lkundrak
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: 2017-12-12 10:09:05 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:
Attachments:
Description Flags
Hardware. lspci none

Description Lucious 2016-11-30 02:22:53 UTC
Created attachment 1226096 [details]
Hardware. lspci

Description of problem:

NetworkManager fails to connect when switching between known authenticated wireless networks, since upgrading to Fedora 25.

Version-Release number of selected component (if applicable):
NetworkManager-1.4.2-1.fc25.x86_64


How reproducible: Very


Steps to Reproduce:
1. Connect to a wireless network.
2. Switch to another wireless network.

Actual results:
The connection attempt will fail/timeout with this output from dmesg.

aborting authentication with (mac address) by local choice (Reason: 3=DEAUTH_LEAVING)

Afterwards, NetworkManager will fail back to the previous wireless network successfully.

Additional info: 

03:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
Kernel driver in use: iwlwifi

Restarting NetworkManager temporarily fixes the problem.

Comment 1 Scott Dowdle 2016-11-30 11:34:15 UTC
With the most recent batch of updates, wifi on my laptop is broken as well.  I don't have to try to switch between networks... just trying to use what has been my default for a long time no longer works... and the logs say it fails to authenticate.  There was a kernel update (4.8.10-100) along with NetworkManager updates so I'm not sure what is exactly responsible... NM I would assume.  I can provide additional info (make/model of laptop and wifi card) but I'm guessing this is not limited to particular hardware.

Comment 2 Lucious 2016-12-30 00:03:10 UTC
My problem seems to be related to this bug:  https://bugzilla.gnome.org/show_bug.cgi?id=770456

I applied the work-around adding:

 [device]
  wifi.scan-rand-mac-address=no

to my /etc/NetworkManager/NetworkManager.conf file. And after rebooting, it seems to have fixed the connection issues.

Comment 3 Fedora End Of Life 2017-11-16 19:53:44 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 Fedora End Of Life 2017-12-12 10:09:05 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.