From: Bruno Randolf <br1@einfach.org>
To: David Mosberger <davidm@egauge.net>,
Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: lost connectivity until "wpa_cli reassociate" is issued
Date: Thu, 7 Jan 2016 16:59:40 +0000 [thread overview]
Message-ID: <568E997C.1030003@einfach.org> (raw)
In-Reply-To: <CALnQHM1mzqFbprQqujB7BWncOa=D9uAxLQ0paiv-21vrx+hFvw@mail.gmail.com>
On 01/07/2016 04:29 PM, David Mosberger wrote:
> On Thu, Jan 7, 2016 at 9:24 AM, Ben Greear <greearb@candelatech.com> wrote:
>> On 01/07/2016 08:19 AM, David Mosberger wrote:
>>>
>>> We are seeing a curious issue where WLAN connectivity sometimes
>>> gets stuck until a "wpa_cli reassociate" command is issued.
>>>
>>> At the WPA level, everything appears to be working fine)
>>> (see thread starting at
>>> http://lists.infradead.org/pipermail/hostap/2016-January/034454.html).
>>
>> I don't remember seeing you mention the driver and NIC you are using.
>>
>> I think this is likely a driver bug, so please provide that info.
>
> Sure, we're using rtl8192cu. I started out suspecting a driver bug as
> well, but since we're processing management frames during those
> "stuck" periods just fine (see
Although I have not checked if the "wpa_cli reassociate" command helps,
I have seen rtl8192cu get "stuck" in similar ways. Maybe you can give
the new rtl8xxxu driver from Jes Sorensen try? It has less features, but
works more reliable, IMHO...
bruno
next prev parent reply other threads:[~2016-01-07 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 16:19 lost connectivity until "wpa_cli reassociate" is issued David Mosberger
2016-01-07 16:24 ` Ben Greear
2016-01-07 16:29 ` David Mosberger
2016-01-07 16:32 ` Krishna Chaitanya
2016-01-07 16:47 ` David Mosberger
2016-01-07 16:58 ` Krishna Chaitanya
2016-01-07 17:00 ` David Mosberger
2016-01-07 16:33 ` Ben Greear
2016-01-07 16:45 ` David Mosberger
2016-01-07 16:59 ` Bruno Randolf [this message]
2016-01-07 17:32 ` David Mosberger
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=568E997C.1030003@einfach.org \
--to=br1@einfach.org \
--cc=davidm@egauge.net \
--cc=greearb@candelatech.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 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.