On Fri, 2009-04-10 at 23:47 +0300, Maxim Levitsky wrote: > And I found out why device is always busy, when wpa supplicant tries to > scan. It is the disassociation sequence. > > Does kernel notify, when disassociation have finished? > Maybe it is still better not to fail scan request, but block? Can you _please_ be more explicit? What _is_ with the association sequence? I already _know_ that setting a random ESSID will block scans, and no, I don't think blocking is a good idea, and no, there's nothing to do about it. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
