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: Wed, 11 Mar 2015 17:20:17 +0100	[thread overview]
Message-ID: <1426090817.1904.6.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzYKa5eR+UrinkqY99jxOpVR4mTYcW_3xZ5f2kf9hXHCznA@mail.gmail.com> (sfid-20150311_171529_797404_ECB8E5E9)

On Wed, 2015-03-11 at 21:45 +0530, Krishna Chaitanya wrote:

> I did some experiments on this and found the root cause.
> 
> We are using 5GHz in WORLD Mode, so only passive scan is allowed.
> So when connecting the very first time, the mac80211 MLME sees that
> there are no probe_resp ies (only beacon_ies are present) and it sends
> a directed probe and updates the probe_resp ies. (and also the "ies").
> 
> But when config is changed and we get disconnected, beacon_ies are updated
> with the new config, but the probe_resp ies are not.
> cfg80211_bss_update assigns
> probe_resp ies to "ies' and mac80211 updates its bss info based on the
> probe_resp
> ies which have old config causing the issue.
> 
> Solution:
> 
> 1) Make the directed probe mandatory.
> 2) As you suggested maintain timestamps for probe_resp_ies and beacon_ies
> and use the latest.
> 
> Any takes?

What's the operational problem here? I don't really see it. Are you
afraid users will reconfigure their APs often enough for this to be an
issue?

johannes


  reply	other threads:[~2015-03-11 16:20 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 [this message]
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=1426090817.1904.6.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).