Re: [PATCH] wifi: don't remove AP upon link lost event

On Fri, May 10, 2013 at 12:14 PM, Dan Williams <dcbw redhat com> wrote:
The supplicant has a BSS timeout too, and APs don't get removed from the
supplicant's list until the next scan after the timeout happens.  So it
could be long after you're out of range, and that means NM would keep
trying to reconnect to the AP that's not there because it doesn't know
it's gone.

There's no good way to know that an AP isn't in range anymore besides
probe-scanning for it after you lose the connection to it, which would
be a good thing to do.  But would also require some supplicant

OK, the approach in your patch makes sense. I've been running it all
day, the AP has kicked me off several times and each time NM recovers


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