RT61 and WPA2 + AES

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=5047


20-10-2008 04:30:07

I've been trawling the web for answers to all these questions and am getting conflicting information, so I thought I would go to the source!

I am using the latest daily tarball from your server (downloaded on the 16th of October).

I'm using Zenwalk 5.2 with the RT61 drivers and the built-in RT2x00 module, this is running on an old Pentium III with 128MB ram.

The PCI card (Edimax) is detected and I can see wlan0 when I run ifconfig.

iwlist also scans succesfully for my wireless network but I still cannot connect when I 'up' wlan0.

The only thing I can think of is that WPA2 + AES does not work with the RT61 drivers.

Oh, by the way, I have non-alphanumeric characters in my password. Does this make a difference?

Do I need to put the s prefix on the password if it is not in hex in my call to iwpriv?

Your help would be greatly appreciated. And, YES, I have read the README, TESTING and all other files that come with the source AND with the Edimax card and cannot find anything on WPA2 and AES.


20-10-2008 11:27:52

I've now tested the connection without any security and I'm finding still can't connect with either the DHCPCD command or with WICD in zenwalk.

The IP address DHCPCD is assigning also makes no sense

My router only assigns IPs from

Does anyone know why this might be happening?


20-10-2008 12:13:44

OK, I've replaced the drivers with the rt61pci drivers that came with the kernel.
I can connect with no encryption, but I'm still having trouble connecting with both
WPA + TKIP and WPA2 + AES.

My next step will be to try wpa_supplicant, even though the hardware is supposed to do this on its own...

If anyone can point me in the right direction, it would be much appreciated!


20-10-2008 12:17:29

My next step will be to try wpa_supplicant, even though the hardware is supposed to do this on its own...

No it isn't. Hardware doesn't do associations on its own. Some Intel hardware can do it because of their firmware, but even that is disabled in the drivers because tools like wpa_supplicant must handle associations.

Legacy driver does perform auto-associations in driver, but that is _very_ bad behavior of the driver.


22-10-2008 17:59:03

My next step will be to try wpa_supplicant, even though the hardware is supposed to do this on its own...[/quoteysqhdeb5]
wpa_supplicant only works with rt2x00 ([bysqhdeb5]rt61pci[/bysqhdeb5]), while the legacy driver ([bysqhdeb5]rt61[/bysqhdeb5]) embeds everything, and as far as I remember it is capable of both WPA+TKIP and WPA2+AES.


23-10-2008 14:58:31

Hi paul.sijpkes,

Actually the legacy rt61 driver does support wpa supplicant, but I believe you need to use version 0.60 or better of wpa supplicant with the "-Dralink" option.



26-10-2008 09:27:57

WPA2 + AES works ok with my card using CVS drivers of 23rd Oct

You have to manually configure using iwpriv and set the following parameters, if it works it should associate with your AP - I am using a static IP however...

I ended up putting these commands in /etc/rc.local to get them sorted on boot, as the ifcfg-ethX file didn't appear to work. Note the order of these commands is quite crucial for some reason and a scan first seems to help, see if it helps you?
# Set up wireless WPA2 on boot (rt61)
/sbin/iwlist eth1 scan

echo "Setting up WPA2PSK for wireless..."
/sbin/iwconfig eth1 essid youressidhere
/sbin/iwconfig eth1 key off

/sbin/iwpriv eth1 set AuthMode=WPA2PSK
/sbin/iwpriv eth1 set WPAPSK=yourpassphrasehere
/sbin/iwpriv eth1 set EncrypType=AES


27-10-2008 16:50:50

I'm using debian etch (c54ri) in rt61 driver 24-oct release
sometimes get a blinking light, using DHCP
and would like to join in the hope to solve the problem for both of us
But I can confirm I've similar problems om WPApks WPA2PKS TICK AES

for the good order I have some basic setting in my INTERFACES file setting everything up
but I get no final result

Additionaly I use following script to set up
unsuccessfull i'm afraid
ifup wlan0
iwconfig wlan0 mode managed
ifconfig wlan0 up
iwconfig wlan0 essid $myEssid
iwconfig wlan0 ap $AP
iwpriv wlan0 set AuthMode=WPAPSK
iwpriv wlan0 set WPAPSK=$myKey
iwpriv wlan0 set EncrypType=TKIP
dhclient wlan0

I'll addapt it to this threrads suggestions
I suspect this script overrides all previous settings any suggestions welcome


27-10-2008 17:16:46

using yesterdays driver i get no success result but
# Set up wireless WPA2 on boot (rt61)
echo "Setting up WPA2PSK for wireless..."
sudo ifup $dev
sudo iwconfig $dev mode managed
#sudo ifconfig $dev up
sudo iwconfig $dev essid $myEssid
sudo iwconfig $dev key off
#sudo iwconfig $dev0 ap $AP
sudo iwpriv $dev set AuthMode=WPA2PSK
sudo iwpriv $dev set WPAPSK=$myKey
sudo iwpriv $dev set EncrypType=AES
sudo dhclient $dev
sudo iwlist $dev scan

I hoped using DHCP to see a reaction from the network but nothing
iwconfig wlan0 ($dev)
tecra:~$ sudo iwconfig wlan0
wlan0 RT61 Wireless ESSID:"myessid" Nickname:"tecra-toshiba"
Mode:Managed Frequency:2.472 GHz Bit Rate=54 Mb/s
RTS thr:off Fragment thr:off
Encryption key:6379-6356-6F6E-6441-7263-6869-74
Link Quality=54/100 Signal level:-84 dBm Noise level:-111 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


but I do not get a connection nor DHCP

all help welcome

ps RutilT build but can not get it connected on a remote x11 display it asks for profile and dies...


27-10-2008 17:22:26

have you tried tempoarily setting up a static ip? - this removes the question over whether your dhcp client is working or even monitoring that interface.

if you run 'iwlist $dev scan' does your access point appear?


27-10-2008 18:37:04

i have indeed, without any result though
as I see less, i used DHCP
Do you sugest to pick a static IP
can do of coarse just a bit more code


29-10-2008 23:24:34

sorry did not read about the scan....
Yes scan sees all the ap arround here

I'm giving essid & key
pswkey="direct key text"

and set the encryption key = none as mentioned here before

the settings essid & key work on an xp machine standing just aside using the same card

realy asny idea's are the latest sources working
please give me a hint to get to last working sources
no fancy stuff required