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 18:34:38 +0100 [thread overview]
Message-ID: <51DEECAE.8080100@inov.pt> (raw)
In-Reply-To: <1373551187.8385.44.camel@cumari.coelho.fi>
On 11-07-2013 14:59, Luciano Coelho wrote:
> It seems that the wl1273 is not receiving the frames correctly. What
> happens in the first 3 frames is all normal, but we keep retransmitting
> the auth frame as if the AP hadn't sent us an ACK.
>
> 1. wl1273 sends auth to the AP
> 2. the AP acks the frame
> 3. the AP sends an auth back to us
> 4. we should send an ACK and continue, but instead we retransmit
> And from then on everything is screwed up.
>
> You could try to use the calibrator's RX statistics commands to see if
> you're getting lots of bad frames and such.
>
> This could be a problem in the firmware, but my hunch is that it's RF.
> What kind of antenna are you using?
A standard omni-directional antenna with a 4dBi gain. After I've read your email I
tried to change the antenna and immediately I got associated with the AP! But it
was only from a brief period. After that I've made some more tests and I was not
able to associate again. So it really seems that I've some kind of RF problem with
my module :-( BTW, my module has dual-band and I've tested in both 2.4 GHz and 5
GHz bands (with appropriate antennas), both without success.
>
> BTW, you should set a proper MAC address in your NVS too (calibrator's
> set_mac command). You could first try to set it to 00:00:00:00:00:00,
> which will check if the chip has a MAC in the Fuse ROM and use it from
> there. If that doesn't work, create your own and set it in the NVS.
I've already verified that the module doen not have a MAC built in. So I leaved
the "DE:AD:BE:EF:00:00" MAC set, which is as good as another one (for tests), and
a good reminder that I must add an EEPROM with a MAC address built in to my design.
>
> The TP-Link log is "too clean", missing some frames, we don't see most
> of the ACKs and we don't see the auth frame being sent back from the AP.
>
>
I've captured both files with display filter "wlan.addr == <MAC>". For instance,
for the log with the wl1273 based module, I used "wlan.addr == DE:AD:BE:EF:00:00".
It seemed to me the appropriate filter to extract all the traffic related with
that station, don't you agree?
José Gonçalves
next prev parent reply other threads:[~2013-07-11 17: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
2013-07-11 13:59 ` Luciano Coelho
2013-07-11 17:34 ` José Miguel Gonçalves [this message]
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=51DEECAE.8080100@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).