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: Wed, 10 Jul 2013 18:48:28 +0100 [thread overview]
Message-ID: <51DD9E6C.5060008@inov.pt> (raw)
In-Reply-To: <1373476663.8385.28.camel@cumari.coelho.fi>
On 10-07-2013 18:17, Luciano Coelho wrote:
> On Wed, 2013-07-10 at 17:30 +0100, José Miguel Gonçalves wrote:
>> On 10-07-2013 13:34, José Miguel Gonçalves wrote:
>>> I will try a new AP to see how it behaves...
>>>
>> I've tested with my Android smartphone acting as an AP, without authentication,
>> and I'm also unable to associate!
>>
>> I get from iw the following error message:
>>
>> wlan0 (phy #0): failed to connect to b4:07:f9:49:cc:65, status: 1: Unspecified failure
>>
>> Complete log is here:
>>
>> http://pastebin.com/DzPmMw8i
>>
>> So, something is definitely wrong with my setup... but what?
>> Hope that log has some useful info for you...
> This definitely looks like RF problems. Especially this:
>
> [ 177.575000] wlan0: send auth to b4:07:f9:49:cc:65 (try 1/3)
> [ 177.595000] wlan0: send auth to b4:07:f9:49:cc:65 (try 2/3)
> [ 177.605000] wlcore: EVENT on mbox 1
> [ 177.605000] wlcore: MBOX vector: 0x100000
> [ 177.610000] wlcore: MAX_TX_FAILURE_EVENT_ID
> [ 177.615000] wlan0: send auth to b4:07:f9:49:cc:65 (try 3/3)
> [ 177.640000] wlan0: authentication with b4:07:f9:49:cc:65 timed out
>
> You are send auth requests out, but not getting anything back.
> Apparently you're not even getting ACKs (as pointed out by the
> MAX_TX_FAILURE_EVENT_ID).
Hum. I never considered RF problems because I'm testing this module with a
Jorjin's development kit, so I was considering that Jorjin knows how to make PCBs
for RF. Also seeing that when I remove the antenna the AP signal strength changes
from -51 dBm to -73 dBm was a signal to me that the RF was OK.
>
> Do you have a sniffer? You could try to use your TP-Link dongle with
> wireshark to see if it works fine as a sniffer.
I have a text console only system. I could put tcpdump on my system, but I think I
can not monitor wireless traffic with it, or can I?
José Gonçalves
next prev parent reply other threads:[~2013-07-10 17:48 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 [this message]
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
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=51DD9E6C.5060008@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 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).