From owner-freebsd-hackers@FreeBSD.ORG Tue May 31 17:00:49 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 D0E3A1065673 for ; Tue, 31 May 2011 17:00:49 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 642848FC1C for ; Tue, 31 May 2011 17:00:49 +0000 (UTC) Received: by bwz12 with SMTP id 12so5662641bwz.13 for ; Tue, 31 May 2011 10:00:48 -0700 (PDT) Received: by 10.204.26.200 with SMTP id f8mr1289118bkc.99.1306859779990; Tue, 31 May 2011 09:36:19 -0700 (PDT) Received: from amy.lab.techwires.net (p54B4C39E.dip.t-dialin.net [84.180.195.158]) by mx.google.com with ESMTPS id k10sm176242bkq.22.2011.05.31.09.36.18 (version=SSLv3 cipher=OTHER); Tue, 31 May 2011 09:36:18 -0700 (PDT) Sender: Bernhard Schmidt From: Bernhard Schmidt To: freebsd-hackers@freebsd.org Date: Tue, 31 May 2011 18:36:43 +0200 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.3; amd64; ; ) References: <4DE01421.7080902@rawbw.com> <201105311029.15259.jhb@freebsd.org> In-Reply-To: <201105311029.15259.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105311836.43543.bschmidt@freebsd.org> 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 17:00:49 -0000 On Tuesday 31 May 2011 16:29:15 John Baldwin wrote: > 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. Are you using -D bsd or -D ndis as the driver for wpa_supplicant? -- Bernhard