From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 22 14:30:38 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 76D5CACB for ; Mon, 22 Oct 2012 14:30:38 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 2EAEF8FC08 for ; Mon, 22 Oct 2012 14:30:37 +0000 (UTC) Received: from [89.204.137.104] (helo=tiny.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1TQHKR-0003hO-9M; Mon, 22 Oct 2012 14:41:59 +0200 Received: from tiny.Sisis.de (localhost [127.0.0.1]) by tiny.Sisis.de (8.14.5/8.14.3) with ESMTP id q9MCfuxq003736; Mon, 22 Oct 2012 14:41:56 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by tiny.Sisis.de (8.14.5/8.14.3/Submit) id q9MCft78003735; Mon, 22 Oct 2012 14:41:55 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: tiny.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Mon, 22 Oct 2012 14:41:55 +0200 From: Matthias Apitz To: George Subject: Re: Wireless network Broadcom not connected Message-ID: <20121022124154.GA3701@tiny.Sisis.de> References: <50852F81.1010007@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <50852F81.1010007@gmail.com> X-Operating-System: FreeBSD 10.0-CURRENT r226986 (i386) User-Agent: Mutt/1.5.21 (2010-09-15) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.204.137.104 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Matthias Apitz List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 14:30:38 -0000 El día Monday, October 22, 2012 a las 02:35:29PM +0300, George escribió: > I think it's a bug in the driver BWN (4), I tried all known variants and > the result is negative ... not connecting. Does anyone else have another > solution? > I checked the mail archive for this thread and do not fully understand what the problem is for you; I saw in some mails that the interfaces bwn0 and wlan0 both are "associated" and wlan0 does even contain a valid IP addr; what exactly is not working? routing? or what? matthias -- Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: guru@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards