"Luis R. Rodriguez" <lrodriguez@xxxxxxxxxxx> writes: > We need to do this since the beacon monitor does not > push back the connection monitor by design so even if we > are getting beacons from these type of APs our connection > monitor currently relies heavily on the way the probe > requests are received on the AP. An example of an AP > affected by this is the Nexus One, but this has also been > observed with random APs. > > We can probably optimize this later by using null funcs > instead of probe requests. Beginning of this year I sent patches to use null funcs. Unfortunately I had to drop them due to time constraints. Also a major power consumption imporovement from using null func frames is that we don't have to trigger dynamic power save timer during the poll. Just send the frame with PSM bit set, wait for ack and go immeaditely back to sleep. So instead of having radios enabled for example 100 ms per frame, we can do it in just 1 ms. -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
