On Fri, 2009-07-10 at 14:17 +0300, Kalle Valo wrote: > Johannes Berg <johannes@xxxxxxxxxxxxxxxx> writes: > > > With the recent MLME rework I accidentally removed the connection > > monitoring code. In order to add it back, this patch will add new > > code to monitor both for beacon loss and for the connection actually > > working, with possibly separate triggers. > > > > When no unicast frames have been received from the AP for (currently) > > two seconds, we will send the AP a probe request. > > I think this is too short, but we can change it later. That's why I kept it separate (well, also to change the beacon stuff to be dependent on the beacon interval later) > I quickly looked at the patch and it looks ok for me. Unfortunately I > can't test it right now because N800 support is broken in 2.6.31. I'm > fixing that currently. One thing is actually broken -- I start the monitoring even when hardware is doing beacon filtering/monitoring. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
