> > - Driver authenticating with new AP while having a valid > > association with and other AP. > > Yes, that is the problem, we should disassociate first. If > you can come up with a patch to send a disassoc packet in > that case (and test it, > preferably) that would be much welcome. OK. I understood that there has been a discussion about the way the driver should handle this situation and the current behaviour is according to that discussion. Is there any information document available describing the selected design path or is it only the code that document the design ? I think need that information if I should be able to create the patch requested above. On the other hand, that patch will only keep track of 'dual association' problem. With the current wpa_supplicant, we will still have the problem with the driver start an association sequence as soon as 'trig' ioctl arrives. I think the wpa_supplicant need to modified to better cooperate with the driver. The patch that I suggested is now installed in the system where I had the problem. The traces looks good and I have had no problems reported so far. /Lars -- 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
