All of lore.kernel.org
 help / color / mirror / Atom feed
From: kang haiyang <hykang@dongniannetworks.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Can't associate with a particular AP
Date: Sun, 23 Oct 2011 23:05:28 +0800	[thread overview]
Message-ID: <4EA42D38.6050202@dongniannetworks.com> (raw)
In-Reply-To: <20111023142536.GA4633@kirya.net>

from the failed wireshark log, i saw there is inconsistent information 
in reassociation response:
in capability tag: ap tells client that it supports 40Mhz, but in the HT 
info tags it tells client that it only support 20Mhz.

i don't know if this maybe bother some particular clients.

Best Regards,
kang haiyang


On 10/23/2011 10:25 PM, Julien Valroff wrote:
> Hi,
>
> Le dimanche 16 oct. 2011 ? 17:31:44 (+0200 CEST), Adrian Chadd a ?crit :
>> Can you please grab a third device and grab a dump of the actual
>> probe/association frames?
>>
>> I think it'd be helpful to see what's changed.
> I have tried and captured the association process from my 2 other laptops
> using wireshark, but unfortunately, I am unable to capture packets in
> monitoring mode: in Wireshark, the box is not greyed out, but I cannot tick
> it.
>
> I've tried reading the Wireshark documentation on this point, but I could
> not see anything about this problem.
>
> I have followed Peter's instructions and the ones described in [0] both
> with the same results.
>
> But still, I have been able to capture something from the problematic
> laptop, you will find the wireshark logs attached.
>
> When failing to associate, I can see a lot of lines as follows:
> 50	11.081661	ba:f4:8a:c6:c8:44 (TA)	74:2f:68:57:2c:dc (RA)	802.11	46	Request-to-send, Flags=........C
>
> followed by:
> 166	23.082827	ba:f4:8a:c6:c8:44	74:2f:68:57:2c:dc	802.11	56	Deauthentication, SN=1142, FN=0, Flags=........C
>
> where:
> ba:f4:8a:c6:c8:44 is my AP
> 74:2f:68:57:2c:dc is my Atheros wlan NIC
>
> When the association succeeds, I notice the MAC address of the AP changes:
> 99	5.752088	c6:6e:27:a6:be:a4	74:2f:68:57:2c:dc	802.11	272	Probe Response, SN=269, FN=0, Flags=........C, BI=100, SSID=Kirya
>                        ^^^^
>
> Which is confirmed by iwlist scan.
> Before the association:
> Cell 01 - Address: BA:F4:8A:C6:C8:44
>          Channel:3
>          Frequency:2.422 GHz (Channel 3)
>          Quality=26/70  Signal level=-84 dBm
>          Encryption key:on
>          ESSID:"Kirya"
>
> After the succeeded association:
> Cell 04 - Address: C6:6E:27:A6:BE:A4
>          Channel:3
>          Frequency:2.422 GHz (Channel 3)
>          Quality=70/70  Signal level=-35 dBm
>          Encryption key:on
>          ESSID:"Kirya"
>
> How is this possible?
>
> Please continue and CC me as I am not subscribed to the list.
>
> Cheers,
> Julien
>
> [0] http://wiki.wireshark.org/CaptureSetup/WLAN#Linux
>
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111023/942575eb/attachment.htm 

  parent reply	other threads:[~2011-10-23 15:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 16:36 [ath9k-devel] Can't associate with a particular AP Julien Valroff
2011-10-04  5:46 ` Mohammed Shafi
2011-10-04 18:35   ` Julien Valroff
2011-10-05  4:24     ` Julien Valroff
2011-10-15  4:51       ` Julien Valroff
2011-10-16 13:22         ` Mohammed Shafi
2011-10-16 15:01           ` Julien Valroff
2011-10-16 15:31             ` Adrian Chadd
2011-10-16 15:37               ` Mohammed Shafi
2011-10-16 15:40               ` Julien Valroff
2011-10-16 17:16                 ` Peter Stuge
2011-10-23 14:25               ` Julien Valroff
2011-10-23 15:02                 ` Peter Stuge
2011-10-23 15:54                   ` Adrian Chadd
2011-10-23 16:25                     ` Julien Valroff
2011-10-23 16:34                   ` Julien Valroff
2011-10-23 16:52                     ` Peter Stuge
2011-10-23 17:15                       ` Julien Valroff
2011-10-23 18:16                         ` Peter Stuge
2011-10-23 19:45                           ` Adrian Chadd
2011-10-23 15:05                 ` kang haiyang [this message]
2011-10-24  6:27                 ` Alex Hacker
2011-10-24 18:59                   ` Julien Valroff
2011-10-24 19:55                     ` Jouni Malinen
2011-10-27 18:36                       ` Julien Valroff
2011-10-27 19:13                         ` Julien Valroff
2011-10-27 20:27                           ` Jouni Malinen
2011-10-28  4:26                             ` Julien Valroff
2011-10-28  8:35                               ` Jouni Malinen
2011-10-28 19:30                                 ` Julien Valroff
2011-10-28 20:25                                   ` Peter Stuge
2011-10-27 20:31                         ` Peter Stuge
2011-10-29  6:41                     ` Julien Valroff
2011-10-29  6:50                       ` Adrian Chadd
2011-10-29 16:27                         ` Peter Stuge
2011-10-29 16:34                           ` Julien Valroff
2011-10-29 17:09                             ` Peter Stuge
2011-10-29 17:15                           ` Adrian Chadd
2011-10-29 17:23                             ` Peter Stuge

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=4EA42D38.6050202@dongniannetworks.com \
    --to=hykang@dongniannetworks.com \
    --cc=ath9k-devel@lists.ath9k.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.