flaky association with wireless access points

Bug #64931 reported by Zack Weinberg
6
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

network-manager does not reliably associate my laptop's wireless card with an access point. About half of the time, it gets stuck in the two-gray-balls state; somewhat less often, it gets stuck in the one-green-one-gray-ball state (these both describe the icon in the notification area). It seems to have more trouble when there are a lot of APs in range, especially when those APs all have the same SSID (I use the laptop all the time on the UCSD campus, which has a blanket wireless network).

I'm filing this bug against network-manager instead of the kernel because it happens with both the Dapper and Edgy kernels as long as the Edgy network-manager is in use. This problem did not occur with the Dapper network-manager, or at least it happened sufficiently less often that I didn't notice it.

I will attach the network-manager logfile.

Revision history for this message
Zack Weinberg (ubuntu-bugs-zackw) wrote :

whups, this got filed against acpi by mistake.

Revision history for this message
Zack Weinberg (ubuntu-bugs-zackw) wrote :

Here's /var/log/daemon.log from the problem system, which is basically all network-manager logs. There is definitely a failure to associate with SSID 'njs2' somewhere in here, and I believe there are some failures to associate with 'UCSD' too.

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

Can you also attach the results from an "lshal" and "lspci -v"?

Revision history for this message
Zack Weinberg (ubuntu-bugs-zackw) wrote :

Here you go.

Revision history for this message
Zack Weinberg (ubuntu-bugs-zackw) wrote :

I guess I have to make two comments to add two attachments...

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

It appears to be trying to migrate to the "better" network connection. This is a good candidate for forwarding upstream.

Will you be able to test any custom patches or versions that end up resulting from trying to fix this bug?

Revision history for this message
Zack Weinberg (zackw) wrote : Re: [Bug 64931] Re: flaky association with wireless access points

Yes, I can do that, no problem.

Revision history for this message
Scott (shatheruk) wrote :

I'm trying out fiesty beta on my laptop with PCMCIA wireless (using NDISwrapper and a solid XP driver) and the wireless seems alot more flaky than Edgy used to.

I use several wireless access points and whenever I go from one to the other, I have to unplug my PCMCIA card, plug it in again, go to the network settings window and switch "roaming mode" on, click OK, go back in and switch it on Off, wait about half a minute, then it connects and get's an IP address and I'm on. I've tried various other ways, but this seems to work each time now, just a bit long-winded.

Anyway, just thought I'd let you know. Not sure if its the same problem described above. I've had no other issues with fiesty, just this niggly little glitch. - Any log files I can send you, just let me know.

Revision history for this message
Zack Weinberg (zackw) wrote :

I should probably mention in this bug too that I have gone back to
Debian on this laptop - the last straw, in fact, was that the wireless
card didn't work AT ALL in feisty (the madwifi in feisty was
incompatible with the 2.6.20 kernel). I miss working suspend-to-disk,
but I need reliable wireless a lot more than I need suspend (and
suspend wasn't ever reliable, anyway).

Revision history for this message
John Vivirito (gnomefreak) wrote :

Thank you for your bug report.
Can you please test if your bug is still present in gutsy by using the latest gutsy livecd.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
John Vivirito (gnomefreak) wrote :

to grab the latest Gutsy Desktop cd please visit
http://cdimage.ubuntu.com/daily/current/

Revision history for this message
Alexander Sack (asac) wrote :

network-manager has come a long way since you posted your bug. Its most likely fixed. If its not fixed in latest gutsy network-manager for you, feel free to reopen it.

Changed in network-manager:
status: Incomplete → Fix Released
Revision history for this message
Zack Weinberg (zackw) wrote :

It ceased to be a problem for me when I gave up on Ubuntu (again) and
went back to Debian. This was about a year ago now.

zw

On 10/4/07, Alexander Sack <email address hidden> wrote:
> network-manager has come a long way since you posted your bug. Its most
> likely fixed. If its not fixed in latest gutsy network-manager for you,
> feel free to reopen it.
>
> ** Changed in: network-manager (Ubuntu)
> Status: Incomplete => Fix Released
>
> --
> flaky association with wireless access points
> https://bugs.launchpad.net/bugs/64931
> You received this bug notification because you are a direct subscriber
> of the bug.
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.