From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 8 08:41:10 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D8B9F09; Wed, 8 Jan 2014 08:41:10 +0000 (UTC) Received: from lyra.its.uu.se (lyra.its.uu.se [130.238.7.73]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EE9F31F83; Wed, 8 Jan 2014 08:41:09 +0000 (UTC) X-Virus-Scanned: amavisd-new at uu.se Received: from nyx.uppmax.uu.se (nyx.uppmax.uu.se [130.238.137.40]) by lyra.its.uu.se (Postfix) with ESMTP id 8448338F7D; Wed, 8 Jan 2014 09:31:31 +0100 (CET) Message-ID: <52CD0CEE.5010700@pean.org> Date: Wed, 08 Jan 2014 09:31:42 +0100 From: =?windows-1252?Q?Peter_Ankerst=E5l?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130807 Thunderbird/17.0.8 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: wpa_supplicant problem. References: <79AEC286-90EB-41D0-8CA8-18A78D53C3C6@pean.org> <8CFBC6B5-B683-4EC3-9561-EFFA6CE55755@pean.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "stable@freebsd.org" , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jan 2014 08:41:10 -0000 Hehe, I dont think Im ready for 11 yet. Do you think these fixes will be in 10 any time soon? On 01/08/2014 07:30 AM, Adrian Chadd wrote: > Hm, sounds to me like something I fixed in -HEAD. Try -HEAD. > > The TL;DR - the EAPOL frames are going out at a much higher transmit > rate than the initial association attempts, which means it associates > fine but it can't authenticate successfully. > > Try running -HEAD. I bet it'll work. > >