Bug#664767: Brcmsmac driver woes, possible regression?

[Camaleón <noelamac@gmail.com>]

El 2013-03-19 a las 13:16 -0500, Dan Williams escribió:

> On Tue, 2013-03-19 at 19:11 +0100, Camaleón wrote:

(...)

> > > 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 :)

I'm starting to think the embedded wireless adapter could have been 
damaged somehow. The fact is that the card worked fine until kernel 2.6.38 
(IIRC), but afterwards... well, I had to connect an additional USB card.

> > 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.

Debian Wheezy still has 0.9.4 but well, that's a minor issue ;-(

Greetings,

-- 
Camaleón