Return-path: Received: from yw-out-2324.google.com ([74.125.46.29]:47522 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754734AbZDKO4F (ORCPT ); Sat, 11 Apr 2009 10:56:05 -0400 Received: by yw-out-2324.google.com with SMTP id 5so1538431ywb.1 for ; Sat, 11 Apr 2009 07:56:04 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <30353c3d0904101349o915439arffb652b98e245e10@mail.gmail.com> References: <30353c3d0904100736g69782d46g18d99edd0dd0660d@mail.gmail.com> <49DF9E38.5030801@lwfinger.net> <30353c3d0904101349o915439arffb652b98e245e10@mail.gmail.com> Date: Sat, 11 Apr 2009 10:56:03 -0400 Message-ID: <30353c3d0904110756qfc35928x265db523bd1f86be@mail.gmail.com> (sfid-20090411_165621_813968_5E6DD118) Subject: Re: b43legacy AP From: David Ellingsworth To: Larry Finger Cc: Michael Buesch , Broadcom Wireless , wireless Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: I wanted to report that I've finally been successful at getting b43legacy to beacon properly. Originally, I had configured hostapd to use channel 1. After reading the list of bugs for the bwi driver, shown here: http://leaf.dragonflybsd.org/cgi/web-man?command=bwi , I had the inclination to try channel 6. It appears b43legacy might have the same bugs as the bwi driver as I immediately began seeing beacons once I started using channel 6. Regards, David Ellingsworth