All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: Valdis.Kletnieks@vt.edu
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 10:03:54 +0100	[thread overview]
Message-ID: <201003171003.54295.holgerschurig@gmail.com> (raw)
In-Reply-To: <27228.1268814093@localhost>

> The problem is a combination of things - (a) iwlist and iwconfig report no
> crypto and (b) there doesn't seem to be any *other* way for userspace to
> find out that in fact you have an encrypted WPA2 connection.

That's not true.


I'm using cfg80211 with wpa_supplicant (even when I only use WEP, despite the 
name of the wpa_supplicant application!).

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:

# wpa_cli status
Selected interface 'wlan0'
bssid=00:xx:xx:xx:xx:xx
ssid=MUMBLEFUTZ
id=0
mode=station
pairwise_cipher=WEP-40
group_cipher=WEP-40
key_mgmt=NONE
wpa_state=COMPLETED
ip_address=172.16.xxx.xx

-- 
http://www.holgerschurig.de

  reply	other threads:[~2010-03-17  9:02 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 [this message]
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=201003171003.54295.holgerschurig@gmail.com \
    --to=holgerschurig@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --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.