From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 17:19:57 2009 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 AFCA7106568B for ; Sat, 7 Nov 2009 17:19:57 +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 44CFE8FC15 for ; Sat, 7 Nov 2009 17:19:56 +0000 (UTC) Received: by ewy18 with SMTP id 18so1694838ewy.43 for ; Sat, 07 Nov 2009 09:19:56 -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=n22BxNWbU2ylWS3wsVqEgOOaTjTWZ/PB+KP7CKSwAzk=; b=YmXY+p9XtEfrCBxPF+6+FY6MCrTTaSansdSCf91J8giUkfNMqPVtMzW6NvMhXLM17W V/rEjqYifaxOXCewfnQcXum/5Sgh9stm9P5WFHrhVZ5zGfZFO1x2LqakJ8acwRlwBzVU bvni7oSLLavY3wZKbF7nTYr6l/cbwiH4OvAIg= 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=xGGUK5nPcRm7H0Oah11dwDByOSFndfXEQzFnUXbym218D68XyIE2Z2qVH+WPFfAGos DseRXKbK0k5O6y7/d4acSQcYIoSRSPXjkKiO+iW+8UMdw1u0Jkftadgl3Z50hoL3jnYE WU7I63h/ySsCf32X2aTGQ30xo0P4Gn1ZSlGRA= MIME-Version: 1.0 Received: by 10.213.23.80 with SMTP id q16mr992440ebb.3.1257614396256; Sat, 07 Nov 2009 09:19:56 -0800 (PST) In-Reply-To: References: <1257426023.1436.18.camel@RabbitsDen> <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> Date: Sat, 7 Nov 2009 18:19:56 +0100 Message-ID: <3a142e750911070919s592980e1yfa420ea1d2654d52@mail.gmail.com> From: Paul B Mahol To: "Alexandre \"Sunny\" Kovalenko" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Nov 2009 17:19:57 -0000 On 11/5/09, Alexandre "Sunny" Kovalenko wrote: > On Thu, Nov 5, 2009 at 9:24 AM, Paul B Mahol wrote: > >> On 11/5/09, Alexandre "Sunny" Kovalenko 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 >> ... >> > I am using ath (I am away from my laptop ATM -- I could provide part number > later today). > > I have seen mesh changes in there and that's when I gave up and posted -- I > am not > nearly enough qualified to figure out which ones could or could not impact > normal operation. You could track which commit introduced bug and/or use wlandebug and/or athdebug to see what is going on.