hostapd "deauthenticated due to local deauth request"

[Paul B Mahol]

On 10/31/09, Paul B Mahol <onemda at gmail.com> wrote:
> On 10/31/09, Ivan Voras <ivoras at gmail.com> wrote:
>> I'm trying to setup an AP with a run0 interface on latest 8-STABLE but
>> apparently 802.11 association fails:
>>
>> Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
>> 802.11: associated
>> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
>> 802.11: deauthenticated due to local deauth request
>> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
>> 802.11: deassociated
>> Oct 31 16:21:35 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
>> 802.11: associated
>> Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
>> 802.11: deauthenticated due to local deauth request
>> Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
>> 802.11: deassociated
>>
>> etc. Apparently the client never comes to the phase to receive DHCP
>> address.
>>
>> The client in this case is WinXP and the setup did work with 7-STABLE,
>> though with a bug in the rum driver which caused regular kernel panics
>> on the AP.
>>
>
> I tried same one with rum(4) as AP and ndis(4) as client on same
> machine(some version of 8.0 - CURRENT). ndis client (configured via
> wpa_supplicant)
> would keep auth and deauth all the time.
> I came to conclusion that rum is broken. But I think I remmember that
> bwi(4) (as a client)
> did not have such problem ... (I will test again to see)

Well, I tried again and I got similar output like yours if I use wrong
password. And with correct password client reauth all the time, maybe
I need to setup ndis_events(8) ....