From owner-freebsd-current@FreeBSD.ORG Sat Nov 7 02:34:13 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 DE83B106566C for ; Sat, 7 Nov 2009 02:34:12 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail3.es.net [IPv6:2001:400:4c01::2]) by mx1.freebsd.org (Postfix) with ESMTP id AF7C68FC0C for ; Sat, 7 Nov 2009 02:34:12 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id nA72YAPL003866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 6 Nov 2009 18:34:11 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 940601CC0E; Fri, 6 Nov 2009 18:34:10 -0800 (PST) To: Paul B Mahol In-reply-to: Your message of "Thu, 05 Nov 2009 15:24:59 +0100." <3a142e750911050624q41a22ed5ud4f6919a2fac686e@mail.gmail.com> Date: Fri, 06 Nov 2009 18:34:10 -0800 From: "Kevin Oberman" Message-Id: <20091107023410.940601CC0E@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-11-06_11:2009-10-29, 2009-11-06, 2009-11-06 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-0911060303 Cc: freebsd-current@freebsd.org, "Alexandre \"Sunny\" Kovalenko" 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 02:34:13 -0000 > Date: Thu, 5 Nov 2009 15:24:59 +0100 > From: Paul B Mahol > Sender: owner-freebsd-current@freebsd.org > > 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 seeing exactly the same issue. Atheros 5212 with a non-broadcast SSID. Similar wpa_supplicant.conf including 'scan_ssid=1'. 'ifconfig wlan0' shows no ssid. Every time I boot my laptop at home, I need to enter 'ifconfig wlan0 ssid MySSID'. As soon as I do this, it immediately associates correctly. This was never a problem when I was running V7.0. Again, it only is an issue when I am associating with my non-broadcast SSID at home. When at work or traveling where the SSID is broadcast, wpa_supplicant works just fine. If I ever get more time, I'll try to run wpa_supplicant with gdb and see what is happenning, but I may not get a chance any time soon. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751