linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
To: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>,
	johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, rmanohar@codeaurora.org
Subject: Re: [PATCH] mac80211: Update last_ack status for all except probing frames
Date: Tue, 31 Oct 2017 19:31:33 -0700	[thread overview]
Message-ID: <46362ff1-acfb-701c-5f71-7d117d223e1a@quantenna.com> (raw)
In-Reply-To: <1509409746-26592-1-git-send-email-rmanohar@qti.qualcomm.com>

On 10/30/2017 05:29 PM, Rajkumar Manoharan wrote:
> 
> Update last_ack status for all except station probing frames
> (i.e null data). Otherwise the station inactivity duration is
> cleared whenever AP is checking presence of idle stations by sending
> null data frame for every inactive threshold (ap_max_inactivity).
> Though the station is idle for longer period, the inactive
> time in station dump is restricted ap_max_inactivity threshold.
> 
> Signed-off-by: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
> ---

To clarify: wouldn't it break hostapd's "inactivity timeot kick-out" 
logic in hostapd? As hostapd generates NULL frames to idle stations to 
reset their inactivity time, otherwise it will disassociate a station, 
after an ap_max_inactivity period.

  reply	other threads:[~2017-11-01  2:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31  0:29 [PATCH] mac80211: Update last_ack status for all except probing frames Rajkumar Manoharan
2017-11-01  2:31 ` Igor Mitsyanko [this message]
2017-11-02 18:06   ` Rajkumar Manoharan
2017-11-06 10:29 ` Johannes Berg
2017-11-06 17:44   ` Rajkumar Manoharan
2017-11-06 19:50     ` Igor Mitsyanko
2017-11-06 20:20       ` Rajkumar Manoharan
2017-11-13  9:25         ` Johannes Berg
2017-11-15 19:21           ` Rajkumar Manoharan
2017-11-20 16:09             ` 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=46362ff1-acfb-701c-5f71-7d117d223e1a@quantenna.com \
    --to=igor.mitsyanko.os@quantenna.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rmanohar@codeaurora.org \
    --cc=rmanohar@qti.qualcomm.com \
    /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).