Search Linux Wireless

Re: Problem with IEEE80211_MONITORING_INTERVAL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2009-04-16 at 12:49 +0300, Kalle Valo wrote:

> >> But that doesn't make sense to me now. ieee80211_associated() is only
> >> run from the station work (ieee80211_sta_work) which doesn't do anything
> >> when we're scanning (and gets restarted on scan end). So even if last_rx
> >> or last_beacon isn't updated we should only run the evaluation of that
> >> after the scan finishes.
> >> 
> >> I'll try to reproduce this.
> >
> > Can't. Scanning here, with 4965, takes almost 7 seconds, but all I see
> > is, _after_ the scan, a probe:
> >
> > [ 1534.592164] wlan0: beacon loss from AP 00:1d:7e:4a:a1:ab - sending probe request
> >
> 
> How many APs can your 4965 see? You need to have at least 4 second
> silence period to see the disassication (2 seconds for beacon loss
> detection, other two seconds for waiting probe response).
> 
> Try artificially dropping received frames during scan or something like
> that.

But that doesn't make sense. We don't run ieee80211_associated() during
scanning, so how would the state machine ever proceed?

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux