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
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
