@ldc: - I did observe multiple times now, that killing the wpa_supplicant + reconnecting to the wifi solved the no traffic issue. - I can reproduce it quite good in the company by changing the floor (and thus, getting a different access point with the same ssid)
- Does that workaround work for your "no traffic" situations, too? With having looked into the code, I bet the crypto WPA stuff is done with the wrong (old, before roaming) BSSID in the keys or challenge response or whatever. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1478592 Title: bcmwl-kernel-source fixes [Patch] Status in bcmwl package in Ubuntu: Confirmed Bug description: The broadcom-wl driver have a few issues that have not been corrected in the ubuntu package. Supplied with this bugreport is a monolithic patch that addresses some of those. Summary/testing of patch: - 2 days of local testing with associate/disassociate/scan between 2 access-points. (same model and running same openwrt version, so might not be a good test). - Suspend/resume seems to work (no extensive testing there yet). - Testing been done on a MBP 11,3 with a BCM4360 card running Ubuntu 15.04 with kernel 4.1.3 (vanilla) - Only 4.x changes are new, rest have been in use by several projects (ubuntu/gentoo/archlinux etc) for some time. Feel free to split it up into several patches.... This have been a locally maintained repo that have used several different sources and that's the reason for the monolithic patch. One issue that is left is the: if (WARN_ON(!bss)) return; in net/wireless/sme.c but this does not seem to cause issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1478592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
