Connection/disconnection problems with wpa_supplicant and hostapd when using WPA2 encryption
ad.decostre at gmail.com
Wed Jan 25 12:47:03 EST 2012
Thanks for your suggestion.
Increasing the amount of random numbers available in /dev/random has
helped a lot to solve this issue.
On Mon, Jan 23, 2012 at 8:34 PM, Adrien Decostre <ad.decostre at gmail.com> wrote:
> Dear Johannes,
> I have added in attachment the hostapd log.
> But the only thing I see is that the client (mac 00:23:a7:39:d0:69)
> "did not acknowledge authentication" and that this causes the
> What is the signification of the "reason_code=3" for the disassociation?
> Thanks in advance for your help.
> Best regards
> On Mon, Jan 23, 2012 at 8:19 PM, Adrien Decostre <ad.decostre at gmail.com> wrote:
>> Dear Jouni,
>> Thanks a lot for this quick answer.
>> The ath9k driver is used on the access point with hostapd.
>> In attachment, there is a full log file from wpa_supplicant where the
>> client disconnects before the completion of the authentication
>> procedure (due to limited size of the attachment, I have cut the part
>> of the log showing successful authentication).
>> Up to now, I have seen this problem with different PCs among other one
>> with a rt2800usb driver
>> Is there a way to reduce the authentication timeout (now currently set
>> to 10sec.) such that in case of "authentication failure", the
>> authentication procedure is restarted sooner?
>> Thanks in advance for your answer.
>> On Mon, Jan 23, 2012 at 7:23 PM, Johannes Berg
>> <johannes at sipsolutions.net> wrote:
>>> On 2012-01-23 04:39, Adrien Decostre wrote:
>>>> Apparently, the client is 1st correctly associated (message “State:
>>>> ASSOCIATING -> ASSOCIATED” visible in the wpa_supplicant log) but the
>>>> client is soon after disconnected due to authentication problem with
>>>> the following error message:
>>>> WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
>>>> Authentication with 00:0e:8e:3b:05:6d timed out.
>>>> BSSID 00:0e:8e:3b:05:6d blacklist count incremented to 2
>>>> No keys have been configured - skip key clearing
>>>> State: ASSOCIATED -> DISCONNECTED.
>>>> After this the client restarts the association/authentication
>>>> procedure and after a few tries the authentication succeed.
>>> Need logs from hostapd, but it could be that there are not enough
>>> random numbers.
>>> HostAP mailing list
>>> HostAP at lists.shmoo.com
More information about the HostAP