> On Mon, 2017-11-06 at 20:20 +0000, 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 steer the station even though the station is > > > > not sending or receiving > > > > > > any data or mgmt. frame. > > I guess you want something else. Why even consider a station that's sending > mgmt frames as non-idle? > > You can just use the data TX/RX counters to figure out if the station has been > idle. > Hmm.. But polling TX/RX counters will not give exact activity time. Moreover It will be useful if STA's last data activity tstamp is logged in station dump. No? > You've not convinced me that changing the current logic here makes any sense. > I thought adding new inactive time attribute may conflict with existing last_active info. As Igor mentioned earlier, what is your thought of adding new attribute "sta_last_data_active" to monitor data frame. Any suggestions are welcome. -Rajkumar
