linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:08:48 +0100	[thread overview]
Message-ID: <1424772528.2192.13.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzYJD9KL1JngdKBwRqcGR2zFeo=hEfY0UVwAObd+E2ot5DQ@mail.gmail.com> (sfid-20150219_203032_581866_79C1F323)

On Fri, 2015-02-20 at 01:00 +0530, Krishna Chaitanya wrote:
> Hi Johannes,
> 
> The BW tracking feature in mac80211 is causing connection problems and
> operating mode/bw problems when switching b/w modes and bw's in AP.
> 
> For Eg. Initially if AP is operating in VHT-80MHz, and then we changed
> in to HT-40MHz, mac80211 cannot handle it because the VHT capability
> is mismatched b/w stored info (ifmgd->flags).

How are you doing such a change? I was assuming that the BSS would cease
to exist if it was reconfigured in such a way.

> I have tried your DISABLE_BW_TRACK patch, that helps making the
> connection but it doesn't update the chipset causing issues.

Well, that was clearly going to happen.

> Ideally we should be able to handle all the config changes right?

Not sure. How does this config change work? I'd have expected the AP to
stop beaconing and kick everyone out if you actually reconfigured it to
no longer have VHT since then it can't do VHT rates any more either
according to the new config?

What exactly are you doing, and how does the AP behave, and what do you
expect to happen?

johannes


      parent reply	other threads:[~2015-02-24 10:08 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
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 [this message]

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=1424772528.2192.13.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).