From owner-freebsd-current@FreeBSD.ORG Sun May 30 17:48:41 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 1A6421065673; Sun, 30 May 2010 17:48:41 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.0x20.net [217.69.67.217]) by mx1.freebsd.org (Postfix) with ESMTP id 99EE28FC14; Sun, 30 May 2010 17:48:40 +0000 (UTC) Received: by mail.0x20.net (Postfix, from userid 1002) id 01DFA3A581; Sun, 30 May 2010 19:48:38 +0200 (CEST) Date: Sun, 30 May 2010 19:48:38 +0200 From: Lars Engels To: Rui Paulo Message-ID: <20100530174838.GC41305@e.0x20.net> Mail-Followup-To: Lars Engels , Rui Paulo , bf1783@gmail.com, Doug Barton , freebsd-current@freebsd.org References: <4C00832A.4030102@FreeBSD.org> <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="P6d3k5Edf9pZm0D3" Content-Disposition: inline In-Reply-To: <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> X-Editor: VIM - Vi IMproved 7.2 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: Mutt/1.5.20 (2009-06-14) Cc: bf1783@gmail.com, 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: Sun, 30 May 2010 17:48:41 -0000 --P6d3k5Edf9pZm0D3 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 29, 2010 at 11:20:18AM +0100, Rui Paulo wrote: >=20 > On 29 May 2010, at 05:39, b. f. wrote: >=20 > > 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 fu= ll > >> 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. >=20 > 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. Correction: Wireless actually works if you set the channel manually and start wpa_supplicant afterwards. So wpa_supplicant no longer seems to be able to change the channel itself. --P6d3k5Edf9pZm0D3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkwCpPYACgkQKc512sD3afixDQCgxiqb5N4dD1NU7uHfn1y3XsqL gSEAn0asHbB1i6OynWdK12AfGOeCi84E =I9sV -----END PGP SIGNATURE----- --P6d3k5Edf9pZm0D3--