From owner-freebsd-current@FreeBSD.ORG  Fri May 28 23:50:05 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 BF3E2106566B;
	Fri, 28 May 2010 23:50:05 +0000 (UTC)
	(envelope-from bf1783@googlemail.com)
Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 312208FC16;
	Fri, 28 May 2010 23:50:04 +0000 (UTC)
Received: by wwb34 with SMTP id 34so550834wwb.13
	for <multiple recipients>; Fri, 28 May 2010 16:50:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=googlemail.com; s=gamma;
	h=domainkey-signature:mime-version:received:received:reply-to:date
	:message-id:subject:from:to:cc:content-type;
	bh=nPlzlDGV1P5W/NcFm37uBlNlnDX8OtU/cRZOWbdmRmI=;
	b=wrYoud6oFSsK1L1SzESYNSNf83UCWA2wRVWA80KKxvtXQKdMqWZ+4THyTY42YpyCs4
	oqQMBLK+rcksy2Bds0QgvWhv1Mb3aP4QfsspWNdzEVHlHJOp/uvhhqF6FPuI8QijZEX7
	FwFWCh64k2tQYi1DSB/s7u1yqI022pbhLbHaU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma;
	h=mime-version:reply-to:date:message-id:subject:from:to:cc
	:content-type;
	b=OnvDXz+YrH+6eFH6M2WODBNT704QW5guRJXymEDqGCgE2dm/MU4yf/Vj4+HvFCZBBi
	5b/5gz/L4XgzJXIw4TDH4v/bB0qkj3A00ttirhj1ueXjKwT+/gCLE2tcvrMFZTvZNx7O
	zBOBk+5u3W+xNjuXboAQaN2MR/EgjILrlOABM=
MIME-Version: 1.0
Received: by 10.216.185.209 with SMTP id u59mr2090042wem.112.1275090603353; 
	Fri, 28 May 2010 16:50:03 -0700 (PDT)
Received: by 10.216.158.146 with HTTP; Fri, 28 May 2010 16:50:03 -0700 (PDT)
Date: Fri, 28 May 2010 19:50:03 -0400
Message-ID: <AANLkTilCmEAdZXpO_hhQXOkY576POiNqf71fZ4nmu7hO@mail.gmail.com>
From: "b. f." <bf1783@googlemail.com>
To: freebsd-current@FreeBSD.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: dougb@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
Reply-To: bf1783@gmail.com
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 May 2010 23:50:05 -0000

>On 05/28/10 13:18, Doug Barton wrote:
>> I am trying to update -current in order to try kib's patch for the
>> nvidia driver, and the wpi driver won't establish a connection. I'm
>> using r207134 right now without any problems, but that's a long time
>> back to try and do a binary search.
>>
>> I don't see any changes to wpi or wpa_supplicant between then and now,
>> anyone have an idea of where to look? My WAP is using WPA2 with AES if
>> that's any help.
>
>Correction, the problem seems to be more generally with wpa_supplicant.
>I tried with the new kernel and my ath PCMCIA card (AR5416 mac 13.10
>RF2133 phy 8.1) and it doesn't work with the latest kernel either.
>However, the same card is working fine with the older kernel (I'm using
>it now).

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.  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.

b.