From: Chris Murphy <lists@colorremedies.com>
To: linux-wireless@vger.kernel.org
Subject: BCM4331 won't connect with WPA2
Date: Tue, 21 Nov 2017 15:36:02 -0700 [thread overview]
Message-ID: <CAJCQCtQUE6V6zQewVAQJRmDPHjqL=Mixq4nj0kZGZ67UKOTnKg@mail.gmail.com> (raw)
Hi,
Pretty much all the details and logs are here:
refuses to connect to WPA2 secured WiFi
https://bugzilla.redhat.com/show_bug.cgi?id=1516009
So I will just include a summary here:
Macbook Pro, Broadcom BCM4331
firmware version 784.2 (2012-08-15....
kernels 4.5.5 through 4.13.13
NetworkManager-1.8.4
wpa_supplicant-2.6
Access point is an Xfinity branded
Arris TG1682G, 802.11a/b/g/n/ac
Connecting to this AP's unsecured "xfinity" SSID succeeds, but fails
to its "altitude" WPA2 secured SSID. The user visible failure is
either no error other than three dots for the Wifi icon in the gnome
menu bar, or more often the modal passphrase dialog for the AP comes
up asking for the passphrase again.
No other devices (about 1/2 dozen) have this problem, including this
same laptop if I reboot to macOS and connect to this same "altitude"
SSID with the same entered passphrase.
There is an attached log (journal3) where a connection did succeed for
a very short amount of time, but then promptly was disconnected with
all subsequent attempts to connect failing while the user intervention
was zero (I was touching nothing, just monitoring and logging stuff).
The journal2 log attached to the bug report contains wpa_supplicant -d
output. Let me know if I need to retry with -dd and post that
somewhere. Also in the bug are the kernel config options, I don't see
any of the requested 80211 options in the reporting bugs guidelines.
https://wireless.wiki.kernel.org/en/users/documentation/reporting_bugs
So if I need to compile a kernel and enable options, no problem, just
let me know which ones.
If I change any of the three components: client (the laptop with
BCM4331) + linux + AP then the problem doesn't happen. Change the OS
and it works. All other devices work with this AP and WPA2. And
BCM4331 + linux work with other APs than this one. So it's something
of a trifecta bug.
--
Chris Murphy
reply other threads:[~2017-11-21 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJCQCtQUE6V6zQewVAQJRmDPHjqL=Mixq4nj0kZGZ67UKOTnKg@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).