Bug 831060 - Can't connect to wireless-n 5GHz (Intel iwlwifi 6200)
Summary: Can't connect to wireless-n 5GHz (Intel iwlwifi 6200)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-12 06:19 UTC by Gerard Fernandes
Modified: 2012-06-14 20:53 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-14 13:14:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gerard Fernandes 2012-06-12 06:19:25 UTC
Description of problem: Can't connect to Wireless-N on 5GHz


Version-Release number of selected component (if applicable): (output from dmesg)
[    6.735324] iwlwifi 0000:08:00.0: Detected Intel(R) Centrino(R) Advanced-N 6200 AGN, REV=0x74
[    6.735468] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
[    6.753049] iwlwifi 0000:08:00.0: device EEPROM VER=0x436, CALIB=0x6
[    6.753054] iwlwifi 0000:08:00.0: Device SKU: 0x1F0
[    6.753056] iwlwifi 0000:08:00.0: Valid Tx ant: 0x6, Valid Rx ant: 0x6
[    6.753078] iwlwifi 0000:08:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels



How reproducible: Always


Steps to Reproduce:
1. Attempt to connect to Wireless-N 5GHz network

  
Actual results: Fails - comes back to password dialogue.


Expected results: Should connect - used to work in F-16.


Additional info:

Comment 1 Gerard Fernandes 2012-06-12 09:11:35 UTC
Router is a Netgear WNDR3500 dual radio (2.4GHz G, 5GHz N). I can connect to 2.4GHz G, but connection _always_ fails to 5GHz N.

Comment 2 Gerard Fernandes 2012-06-12 09:12:47 UTC
WNDR-3700 I mean.

Comment 3 John W. Linville 2012-06-12 14:44:11 UTC
What kernel version are you using?

What sort of encryption are you using on your network?

Comment 4 Gerard Fernandes 2012-06-12 19:01:55 UTC
Kernel version: kernel-3.4.0-1.fc17.x86_64
Network is setup to use WPA-2 (AES) encryption.

Comment 5 John W. Linville 2012-06-13 11:42:02 UTC
Please attach the contents of /var/log/wpa_supplicant.log and /var/log/messages from immediately after an unsuccessful connection attempt.

Comment 6 Gerard Fernandes 2012-06-13 19:36:50 UTC
Thanks for pointing me at the logs. I've found the problem.

My WPA-2 password is a 64-char long auto-generated random string. The last character was a "\".

This was being saved incorrectly in the key-ring as a "'" character. This caused password authentication to fail.

I tried manually editing it a few times in NetworkManager without success.

I swapped the last 2 chars around and now I can connect.

This is quite strange - I've never experienced this problem in the past (had the exact same password on Fedora-16 and it was saved correctly in the key-ring).

Don't know exactly what the cause of this problem is. But as the connection works now, this issue can be closed.

Comment 7 Gerard Fernandes 2012-06-14 09:24:47 UTC
>>I swapped the last 2 chars around and now I can connect.

(This also meant making the exact same change to the password on the router of course...)

Comment 8 John W. Linville 2012-06-14 13:14:57 UTC
Closing as NOTABUG, based on documented info in comment 6 and comment 7.

FWIW, I would guess that some other form of quoting/escaping would allow for the last character to be '\', but I think you current solution is as good as any. :-)

Comment 9 Gerard Fernandes 2012-06-14 20:53:00 UTC
:)
Thankyou for your help.


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