linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: No connection with TP-Link TL-WN823N (rtl8192cu)
Date: Wed, 25 Sep 2013 11:46:21 -0500	[thread overview]
Message-ID: <5243135D.30700@lwfinger.net> (raw)
In-Reply-To: <1380113275.7555.18.camel@dcbw.foobar.com>

On 09/25/2013 07:47 AM, Dan Williams wrote:
> On Tue, 2013-09-24 at 17:43 -0500, Larry Finger wrote:
>> On 09/09/2013 05:15 PM, Dan Williams wrote:
>>> On Mon, 2013-09-09 at 16:52 -0500, Larry Finger wrote:
>>
>>>> I have been running rtl8192cu for the past 24 hours without a permanent
>>>> disconnect. Under NetworkManager, I see some reason 7 deauthentications, but
>>>
>>> Running wpa_supplicant with debugging on might shed some light on these;
>>> basically:
>>>
>>> mv /usr/sbin/wpa_supplicant /
>>> killall -TERM wpa_supplicant
>>> /wpa_supplicant -dddtu <piped to your favorite log file>
>>>
>>> and NM should automatically reconnect, and then we can figure out what's
>>> going on in the supplicant.
>>
>> Dan,
>>
>> The log of wpa_supplicant associated with the reason 7 disconnects are as follows:
>
> So reason 7 is "Incorrect frame type or subtype received from
> unassociated station" which seems like the AP thinks we got
> disconnected, and would seem to be a driver/mac80211 issue still, right?

Yes. These only happen with rtl8192ce and rtl8192cu. They are a bit more common 
when running NetworkManager than with ifup. In my current run, they have been at 
intervals of 1000 to 30,000 seconds apart. Capturing them with wireshark may not 
be practical.

--snip--

> And got reconnected after a bit more than one second.  So at least it
> recovers quickly, but the question is more about why the reason 7
> happened, and what frames caused it, I think.

I agree. The sequence seems to start with an MLME Event 39:

.908249: nl80211: MLME event 39
.908252: nl80211: MLME event frame - hexdump(len=26): c0 00 3a 01 1c 65 9d 5a c3 
9d 20 e5 2a 01 f7 ea 20 e5 2a 01 f7 ea a0 f6 07 00
.908269: wlan3: Event DEAUTH (12) received
.908273: wlan3: Deauthentication notification

All that happens within 25 usec, but I have no clue what triggers that. In 
addition, I have been unable to find any documentation on MLME events. Any 
suggestions regarding a source would be appreciated.

Thanks,

Larry


  reply	other threads:[~2013-09-25 16:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 20:40 No connection with TP-Link TL-WN823N (rtl8192cu) Vincent Thiele
2013-09-09 21:52 ` Larry Finger
2013-09-09 22:15   ` Dan Williams
     [not found]     ` <CAEZsi7FY8HdBcb0p1svijAdFjB0MbrYv_Zft0B_+RQTpGWCnhQ@mail.gmail.com>
2013-09-11 16:14       ` Dan Williams
2013-09-11 16:33         ` Larry Finger
2013-09-11 16:53           ` Vincent Thiele
2013-09-11 17:05             ` Larry Finger
2013-09-11 17:11           ` Mark Cave-Ayland
2013-09-11 18:24             ` Larry Finger
     [not found]               ` <CAEZsi7G+FqUh2fBXLLR17qiBb1ggLu2+11aYRt2Wppr1gGK-Wg@mail.gmail.com>
2013-09-12  1:53                 ` Larry Finger
     [not found]                   ` <CAEZsi7F-RxaZJNaYi53kTtsQbxL4TU6DhTPo5v-O5ry=pawb_Q@mail.gmail.com>
2013-09-12  6:24                     ` Larry Finger
2013-09-12  7:41                       ` Vincent Thiele
2013-09-21 17:47                         ` Vincent Thiele
     [not found]                           ` <CAEZsi7HnRxojt6=B3fy8uT2KHuVwzhzzvWV7Ykvr+fO_55Upkw@mail.gmail.com>
2014-02-13 22:05                             ` Fwd: " Vincent Thiele
2014-02-13 22:47                               ` Larry Finger
2014-02-14 12:20                                 ` Vincent Thiele
2013-09-24 22:43     ` Larry Finger
2013-09-25 12:47       ` Dan Williams
2013-09-25 16:46         ` Larry Finger [this message]
2013-09-25 19:06           ` Dan Williams

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=5243135D.30700@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=dcbw@redhat.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).