All of lore.kernel.org
 help / color / mirror / Atom feed
From: Camaleón <noelamac@gmail.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	664767@bugs.debian.org, linux-wireless@vger.kernel.org
Subject: Re: Brcmsmac driver woes, possible regression?
Date: Sun, 24 Mar 2013 11:37:13 +0100	[thread overview]
Message-ID: <CAKprTDHmJGgjcirrRARVoFmovnn9pF0pRry3BMc=L=K8L6_15Q@mail.gmail.com> (raw)
In-Reply-To: <514ED101.9010006@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]

2013/3/24 Arend van Spriel <arend@broadcom.com>:
> On 03/23/2013 04:28 PM, Camaleón wrote:

(...)

>> More verbose logs, just in case someone finds something of interest.
>>
>
> What I see in this log is that your AP keeps sending EAPOL message 1 and
> you keep sending EAPOL message 2 until one gives up the attempts. This
> behaviour would suggest the psk is wrong as indicated in the log, but
> you said you could connect using another card, right? So using the same
> configured N-M connection?

Yes, a second card works perfect.

Even more... look at these news logs (attached and compressed because
this one is a bit big, ~1.5 MiB), wlan0 is binded to brcmsmac and
wlan2 is the external card (rt2800usb). Okay, as soon as I boot the
system wlan2 loads and runs fine. The I remove the this second card
(unplug the usb cord) and load the re-pacthed brcmsmac kernel module.
It cannot connect and asks me for the passkey. I carry the computer
next to the AP and voilà, I get magically associated to the AP and N-M
asks no more for the passkey. As soon as I return to my room, problems
start over... so, it does not look like a bad passkey problem, I'm
afraid :-)

Greetings,

-- 
Camaleón

[-- Attachment #2: 20130324_brcmsmac_supplicant_debug_on_off.txt.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 76008 bytes --]

      reply	other threads:[~2013-03-24 10:37 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
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 [this message]

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='CAKprTDHmJGgjcirrRARVoFmovnn9pF0pRry3BMc=L=K8L6_15Q@mail.gmail.com' \
    --to=noelamac@gmail.com \
    --cc=664767@bugs.debian.org \
    --cc=arend@broadcom.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.