[edgy] APs disappear from NM with madwifi-ng.

[Pedro Côrte-Real]

I have a atheros card (white macbook using madwifi-ng drivers) and just upgraded to edgy. I am using it's kernel and have made no changes to drivers/network-manager.

Edgy seems more solid with this new madwifi driver but I've noticed a weird problem. After a while it stops showing some of the available wireless networks. I have two access points and the one that uses WPA seems to appear after boot and then disappear. Doing a "iwlist ath0 scan" shows it so it seems like a network-applet problem. If I try to connect to it using "Connect to Other Wireless Network" it still doesn't work.

[Pedro Côrte-Real (pedrocr)]

Here's the log of the association attempt. The unencrypted AP that works fine is "CASA" the WPA one that doesn't work and that I tried to force is "NCASA".

[Pedro Côrte-Real (pedrocr)]

This is still happening in the final release of edgy.

[Pedro Côrte-Real (pedrocr)]

I think what's happening is that network manager isn't updating it's AP list at all.

[Jesse Buchanan (buchanan-jesse-deactivatedaccount)]

On a Thinkpad T60 with up-to-date Feisty, Atheros AR5418 and latest SVN for madwifi-ng as of yesterday (r2431 - need SVN as this card isn't supported in Feisty's version of madwifi-hal), I am having this problem. It consistently happens at my university where there are two competing wireless networks, "network A" and "network B". I only have access to "network B". Only "network A" shows in the nm-applet.

Earlier today I noticed that using "iwlist scan" produces all of the APs - both the ones I want to connect to, and the ones I'm not authorized to. However, using "wlanconfig ath0 scan" only shows the AP I don't want. The only difference I could see at the time, and mind you this was only once and may be coincidence -- is that the "network A" points were all on Channel 1, and the "network B" points were on Channel 7.

If I go into manual configuration, and disable roaming mode, in the "Network Settings" screen I can see all APs. Obviously the Network Settings screen and NetworkManager are using different method of scanning.

I will investigate a little more into NetworkManager/madwifi-ng, but I cannot replicate the problem until next week as it's fine on my home wireless.

[Henrik Nilsen Omma (henrik)]

Hi, could you please test this in Gutsy (perhaps with a Live CD)? We'll only be able to address most network-manager bugs in the latest release. Thanks.

[Henrique Ferreiro (henrique-ferreiro)]

This may be related to http://madwifi.org/ticket/1017

[Pedro Villavicencio (pedro)]

Closing this report for now, feel free to re open it if you can reproduce it with Gutsy Gibbon, thanks in advance.