Often have to reload wl module to connect to WPA2/Enterprise network

[Joe Barnett]

I have a WPA2 Enterprise network at work using PEAP authentication with a CA cert that I have on disk and MSCHAPv2 inner authentication. I can connect to it fine via gnome's network-manager integration, but often (1-3 times per day) need to rmmod wl; modprobe wl; in order to successfully associate with the AP. The only related log message I see in syslog when this happens is:

 NetworkManager[9871]: <warn> Activation (wlan0/wireless): association took too long, failing activation.
 NetworkManager[9871]: <info> (wlan0): device state change: config -> failed (reason 'ssid-not-found') [50 120 53]

I do not have this issue with my WPA2 Personal AP at home.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: wl (not installed)
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.17-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Apr 14 11:03:10 2015
InstallationDate: Installed on 2014-02-24 (414 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: wl
UpgradeStatus: Upgraded to vivid on 2015-02-04 (68 days ago)

[Tatsuya Kinoshita (tats-debian)]

This issue is not relate to the wl package (mail reader in Emacs).