All of lore.kernel.org
 help / color / mirror / Atom feed
From: "José Miguel Gonçalves" <jose.goncalves@inov.pt>
To: Luciano Coelho <coelho@ti.com>
Cc: Arik Nemtsov <arik@wizery.com>, linux-wireless@vger.kernel.org
Subject: Re: wl127x: Unable to associate with a WPA2-PSK AP
Date: Thu, 11 Jul 2013 14:33:42 +0100	[thread overview]
Message-ID: <51DEB436.9000300@inov.pt> (raw)
In-Reply-To: <1373549359.8385.36.camel@cumari.coelho.fi>

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

On 11-07-2013 14:29, Luciano Coelho wrote:
> On Thu, 2013-07-11 at 13:08 +0100, José Miguel Gonçalves wrote:
>>
>> I've setup my Linuc PC as a sniffer and yes I see a lot of of authentication
>> frames on the air when I try to associate with my open AP (Android phone).
>>
>> I've repeated the process with a TP-Link dongle and I see a clean 802.11
>> association sequence.
>>
>> What I found strange is that I don't see "probe request" frames on the wl12xx
>> captured frames, it starts directly with an "authentication" frame, when with the
>> TP-Link dongle (ath9k_htc driver) the first frame sent by is a "probe request"!
> Usually the connection will start with a probe request, but if there is
> a response in the cache, we may skip it.  In any case, this is probably
> happening because your sniffer is missing those frames (which again
> points to problems with RF).
>
>
>> I can provide the Wirehsark capture files. What is the best way to send them
>> through the mailing list?
> Cut only the portion that matters, so the file is small and gzip it.
> Small files can be sent as attachments to the list.
>

Here they go...

José Gonçalves

[-- Attachment #2: ath9k_htc.pcap.gz --]
[-- Type: application/x-gzip, Size: 417 bytes --]

[-- Attachment #3: wl12xx.pcap.gz --]
[-- Type: application/x-gzip, Size: 2298 bytes --]

  reply	other threads:[~2013-07-11 13:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 18:54 wl127x: Unable to associate with a WPA2-PSK AP José Miguel Gonçalves
2013-07-08 19:08 ` Arik Nemtsov
2013-07-08 22:47   ` José Miguel Gonçalves
2013-07-09  7:21     ` Arik Nemtsov
2013-07-09  9:09       ` Luciano Coelho
2013-07-09  9:33         ` José Miguel Gonçalves
2013-07-09  9:40           ` Luciano Coelho
2013-07-09 11:27             ` José Miguel Gonçalves
2013-07-09 12:42               ` Arik Nemtsov
2013-07-09 13:22                 ` José Miguel Gonçalves
2013-07-09 19:10                   ` Arik Nemtsov
2013-07-09 23:59                     ` José Miguel Gonçalves
2013-07-10  9:22                       ` Luciano Coelho
2013-07-10 12:34                         ` José Miguel Gonçalves
2013-07-10 16:30                           ` José Miguel Gonçalves
2013-07-10 17:17                             ` Luciano Coelho
2013-07-10 17:48                               ` José Miguel Gonçalves
2013-07-10 18:16                                 ` Larry Finger
2013-07-10 20:29                                   ` Luciano Coelho
2013-07-10 20:27                                 ` Luciano Coelho
2013-07-11 12:08                                   ` José Miguel Gonçalves
2013-07-11 13:29                                     ` Luciano Coelho
2013-07-11 13:33                                       ` José Miguel Gonçalves [this message]
2013-07-11 13:59                                         ` Luciano Coelho
2013-07-11 17:34                                           ` José Miguel Gonçalves
2013-07-11 18:26                         ` José Miguel Gonçalves
2013-07-10  8:48                   ` Luciano Coelho
2013-07-10 14:12                     ` José Miguel Gonçalves

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=51DEB436.9000300@inov.pt \
    --to=jose.goncalves@inov.pt \
    --cc=arik@wizery.com \
    --cc=coelho@ti.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.