wpa_supplicant needed for 802.1X but doesn't work
I have Slackware Linux 12.0 and a D-LINK USB WLAN stick that works correctl with the rt73 legacy driver.
My university's network uses 802.1X, so it appears I need wpa_supplicant to connect to it.
However, I could find no combination of rt73 and wpa_supplicant that works. I tried wpa_supplicant 0.5.9 with some custom patches for ralink, and 0.6.1 with its own ralink drivers. I tried both your legacy rt73 drivers and those from Ralink's homepage.
In all cases, I get errors like these (even through the interface is definitely up)
[quote2pqzna0i]l2_packet_receive - recvfrom Network is down
ioctl[SIOCSIWSCAN] Network is down
Failed to initiate AP scan.
I tried compiling your rt2x00, but it would't compile (my kernel is 18.104.22.168, mac80211 builtin)
[quote2pqzna0i]/home/mbueker/wlan/rt2x00-cvs-2007121112/rt2400pci.c3332 error linux/eeprom_93cx6.h No such file or directory
/home/mbueker/wlan/rt2x00-cvs-2007121112/rt2400pci.c160 warning 'struct eeprom_93cx6' declared inside parameter list
/home/mbueker/wlan/rt2x00-cvs-2007121112/rt2400pci.c160 warning its scope is only this definition or declaration, which is probably not what you want
/home/mbueker/wlan/rt2x00-cvs-2007121112/rt2400pci.c In function 'rt2400pci_eepromregister_read'
/home/mbueker/wlan/rt2x00-cvs-2007121112/rt2400pci.c162 error dereferencing pointer to incomplete type[/quote2pqzna0i]
Please help me to get wpa_supplicant working, with whichever driver; Or to find another way to use the 802.1X authentication.
Recent rt73 CVS tarball should work with wpa_supplicant. Apparently, you forgot to bring the interface up before running it.
rt2x00 currently requires a 2.6.24 kernel.
Recent rt73 CVS tarball should work with wpa_supplicant. Apparently, you forgot to bring the interface up before running it.[/quote8hfrzfqq]
As I said, the interface was up.
Also, interestingly, the error appears wether or not I'm actually near the WLAN I'm wanting to connect to.
rt2x00 currently requires a 2.6.24 kernel.[/quote8hfrzfqq]
Ah, that explains it.
Thanks for your reply,
Also, interestingly, the error appears wether or not I'm actually near the WLAN I'm wanting to connect to.[/quotesqjn01s4]
Is there something running in the background that could change the interface state (NetworkManager maybe)? It could also be that wpa_supplicant brings the interface down itself, I'm not very familiar with this tool though.