On Mon, 2008-09-08 at 12:06 +0300, Tomas Winkler wrote: > > That's what we're doing of course, but should we really drop all the > > frames that might still be in the queue? If we're just roaming we could > > send them out via the next AP, but it's hard to know, and since it's > > working let's not touch it for now. > > In current situation we are dropping the frames anyway. > How do you know you are roaming and not moving to another network? Yeah exactly, it's not easy to know. > > How exactly are you triggering that "unauthorized port" message? I can't > > seem to reproduce to see if stopping the queue helps, but I'm fairly > > sure, try the patch below that fixes this. > > Powering off AP, I think I've seen only Cisco AP that are able to send > deauth packet on power off. So this was without. Odd. So you did get the "No ProbeResp from current AP - assume out of range" message? In that case I would have expected you to get the same message, but of course it's both timing and frame sensitive. I'm a bit surprised you saw the message at all. Maybe I can reproduce by doing a ping flood to the AP. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
