wpa_supplicant: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Mon Nov 22 11:02:44 PST 2010
Creating a wireless trace with wireshark might also be a good idea. When
the AP sends a dissassociate, is will also give a reason. Might be that
Just my 2 cents,
> Is the driver sending a disassociation event? You'll want '-dddt'
> debugging from the supplicant to figure that out. Or you can run
> 'iwevent' if you have WEXT support built in.
More information about the Hostap