All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: David Mosberger <davidm@egauge.net>, linux-wireless@vger.kernel.org
Subject: Re: lost connectivity until "wpa_cli reassociate" is issued
Date: Thu, 7 Jan 2016 08:24:29 -0800	[thread overview]
Message-ID: <568E913D.7050301@candelatech.com> (raw)
In-Reply-To: <CALnQHM3C=DVaTf58XDyh+rttVs-FSpc4ghozg9HJktEonq7w-g@mail.gmail.com>

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.

Thanks,
Ben

>
> What's truly odd is when connectivity is stuck, you can often "ping" the
> network's gateway exactly once and then you either get no response anymore
> or, after a long time (like 40-60 seconds), the floodgate opens and
> (almost) all previously sent ping responses arrive all at the same time
> (in the latter case, connectivity is fine afterwards again).
>
> This makes me wonder if there may be a packet queue that somehow gets
> stuck.
>
> I have turned on mac80211 debugging but have not found anything
> that seems to correlate with the loss of connectivity.  All I know is that
> wpa_cli reassociate so far is the least intrusive workaround that seems
> to reliably bring back connectivity.
>
> We are based on kernel 3.7.0 but have back-ported the mac80211 fixes
> from the linux-3.7.y stable branch.
>
> I'm not very familiar with the wireless stack, so any tips or hints on how to
> further debug this would be greatly appreciated.
>
> Thanks and best regards,
>
>    --david
>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2016-01-07 16:24 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 [this message]
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
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=568E913D.7050301@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=davidm@egauge.net \
    --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.