[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a32f33a40612131328i177600dfh7f6437f4b5ed1bb8@mail.gmail.com>
Date: Wed, 13 Dec 2006 22:28:15 +0100
From: "Ivo Van Doorn" <ivdoorn@...il.com>
To: "Lennart Sorensen" <lsorense@...lub.uwaterloo.ca>
Cc: "Dan Williams" <dcbw@...hat.com>, "Jiri Benc" <jbenc@...e.cz>,
"John W. Linville" <linville@...driver.com>, netdev@...r.kernel.org
Subject: Re: [PATCH 0/2] d80211, rt2x00: fixes
Hi,
> > 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..."
That is definately the rt2500 legacy driver and _not_ the rt2x00 driver.
> 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.
Correct, that is why those iwpriv commands are the clear evidence
you are not using rt2x00 but rt2500 legacy. Check which driver is loaded
rt2500 means legacy
rt2500pci means rt2x00.
Ivo
-
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