From owner-freebsd-current@FreeBSD.ORG Sat May 29 10:20:27 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 2B1B41065679 for ; Sat, 29 May 2010 10:20:27 +0000 (UTC) (envelope-from rpaulo@freebsd.org) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id D95BF8FC20 for ; Sat, 29 May 2010 10:20:26 +0000 (UTC) Received: from e.earth.lavabit.com (e.earth.lavabit.com [192.168.111.14]) by karen.lavabit.com (Postfix) with ESMTP id AB02A157546; Sat, 29 May 2010 05:20:22 -0500 (CDT) Received: from 10.0.10.3 (54.81.54.77.rev.vodafone.pt [77.54.81.54]) by lavabit.com with ESMTP id VJK577EJTNG2; Sat, 29 May 2010 05:20:22 -0500 Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Rui Paulo In-Reply-To: Date: Sat, 29 May 2010 11:20:18 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> References: <4C00832A.4030102@FreeBSD.org> To: bf1783@gmail.com X-Mailer: Apple Mail (2.1078) Cc: Doug Barton , freebsd-current@freebsd.org 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 10:20:27 -0000 On 29 May 2010, at 05:39, b. f. wrote: > On 5/28/10, Doug Barton wrote: >> On 5/28/2010 4:50 PM, b. f. wrote: >>>=20 >>> 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. >>=20 >> Ok, thanks. >>=20 >>> 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. >>=20 >> 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. >>=20 >=20 > It appears that something is wrong. My wireless stick no longer > associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the = taskqueue stuff that zml committed, I think, but that's a long shot. Regards, -- Rui Paulo