NetworkManager is unable to associate to wireless AP

I have an atheros card, for which the problem seemed to be related with kernel/module under Feisty, because it was as hard to associate via command line as via NM, and the most efficient way, but not very efficient either way to associate was to unload and reload the ath_pci module, but under gutsy it does not help doing this.

Bug is still there in gutsy.

It seems that it is soemhow linked with the freeze bug.

   I mean that when I first upgraded to Gutsy, then NWM did freeze my computer at session start, an update of the network-tools package solve the problem.

   Then it seemed that the association was faster than with Feisty.

But then after another update, the freeze bug is back (comes a little later, and maybe only on wep networks) and the association is quite impossible to achieve with NWM

This is quite an anoying bug, since it forces one to do some command line (not to mention the startup freeze that forces one to deactivate NWM before login to its gnome session) and thus encourages the thought that linux is not an user friendly OS.

Regards.

--
Z.

Still have that problem : I have a network with cells on channel 10 and 3, and NWM just switch between allmost all *other* channels and gives up after a while when deactivating it and typing

sudo ifconfig ath0 down
sudo iwconfig ath0 chanel 10
sudo iwconfig ath0 essid "My Essid"
sudo ifconfig ath0 up
sudo dhclient ath0

it just work as soon as I finish entering these commands.

I'm not really sure on how NWM is working, but I think it tries to locate what wireless network has the strongest signal and if it has the required information to connect on it (it means that if the network is wep or wpa protected it probably do not tries it untill it has the key recorded somewhere) and then uses iwconfig and ifconfig to configure the interface correctly. If so then I assume there is a problem in detecting the correct channel of the strongest network, or an inability to decie between to equivalent strength with same essid and different channels.

--
Z.

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Please attach to this bug the file /var/log/syslog
Also give the result of dpkg -l|grep network-manager

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.