All of lore.kernel.org
 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, 25 Feb 2015 09:02:48 +0100	[thread overview]
Message-ID: <1424851368.2050.8.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzY+Z97Q4JSSaR2GfGnxbbR721qJ-v_AjG4Kc1TGetHF4ng@mail.gmail.com> (sfid-20150224_221135_386626_6E22A752)

On Wed, 2015-02-25 at 02:41 +0530, Krishna Chaitanya wrote:
> On Wed, Feb 25, 2015 at 2:17 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Wed, 2015-02-25 at 02:03 +0530, Krishna Chaitanya wrote:
> >
> >> Use case2: When changing from HT40-VHT80, the connection goes through
> >> but it still connected as HT40 (vht_ie from cfg80211 is returned
> >> null).
> >>
> >> Can you think of any reason why the bss_list is not updated cfg80211?
> >> Note: iwconfig and wpa_supplicant both show same behavior.
> >
> > Well, there's no flushing, only overwriting by new results - but if you
> > previuosly got both beacons and probe responses each one will stick
> > around until you get them again.
> We do have the scan results expiry time of 30secs, that will flush the
> results from bss_list right? Even the get_bss checks for aging?

Yes but if you scan in the meantime the scan result is marked as recent
again, even if some old data might be kept. Perhaps we should split that
into timestamps for probe and beacons separately, but that'd certainly
complicate the code significantly for little gain.

johannes


  reply	other threads:[~2015-02-25  8:02 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 [this message]
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=1424851368.2050.8.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 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.