All of lore.kernel.org
 help / color / mirror / Atom feed
From: Camaleón <noelamac@gmail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Arend van Spriel <arend@broadcom.com>,
	664767@bugs.debian.org, linux-wireless@vger.kernel.org
Subject: Re: Brcmsmac driver woes, possible regression?
Date: Tue, 19 Mar 2013 19:30:44 +0100	[thread overview]
Message-ID: <20130319183044.GA8058@stt008.linux.site> (raw)
In-Reply-To: <1363716980.2225.32.camel@dcbw.foobar.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 

  reply	other threads:[~2013-03-19 18:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130317144603.GA4850@stt008.linux.site>
     [not found] ` <1363532310.3937.266.camel@deadeye.wl.decadent.org.uk>
     [not found]   ` <20130317152428.GA4940@stt008.linux.site>
     [not found]     ` <1363544257.3937.278.camel@deadeye.wl.decadent.org.uk>
2013-03-17 21:43       ` Bug#703142: compatibility with alx ? Ben Hutchings
2013-03-20  9:07         ` Luis R. Rodriguez
2013-03-20 14:41           ` Ben Hutchings
2013-03-20 15:50             ` Luis R. Rodriguez
2013-03-20 17:45               ` Ben Hutchings
2013-03-26 15:07                 ` Camaleón
     [not found]     ` <20130317175658.GA8181@elie.Belkin>
     [not found]       ` <20130317182725.GA5811@stt008.linux.site>
     [not found]         ` <20130317183344.GA8786@elie.Belkin>
     [not found]           ` <CAKprTDFhNnGOPHUqg8Wn6Cd170KaeXj7-w-D6wS2Cc38vstt5A@mail.gmail.com>
2013-03-18  8:37             ` Brcmsmac driver woes, possible regression? Jonathan Nieder
2013-03-18 19:38               ` Arend van Spriel
2013-03-18 21:14                 ` Camaleón
2013-03-18 21:25                   ` Jonathan Nieder
2013-03-19  9:43                     ` Camaleón
2013-03-19 16:21                       ` Camaleón
2013-03-19 16:53                         ` Dan Williams
2013-03-19 17:30                           ` Camaleón
2013-03-19 17:59                             ` Dan Williams
2013-03-19 18:11                               ` Camaleón
2013-03-19 18:16                                 ` Dan Williams
2013-03-19 18:30                                   ` Camaleón [this message]
2013-03-19 21:55                         ` Arend van Spriel
2013-03-19 22:11                           ` Dan Williams
2013-03-23 15:28                         ` Camaleón
2013-03-24 10:10                           ` Arend van Spriel
2013-03-24 10:37                             ` Camaleón

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=20130319183044.GA8058@stt008.linux.site \
    --to=noelamac@gmail.com \
    --cc=664767@bugs.debian.org \
    --cc=arend@broadcom.com \
    --cc=dcbw@redhat.com \
    --cc=jrnieder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.