All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krishna Chaitanya <chaitanya.mgit@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Connection issues with BW Tracking in mac80211
Date: Tue, 24 Feb 2015 15:58:07 +0530	[thread overview]
Message-ID: <CABPxzY+fhpwaS1Pr7_rirPbWy+TOEqSH3yA+gE5JADL_3gczkA@mail.gmail.com> (raw)
In-Reply-To: <1424772587.2192.14.camel@sipsolutions.net>

On Tue, Feb 24, 2015 at 3:39 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Fri, 2015-02-20 at 02:58 +0530, Krishna Chaitanya wrote:
>
>> Before that i have a basic question? Should we reset our tracking after
>> the connection is lost, in my case above the connection was lost (Config
>> change in A triggers a reboot), still mac80211 is tracking the BW changes?
>
> Huh??
>
> So the AP does restart, but mac80211 tries to stay connected to it? That
> seems pretty unlikely. The tracking *shouldn't* have any knowledge of
> what happened before the association, but there could be bugs in the
> flags assignment I guess.
Let me explain the sequences.

STA (mac80211) connects to AP in VHT-80.
AP is reconfigured to 11n40 (stops beaconing for about 30secs and then
starts again).
STA loses connection (HW_CONN_TRACK), iee80211_connection_loss is called.
STA see's AP again and tries to connect, but due to BW tracking in
mac80211 it doesn't connect.

So i guess we are not resetting the tracking after losing connection.

  reply	other threads:[~2015-02-24 10:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 19:30 Connection issues with BW Tracking in mac80211 Krishna Chaitanya
2015-02-19 21:28 ` Krishna Chaitanya
2015-02-23 18:00   ` Krishna Chaitanya
2015-02-24 10:09   ` Johannes Berg
2015-02-24 10:28     ` Krishna Chaitanya [this message]
2015-02-24 10:35       ` Johannes Berg
2015-02-24 11:29         ` Krishna Chaitanya
2015-02-24 20:33           ` Krishna Chaitanya
2015-02-24 20:47             ` Johannes Berg
2015-02-24 21:11               ` Krishna Chaitanya
2015-02-25  8:02                 ` Johannes Berg
2015-03-11 16:15                   ` Krishna Chaitanya
2015-03-11 16:20                     ` Johannes Berg
2015-03-11 16:35                       ` Krishna Chaitanya
2015-03-12  9:17                         ` Krishna Chaitanya
2015-03-17  9:57                           ` Johannes Berg
2015-02-24 10:08 ` Johannes Berg

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=CABPxzY+fhpwaS1Pr7_rirPbWy+TOEqSH3yA+gE5JADL_3gczkA@mail.gmail.com \
    --to=chaitanya.mgit@gmail.com \
    --cc=johannes@sipsolutions.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.