Return-path: Received: from mx1.redhat.com ([209.132.183.28]:56743 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933551Ab3CSSPl (ORCPT ); Tue, 19 Mar 2013 14:15:41 -0400 Message-ID: <1363716980.2225.32.camel@dcbw.foobar.com> (sfid-20130319_191550_452314_1336CE08) Subject: Re: Brcmsmac driver woes, possible regression? From: Dan Williams To: =?ISO-8859-1?Q?Camale=F3n?= Cc: Jonathan Nieder , Arend van Spriel , 664767@bugs.debian.org, linux-wireless@vger.kernel.org Date: Tue, 19 Mar 2013 13:16:20 -0500 In-Reply-To: <20130319181135.GA7969@stt008.linux.site> References: <20130318083752.GA6570@elie.Belkin> <51476D25.6030609@broadcom.com> <20130318211428.GA9136@stt008.linux.site> <20130318212544.GB5062@elie.Belkin> <1363711989.2225.8.camel@dcbw.foobar.com> <20130319173054.GA7873@stt008.linux.site> <1363715961.2225.22.camel@dcbw.foobar.com> <20130319181135.GA7969@stt008.linux.site> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, 2013-03-19 at 19:11 +0100, Camaleón wrote: > El 2013-03-19 a las 12:59 -0500, Dan Williams escribió: > > > On Tue, 2013-03-19 at 18:30 +0100, Camaleón wrote: > > > El 2013-03-19 a las 11:53 -0500, Dan Williams escribió: > > > > > > > > Note that NM 0.9.8 won't ask for a password when just anything fails, > > > > but will ask for a password if the 4-way handshake fails, because if > > > > that fails, it's probably your password. We're contemplating getting > > > > rid of that too, and just notifying the user that their password may be > > > > wrong and that they should go update it in the network configuration > > > > panel so we don't interrupt. But if you're 100% sure your PSK is > > > > correct, then it is, most likely, a driver bug. > > > > > > Password is correct. I have a second wireless card (external, using > > > rt2800usb driver) that connects without a glitch to the same AP. > > > > > > Moreover, unless I type the right password, N-M dialog does not allow > > > me to click on the "Connect" button. > > > > NM minimally verifies the PSK, which by 802.11 standards is between 8 > > and 63 ASCII characters inclusive. So you should be able to type > > anything you want within those constraints, but clearly only one is your > > real PSK. > > Oops! Okay, so what user inputs is not "bullet-proof". > > Anyway, this does not seem to be a problem of bad password. I was > finally able to get connected to the AP as soon as I carry the nebook > and put it next to the AP which is the problem I've always have had > with this driver (brcmsmac). Yeah, that's a symptom of bad power control or bad gain or who knows what in the driver. But also, make sure your antennas are connected correctly :) > As soon as I back to another room, N-M asks me again for the pass-key > and disconnects. NM 0.9.8 shouldn't do that; I bet you're not even getting to the point where the 4-way handshake and password verification are done. NM 0.9.8 will retry a few times, notify you and fail, then wait a couple minutes and try again. It shouldn't ask for a password anymore in situations like this. Dan