Bug 1272736

Summary: NetworkManager stays in Connecting mode, then fails
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: dcbw, lkundrak, psimerda, rkhan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:15:52 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
tail of wpa supplicant log
none
dmesg output
none
iwlist scan output none

Description Peter H. Jones 2015-10-18 10:58:50 UTC
Created attachment 1084110 [details]
tail of wpa supplicant log

Description of problem:
NetworkManager fails to complete wifi connection in a place with excellent signal strenght

Version-Release number of selected component (if applicable):
NetworkManager.x86_64-1.0.6-6.fc22

How reproducible:
Every time

Steps to Reproduce:
1. Try to make a wifi connection

Actual results:
Connection is in Connecting state for a few minutes, then Connection Failed message appears

Expected results:
Successful connection

Additional info:
An Ipad Air 2 connects with no problem.

Comment 1 Peter H. Jones 2015-10-18 10:59:37 UTC
Created attachment 1084111 [details]
dmesg output

Comment 2 Peter H. Jones 2015-10-18 11:00:44 UTC
Created attachment 1084112 [details]
iwlist scan output

Network of interest is "MANOIR 12"

Comment 3 Jirka Klimes 2015-10-19 08:09:12 UTC
The problem may be caused by regulatory domain changes.
Is the regulatory domain set to "CA" before connecting?

Try if setting it manually before connection help:
$ sudo iw reg set CA

Also check that "sudo setregdomain" can set the domain correctly.

Links:
http://ubuntuforums.org/showthread.php?t=2259037&p=13198699#post13198699
https://bugzilla.redhat.com/show_bug.cgi?id=806221

Comment 4 Peter H. Jones 2015-10-19 09:36:33 UTC
I'll be in the location of the wifi next Sunday. I'll try the suggestions in comment 3 then.

Comment 5 Peter H. Jones 2015-10-19 13:10:59 UTC
Today, not in the location, I did:
"# iw reg get
global
country CA: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)

# iw reg set CA
# iw reg get
global
country CA: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
# setregdomain
# iw reg get
global
country CA: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5170 - 5250 @ 80), (N/A, 17), (N/A), AUTO-BW
	(5250 - 5330 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
	(5490 - 5730 @ 160), (N/A, 24), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)"

Looks good, as far as I can see. I'll try again at the location.

Comment 6 Fedora End Of Life 2016-07-19 18:15:52 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.