On Wed, 2017-11-15 at 19:21 +, Rajkumar Manoharan wrote:
> >
> Hmm.. But polling TX/RX counters will not give exact activity time.
Yeah but if you do it every minute, you'll know if it was idle for
roughly 5 minutes, or so... dunno, things could be done.
> Moreover
> It will be useful if ST
> On Mon, 2017-11-06 at 20:20 +, Rajkumar Manoharan wrote:
> > > > For steering an idle station from one BSS to another, the steering
> > > > application has to know the actual station idle period. But if the
> > > > idle period is cleared by ap_max_inactivity, the steering
> > > > application
On Mon, 2017-11-06 at 20:20 +, Rajkumar Manoharan wrote:
> > > For steering an idle station from one BSS to another, the steering
> > > application has to know the actual station idle period. But if the
> > > idle period is cleared by ap_max_inactivity, the steering application
> > > cannot ste
> >>> 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).
> >>
> >> You mak
On 11/06/2017 09:44 AM, Rajkumar Manoharan wrote:
On Mon, 2017-10-30 at 17:29 -0700, 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 s
> On Mon, 2017-10-30 at 17:29 -0700, 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 in
On Mon, 2017-10-30 at 17:29 -0700, 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 thr
> 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.
Igor,
I validated hostpad inactivity monito
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_i
