Re: Problem setup atheros wifi card using WPA TKIP

Quoting Sam Lefebvre <[email protected]>:

> See again between the lines.

Please try to configure your e-mail client to quote messages with ">".  
  It will make it easier for others to read and quote your messages.

> Trying to associate with 00:30:bd:9a:04:da (SSID='belkin54g' freq=2462 MHz)
> Associated with 00:30:bd:9a:04:da
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

Some other program is touching the device, presumably wpa_supplicant.

> The native interface for ath5k and most modern drivers is "nl80211", but
> "wext" should work just fine.
>
> This does not work at all:
>
> sam@Alix3d3:~$ sudo wpa_supplicant -Dnl80211 -iwlan0   
> -c/etc/wpa_supplicant.conf
> Unsupported driver 'nl80211'.

No problem, "wext" should be good enough.

> De volgende pakketten zijn achtergehouden:
>   linux-generic linux-headers-generic linux-image-generic

You can use "LANG=C" in front of the command to make it show messages  
in English.

Upgrading the kernel can be forced by
sudo ath-get install linux-generic

But it's getting too far offtopic.

> NetworkManager can be turned off with GUI.  Right-click on the network
> icon and uncheck "Enable Networking".
>
> Ok, I checked this and there is no bookmark against 'wireless connection'.
> I have to enable 'wired connection' otherwise I can't anymore login   
> through the fixed interface with putty.

Apparently, it's not enough to disable the resident wpa_supplicant.

> wpa_supplicant can be killed by killall:
> killall wpa_supplicant
>
> This is also not a solution:
>
> sam@Alix3d3:~$ sudo killall wpa_supplicant

Please try the command again to see if wpa_supplicant was killed.  If  
it was killed by the previous command, there will be an error message.  
  The most radical way would be to kill wpa_supplicant with SIGKILL:

sudo killall -KILL wpa_supplicant

> 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=2462 MHz)
> Authentication with 00:30:bd:9a:04:da timed out.
> Trying to associate with 00:30:bd:9a:04:da (SSID='belkin54g' freq=2462 MHz)
> Associated with 00:00:00:00:00:00

It looks like the resident wpa_supplicant is still running.

> What can i more try?

I don't want to give you any suggestions how to disable NetworkManager  
and the resident wpa_supplicant permanently, as it can cripple your  
system, especially since you are using the network to access the system.

Basically, either you rely on NetworkManager to handle the connections  
for you, or you run wpa_supplicant manually.  Doing both won't work.

There is nothing MadWifi specific in that problem, as you can see by  
trying ath5k.  You may want to discuss this problem in a more suitable  
place, e.g. in a mailing list about NetworkManager.  Ideally,  
NetworkManager should not try to manage interfaces already managed by  
a non-resident wpa_supplicant.  And of course the network should work  
for you without any need to resort to running wpa_supplicant manually.

-- 
Regards,
Pavel Roskin

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev