From: Dan Williams <dcbw@redhat.com>
To: "J.A. Magallón" <jamagallon@ono.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Problems with ath5k and WPA2 keys
Date: Fri, 25 Dec 2009 14:12:30 -0600 [thread overview]
Message-ID: <1261771950.7657.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20091224105648.6b3ae67e@werewolf.home>
On Thu, 2009-12-24 at 10:56 +0100, J.A. Magallón wrote:
> Hi all...
>
> With last 2.6.32.2 kernel, I can't connect to my home WiFi router.
> I use WPA2+PSK mode.
>
> I have discovered it's related to key length:
>
> one:~# iwconfig wlan0 key s:password
> Error for wireless request "Set Encode" (8B2A) :
> SET failed on device wlan0 ; Invalid argument.
> one:~# iwconfig wlan0 key s:passwor
> Error for wireless request "Set Encode" (8B2A) :
> SET failed on device wlan0 ; Invalid argument.
> one:~# iwconfig wlan0 key s:passwo
> Error for wireless request "Set Encode" (8B2A) :
> SET failed on device wlan0 ; Invalid argument.
> one:~# iwconfig wlan0 key s:passw
>
> (this last works...)
>
> So network scripts can not set my key...
iwconfig does not do WPA. You want wpa_supplicant if you want to make
WPA connections, because a daemon is required to handle the rekeying and
other WPA operations. WPA is a lot more complex and thus you cannot
just use command-line tools.
The reason iwconfig only accepts certain key lengths is because it can
only accept WEP keys, and WEP keys have specific key lengths. WEP Hex
keys can be either 10 or 26 hex characters, and WEP ASCII keys can
either be 5 or 13 characters. Which is why the last example above
works; because the key is 5 ASCII characters.
But in the end, if you're using WPA, you want to use wpa_supplicant to
set up and manage the connection, or a connection manager like
NetworkManager. Plain iwconfig simply does not work with WPA and never
will.
Dan
> I don't know if this is a problem in iwconfig or in the driver...
>
> Any idea ? Any way to debug this ?
>
> pd: hardware is Acer Aspire One 150:
>
> 03:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
> Subsystem: Foxconn International, Inc. Device e008
> Flags: bus master, fast devsel, latency 0, IRQ 18
> Memory at 35200000 (64-bit, non-prefetchable) [size=64K]
> Capabilities: [40] Power Management version 2
> Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
> Capabilities: [60] Express Legacy Endpoint, MSI 00
> Capabilities: [90] MSI-X: Enable- Count=1 Masked-
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [140] Virtual Channel <?>
> Kernel driver in use: ath5k
> Kernel modules: ath5k
>
> TIA
>
> (plz, CC me, I'm not subscribed...)
>
prev parent reply other threads:[~2009-12-25 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 9:56 Problems with ath5k and WPA2 keys J.A. Magallón
2009-12-25 20:12 ` Dan Williams [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=1261771950.7657.2.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=jamagallon@ono.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox