From: Johannes Berg <johannes@sipsolutions.net>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Connection issues with BW Tracking in mac80211
Date: Tue, 24 Feb 2015 11:35:05 +0100 [thread overview]
Message-ID: <1424774105.2192.29.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzY+fhpwaS1Pr7_rirPbWy+TOEqSH3yA+gE5JADL_3gczkA@mail.gmail.com> (sfid-20150224_112828_368221_B3751798)
On Tue, 2015-02-24 at 15:58 +0530, Krishna Chaitanya wrote:
> 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 this goes through the supplicant, right? You actually get a full
connection loss (which I certainly would expect after 30 seconds)
> but due to BW tracking in
> mac80211 it doesn't connect.
>
> So i guess we are not resetting the tracking after losing connection.
Right, some flag is not getting reset correctly I suppose. I thought we
had pretty robust code for this, but I guess not.
Easiest might be to print the flags and other state for during all
connection attempts, and then compare
* VHT connection
* subsequent HT connection
* HT connection after reloading the driver
johannes
next prev parent reply other threads:[~2015-02-24 10:35 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
2015-02-24 10:35 ` Johannes Berg [this message]
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=1424774105.2192.29.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chaitanya.mgit@gmail.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).