From owner-freebsd-current@FreeBSD.ORG Sat May 29 02:59:57 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8950B1065676 for ; Sat, 29 May 2010 02:59:57 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 180CB8FC13 for ; Sat, 29 May 2010 02:59:56 +0000 (UTC) Received: (qmail 24118 invoked by uid 399); 29 May 2010 02:59:56 -0000 Received: from localhost (HELO ?192.168.0.145?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 29 May 2010 02:59:56 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C00832A.4030102@FreeBSD.org> Date: Fri, 28 May 2010 19:59:54 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: bf1783@gmail.com References: In-Reply-To: X-Enigmail-Version: 1.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, "b. f." Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 May 2010 02:59:57 -0000 On 5/28/2010 4:50 PM, b. f. wrote: > > I can't see any problems when using WPA2 with AES on r208606 i386 with > uath(4). I'm updating this machine to r208630 tonight, and if I > encounter problems with the later revision, I'll let you know. Ok, thanks. > Are > you saying that you experienced problems when trying to use a r207134 > base with a r208626 kernel? If that's the case, I would recommend > updating the base to the same revision as the kernel, and then > retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/