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:11:35 +0100 [thread overview]
Message-ID: <20130319181135.GA7969@stt008.linux.site> (raw)
In-Reply-To: <1363715961.2225.22.camel@dcbw.foobar.com>
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).
As soon as I back to another room, N-M asks me again for the pass-key
and disconnects.
Greetings,
--
Camaleón
next prev parent reply other threads:[~2013-03-19 18:11 UTC|newest]
Thread overview: 17+ 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] ` <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 [this message]
2013-03-19 18:16 ` Dan Williams
2013-03-19 18:30 ` Camaleón
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=20130319181135.GA7969@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 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).