Re: [Madwifi-users] Problem setup atheros wifi card using WPA TKIP
Status: Beta
Brought to you by:
otaku
From: Pavel R. <pr...@gn...> - 2010-02-23 17:45:24
|
On Tue, 2010-02-23 at 12:33 +0100, Sam Lefebvre wrote: > rmmod ath_pci > modprobe ath5k > > Ok, i tried this and i get: > > sam@Alix3d3:~$ sudo rmmod ath_pci > sam@Alix3d3:~$ sudo modprobe ath5k > sam@Alix3d3:~$ sudo wpa_supplicant -Dwext -iath4 -c/etc/wpa_supplicant.conf > ioctl[SIOCGIFFLAGS]: No such device The network device is probably called wlan0, not ath4. Use iwconfig to see which devices you have. > sam@Alix3d3:~$ sudo wpa_supplicant -Dath5k -iath4 -c/etc/wpa_supplicant.conf > Unsupported driver 'ath5k'. The native interface for ath5k and most modern drivers is "nl80211", but "wext" should work just fine. > > sam@Alix3d3:~$ uname -a > > > > Linux Alix3d3 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC > > 2009 i586 GNU/Linux > > I think it's not the latest Ubuntu kernel, so you may want to upgrade, > even if it's not related to wireless drivers. > > I completely re-installed the embedded Alix3d3 pc in december 2009. > That means that this kernel is one of the latest kernels. > What is the easiest way to update the kernel? (Linux is relatively new for me) sudo apt-get update sudo apt-get upgrade > > sam@Alix3d3:~$ sudo wpa_supplicant -Dwext -iath4 > > -c/etc/wpa_supplicant.conf > > > > Trying to associate with 00:30:bd:9a:04:da (SSID='belkin54g' freq=2462MHz) > > > > Associated with 00:00:00:00:00:00 > > That's the first indication of trouble. I suggest that you turn off > NetworkManager and kill any instances of wpa_supplicant that me be already > running. I believe that's the most likely reason why wpa_supplicant is > failing for you. > > Indeed, I have also seen that the message 'Associated with > 00:00:00:00:00:00' regulary returns. Somethimes the assiciation with > 00:30:bd:9a:04:da was succeeded and I get the error that 4-way > handshaking was failed. But the system tries this in an endless loop. > Please tell me the steps that i can follow in order to turn off > NetworkManager and kill any instances of wpa_supplicant that may be > already running. NetworkManager can be turned off with GUI. Right-click on the network icon and uncheck "Enable Networking". wpa_supplicant can be killed by killall: killall wpa_supplicant > > I get always the message 'WPA: 4-Way Handshake failed - pre-shared key > > may be incorrect', and I’m sure that my password is correct typed in > > the config file. > > I think if wpa_supplicant gets the BSSID wrong, the encryption will fail. > > What is the difference between BSSID and SSID? The SSID of my acces > point is certainly sent-out, because I activate it in the Belkin > config and I can see it on other (windows) pc's. See also the scan > lower in this mail. BSSID is usually the MAC address of the AP. SSID (also knows as ESSID) is a name on the network. Many APs can have the same ESSID, but exch has a unique BSSID. > One thing that also may be the cause of the current problems is the > version of madwifi driver. On the site http://madwifi-project.org/ I > can read "In case you use kernel 2.6.25 or newer, you need to get this > snapshot of the madwifi-0.9.4 branch instead of the v0.9.4 release! > That snapshot is basically v0.9.4 plus compilation fixes for recent > kernels." Because my kernel is newer than 2.6.25 (2.6.31) and and I > used "madwifi-0.9.4-r4110-20100119.tar.gz" instead of this link which > points to "madwifi-0.9.4-current.tar.gz", this can be an issue. Do you > think it is recommended to re-install the driver before I try other > things? What is the best way to do that smoothly? I'm not aware of any recently fixed problems with WPA, so I think it should be unrelated. > Another guy said me that I have to check if my Belkin uses WPA1 or > WPA2. When I check this, I can see that it is definitly WPA1. I have > no idea how I can verify it in the config file. It should not matter. Everything should just work. -- Regards, Pavel Roskin |