OK, so ran another side-by-side comparison this morning on two machines, a macbook with running the BCM wl driver, and a macbook pro running ath9k. Both machines are Karmic RC + lastest updates.
I bumped the verbosity of wpa_supplicant logging ( added -d to the args in the .service file ), wiped the daemon.log on both. I then did the following on both: 1. Associated with my home AP ( WEP ) 2. Suspended both machines around 9:30 AM 3. Resumed both machines at around 10:15 AM at a local coffee shop As expected, the ath9k machine displayed a Disconnected notification dialog, whereas the wl machine started spinning the applet icon, and eventually popped up a key / password dialog for my home AP. I went through the logs side by side and they look almost identical, except for the fact that the 'wl' driver never seems to generate a disconnect wireless event on sleep. This is what I expected. As NM does have logic to deactivate and clear the currently associated AP on sleep, I think the 'w' driver behavior is exposing a bug in NM. I'll attach sanitized versions of both logs. -- [Broadcom wl]: After Resume, NM tries to connect to previous, non-available Wi-Fi network https://bugs.launchpad.net/bugs/452571 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
