From: Valdis.Kletnieks@vt.edu
To: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Weird wireless/wpa_supplicant screw-up.
Date: Mon, 08 Mar 2010 17:22:19 -0500 [thread overview]
Message-ID: <7197.1268086939@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
(This could be user error/userspace bug, feel free to point me in the right
direction if you think so. Hopefully somebody knows what I've broken this
time...)
Fedora Rawhide as of this morning, 2.6.33-mmotm0304 kernel, wpa_supplicant-0.6.8-8.fc13.x86_64
wireless-tools-29-5.1.fc12.x86_64. Dell Latitude E6500, Intel 5100AGN card.
So I finally get a few spare cycles, and re-try getting WPA2 working on our
enterprise wireless network, and wpa_supplicant reports it completed
successfully and set the keys, but 'iwconfig' reports back:
wlan0 IEEE 802.11abgn ESSID:"VT-Wireless"
Mode:Managed Frequency:2.412 GHz Access Point: 00:0F:F7:14:2A:91
Bit Rate=1 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=42/70 Signal level=-68 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
No encryption key. Yee. Hah.
But wait... 'iwlist keys' reports:
wlan0 2 key sizes : 40, 104bits
4 keys available :
[1]: off
[2]: 6A7D-5232-BDE6-E40A-71C5-EC21-6399-00F3-5CAD-D394-D1E5-1261-BD99-0115-F4A8-63B2 (256 bits)
[3]: off
[4]: off
Current Transmit Key: [1]
So we got a perfectly good key, but we're not using it.
Anybody got any ideas/hints?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2010-03-08 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 22:22 Valdis.Kletnieks [this message]
2010-03-12 11:14 ` Weird wireless/wpa_supplicant screw-up Johannes Berg
2010-03-12 11:16 ` Johannes Berg
2010-03-12 21:49 ` Valdis.Kletnieks
2010-03-12 22:19 ` Pavel Roskin
2010-03-12 22:22 ` Valdis.Kletnieks
2010-03-13 3:09 ` Johannes Berg
2010-03-17 3:06 ` Valdis.Kletnieks
2010-03-17 3:22 ` Johannes Berg
2010-03-17 8:21 ` Valdis.Kletnieks
2010-03-17 9:03 ` Holger Schurig
2010-03-17 20:29 ` Valdis.Kletnieks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7197.1268086939@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.