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, 17 Mar 2015 10:57:16 +0100 [thread overview]
Message-ID: <1426586236.1985.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzYL1uvHG-MsXMiqrnyA8HuJ47AyuJG-fAM2Ok6GQjC_dtg@mail.gmail.com> (sfid-20150312_101811_932722_326ED06E)
On Thu, 2015-03-12 at 14:47 +0530, Krishna Chaitanya wrote:
> 1. Make the directed probe mandatory:
> a. Check for successful probe resp without depending on proberesp_ies.
> b. remove the proberesp_ies from the auth_data to trigger
> directed probe.
>
> 2. Timestamps for proberesp and beacons and update the latest one to "ies".
>
> 3. while update "ies" check only for beacon as its supposed to have latest
> information (This will trigger #1 automatically).
>
> As a quick and minimal impact solution i am thinking 1-b.
Huh? No, that'd be one of the worst possible solution IMHO since it
would make the system behave differently *all the time* just because of
a very uncommon scenario.
Is this really a "real world" use case? I can't really think of any way
this would happen in practice.
The least impact would probably have #2.
johannes
next prev parent reply other threads:[~2015-03-17 9:57 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 [this message]
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=1426586236.1985.1.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).