From owner-freebsd-hackers@FreeBSD.ORG Tue May 31 15:01:26 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98072106564A for ; Tue, 31 May 2011 15:01:26 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 711F08FC08 for ; Tue, 31 May 2011 15:01:26 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 2443746B35; Tue, 31 May 2011 11:01:26 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B3D018A027; Tue, 31 May 2011 11:01:25 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 31 May 2011 10:29:15 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DE01421.7080902@rawbw.com> In-Reply-To: <4DE01421.7080902@rawbw.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105311029.15259.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 31 May 2011 11:01:25 -0400 (EDT) Cc: Yuri Subject: Re: ndis driver presents the valid WiFi network as having the name 0x000000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 May 2011 15:01:26 -0000 On Friday, May 27, 2011 5:14:09 pm Yuri wrote: > Underlying card is Broadcom BCM94312MCGSG (mini-card for laptop) with > Windows driver. > This same card and driver work fine with pretty much any other network I > tried. > But this one particular network shows as 0x000000 and I can't connect to it. > Another FreeBSD desktop with native ath driver and apple both connect to > it fine. > > What might be causing such weird behavior? > Is this a known problem? > Any way to troubleshoot this? I have this same problem. I've had to resort to using wpa_cli to 'select' my network at work that has this issue and then using 'ap_scan 2' to force wpa_supplicant to associate with it. You also will want ndis_events running if you need to do WPA authentication. -- John Baldwin