From owner-freebsd-questions@FreeBSD.ORG Thu Oct 7 21:11:36 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DAED106564A for ; Thu, 7 Oct 2010 21:11:36 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id DECBF8FC0A for ; Thu, 7 Oct 2010 21:11:35 +0000 (UTC) Received: by iwn8 with SMTP id 8so390590iwn.13 for ; Thu, 07 Oct 2010 14:11:35 -0700 (PDT) Received: by 10.231.167.196 with SMTP id r4mr1521990iby.29.1286485894861; Thu, 07 Oct 2010 14:11:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.166.77 with HTTP; Thu, 7 Oct 2010 14:11:14 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Thu, 7 Oct 2010 21:11:14 +0000 Message-ID: To: Paul B Mahol Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Mailing List Subject: Re: if_bwn woes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2010 21:11:36 -0000 On Thu, Oct 7, 2010 at 5:22 PM, Paul B Mahol wrote: > On 10/7/10, Eitan Adler wrote: >>> Looks like you cant associate at all. >>> Also signal power is too low. >>> >>> Why is INT (beacon interval of AP) 102 ? >> >> These are the defaults - I have no idea what these numbers mean. What >> should/could I be changing? > > I doubt that AP have capatibility to change that. > Anyway maybe you could associate if your txpower is big enough... > Sorry - I realized a brief portion of out conversation was done off-list. I just noticed that when I put in the ssid ifconfig seems to be cycling among multiple channels (1,5, 11,12,13 ,14 and maybe others). I'm not sure what this behavior means. What would the best way see why I can't connect be? I tried $ifconfig wlan0 txpower 50 but txpower stays at 30. Is this for sure a signal strength problem? it worked when I used ndis from the same location. -- Eitan Adler