[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061213205425.GC26415@csclub.uwaterloo.ca>
Date: Wed, 13 Dec 2006 15:54:25 -0500
From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To: Dan Williams <dcbw@...hat.com>
Cc: Jiri Benc <jbenc@...e.cz>,
"John W. Linville" <linville@...driver.com>, netdev@...r.kernel.org
Subject: Re: [PATCH 0/2] d80211, rt2x00: fixes
On Wed, Dec 13, 2006 at 12:38:43PM -0500, Dan Williams wrote:
> How, by private ioctls? That's just wrong; I believe you still need to
> go through the 4-way handshake to get the right keying information even
> if you use PSK, which means you still need the supplicant, right?
All I did was add this to /etc/network/interfaces:
iface wlan0 inet static
address 192.168.1.51
network 192.168.1.0
netmask 255.255.255.0
gateway 192.168.1.254
broadcast 192.168.1.255
pre-up ifconfig wlan0 up
pre-up iwpriv wlan0 set AuthMode=WPAPSK
pre-up iwpriv wlan0 set EncrypType=TKIP
pre-up iwconfig wlan0 essid USR8054
pre-up iwpriv wlan0 set WPAPSK="My WPA passphrase..."
It seems to work, although I guess I could be wrong. It was what I
found in the documentation for the rt2x00 driver for doing WPA. It
looks nothing like the wpa_supplicant stuff I used to have with an older
version of the driver. My understanding was that the rt2x00 driver
and/or d80211 stack took care of it now.
--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists