From: Valdis.Kletnieks@vt.edu
To: Holger Schurig <holgerschurig@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Weird wireless/wpa_supplicant screw-up.
Date: Wed, 17 Mar 2010 16:29:47 -0400 [thread overview]
Message-ID: <24712.1268857787@localhost> (raw)
In-Reply-To: Your message of "Wed, 17 Mar 2010 10:03:54 BST." <201003171003.54295.holgerschurig@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
On Wed, 17 Mar 2010 10:03:54 BST, Holger Schurig said:
> And in this case, you can use "wpa_cli status" and well see all the details,
> no matter if you use WPA, WPA2, WEXT or some of the 802.11x derivates:
Wow. Is *that* where they hid it?
In any case, that does fit the bill, even if it was well-hidden:
# wpa_cli status
Selected interface 'wlan0'
bssid=00:0f:f7:14:2a:91
ssid=VT-Wireless
id=0
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2/IEEE 802.1X/EAP
wpa_state=COMPLETED
ip_address=172.31.143.252
Supplicant PAE state=AUTHENTICATED
suppPortStatus=Authorized
EAP state=SUCCESS
selectedMethod=13 (EAP-TLS)
EAP TLS cipher=DHE-RSA-AES256-SHA
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2010-03-17 20:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 22:22 Weird wireless/wpa_supplicant screw-up Valdis.Kletnieks
2010-03-12 11:14 ` 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 [this message]
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=24712.1268857787@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=holgerschurig@gmail.com \
--cc=johannes@sipsolutions.net \
--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.