Grr, it's slightly more complicated than that.

That whole timer mess is actually used for two things:

* if the management transmit succeeds - it acts as a short-interval (a few
seconds) timer to ensure that the probe request ends up providing some
response that transitions to auth; otherwise it aborts and transitions back
to the SCAN state;
* if the management transmit fails - it immediately transitions back to

So, the "correct" fix involves correctly locking things and turning that
timer into a "if I fail to transition into a run state, then just go back
to scanning" timeout.

It sucks and it's going to take an evening of deep thought to figure out
the correct solution to.

Thanks for reminding me about this mess!

_______________________________________________ mailing list
To unsubscribe, send any mail to ""

Reply via email to