From owner-freebsd-current@FreeBSD.ORG  Thu Nov  5 14:25:01 2009
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 44D8510656AC
	for <freebsd-current@freebsd.org>; Thu,  5 Nov 2009 14:25:01 +0000 (UTC)
	(envelope-from onemda@gmail.com)
Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com
	[209.85.219.218])
	by mx1.freebsd.org (Postfix) with ESMTP id 9B9EB8FC18
	for <freebsd-current@freebsd.org>; Thu,  5 Nov 2009 14:25:00 +0000 (UTC)
Received: by ewy18 with SMTP id 18so20995ewy.43
	for <freebsd-current@freebsd.org>; Thu, 05 Nov 2009 06:24:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type;
	bh=fM5JUitwisftWnGsHTZbvGdWGJFnrRUIQbIHO69GElY=;
	b=rwbrLkXmdbRxTdWTWYL61xAmEU8e6ljSDUwe0oBWwwV0RLcgOuQMZx16BZPUuaWVvW
	x94jsd6bvHpfCA7HBAoY/XwbkT2izWI/B5t9+63O8Imr6yotgl5QMyHU6UgC0OVjK7IM
	lyLEj5AcMb805OLo1nXa5HgavfysDr+jwM6AY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=SQvDlvhj9dJPPDGWbpjDP8NOriUkelRCLbmSHNXGhjy41XxGZdLzLUcOymn7y+bUU0
	n84/yROQVhArnuq3tRbeVL9yXo04jKvUwzGdZAxYnVfdR+8SDASjnD4jrMdAORT3I+nV
	8i2HScCPENwLUd6JeLfYIxeOezJwTv7ZF78wI=
MIME-Version: 1.0
Received: by 10.213.0.132 with SMTP id 4mr1243375ebb.8.1257431099184; Thu, 05 
	Nov 2009 06:24:59 -0800 (PST)
In-Reply-To: <1257426023.1436.18.camel@RabbitsDen>
References: <1257426023.1436.18.camel@RabbitsDen>
Date: Thu, 5 Nov 2009 15:24:59 +0100
Message-ID: <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com>
From: Paul B Mahol <onemda@gmail.com>
To: "Alexandre \"Sunny\" Kovalenko" <gaijin.k@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-current@freebsd.org
Subject: Re: After sys/net80211 changes in r198931 laptop is no longer 
	associating with AP
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
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: Thu, 05 Nov 2009 14:25:01 -0000

On 11/5/09, Alexandre "Sunny" Kovalenko <gaijin.k@gmail.com> wrote:
> It seems that 8.0 discussion is still going on on @current... if I
> should have posted this on @stable, please, feel free to chastise me as
> appropriate.
>
> After updating to r198831 my laptop no longer associates with either of
> two APs I have. Rolling back just 'sys/net80211' to r198443 fixes the
> problem.
>
> Working system:
> FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC1 FreeBSD 8.0-RC1 #0
> r198443M: Sat Oct 24 14:03:30 EDT 2009
> root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60  i386
>
> Non-working system:
> FreeBSD RabbitsDen.RabbitsLawn.verizon.net 8.0-RC2 FreeBSD 8.0-RC2 #0
> r198931: Wed Nov  4 20:56:16 EST 2009
> root@RabbitsDen.RabbitsLawn.verizon.net:/usr/obj/usr/src/sys/TPX60  i386
>
> APs are is:
> SSID/MESH ID    BSSID              CHAN RATE   S:N     INT CAPS
> AP_SSID         00:1f:33:3b:xx:xx    3   54M -68:-96  100 EP   RSN WPS
> WME
> AP_SSID         00:1f:90:cb:xx:xx    8   54M -73:-96  100 EPS  RSN WPA
> ATH
>
> Relevant piece of wpa_supplicant.conf is:
>
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=wheel
> eapol_version=2
>
> network={
>   ssid="AP_SSID"
>   scan_ssid=1
>   priority=1
>   proto=WPA
>   key_mgmt=WPA-PSK
>   psk="Really secure something"
> }
>
> APs are set not to broadcast SSID, but enabling broadcast does not
> change much.
>
> Running wpa_supplicant with -d shows that it could not match AP_SSID.
>
> If there is anything else I can provide, please, let me know.

What driver are you using?
Looking into net80211 svn log for that time period I only see mesh hacks ...