From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 21 23:06:26 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 9B3A8A04 for ; Sun, 21 Oct 2012 23:06:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 67DEB8FC0C for ; Sun, 21 Oct 2012 23:06:26 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so1605979pbb.13 for ; Sun, 21 Oct 2012 16:06:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=JKCQXVL6SZsOXQO/4R/bgT7FHZ6AFzHd6zmOqaKsCtI=; b=lbf/jKRhkHfgG73iTV9AyYlJ2+KBphHVfzrDwdCgtFASGeskT+MxKfKXpou5ogLQDC 5pRugHH5JQsF3itrgNN1dsjfPeaKb7bgEjRjhE5BmvCqpBzkS56RnpOWIxRQ5rBSO+iB vE+qxU3e1ydmZu/XpIAaxonInpYR+XMENgAlb168xV13pNx2DrvPe7sd0+RrO4gKFh3r ZeuYF9qljfE8+ozsM5l0MLRGE5Hkwu/LFzKu7i2HXcm6ZeYvbhazTCUYezQkFpB9hH+F lKwFdBv6LUKVCt8qgfduO6qUSM3AJluQ1O9qcuDnGC/TFuptX+BZ5Gy6WJzGmLBWTDfM 08wA== MIME-Version: 1.0 Received: by 10.66.74.40 with SMTP id q8mr21405807pav.29.1350860786020; Sun, 21 Oct 2012 16:06:26 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.146.233 with HTTP; Sun, 21 Oct 2012 16:06:25 -0700 (PDT) In-Reply-To: <50847F5C.4030208@gmail.com> References: <50847145.6020301@yahoo.com> <50847B79.3080605@gmail.com> <50847F5C.4030208@gmail.com> Date: Sun, 21 Oct 2012 16:06:25 -0700 X-Google-Sender-Auth: u4YIdHeoVz7Vi85vBHhvPAJpkKc Message-ID: Subject: Re: Wireless network Broadcom not connected From: Adrian Chadd To: George Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list 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: Sun, 21 Oct 2012 23:06:26 -0000 On 21 October 2012 16:03, George wrote: > root@fbsd:/home/yo9fah # ifconfig wlan0 list scan > SSID/MESH ID BSSID CHAN RATE S:N INT CAPS > D.O.D 34:08:04:08:3c:14 1 54M -133:-95 100 EPS WPS HTCAP > WME > Nutunet 28:10:7b:62:fc:28 6 54M -129:-95 100 EP HTCAP WPA RSN > WME WPS > YO9FAH 00:22:6b:e9:5e:7a 6 54M -114:-95 100 EP RSN WME > cla@alex f4:ec:38:cb:53:42 4 54M -124:-95 100 EPS RSN WPA WME > HTCAP ATH WPS > TRENDnet 00:14:d1:34:6b:8e 6 54M -139:-95 100 EPS See how those RSSI values are all below -95? That's really quite creepy and worth investigating. > root@fbsd:/home/yo9fah # ifconfig wlan0 list sta > ADDR AID CHAN RATE RSSI IDLE TXSEQ RXSEQ CAPS FLAG > 00:22:6b:e9:5e:7a 1 6 54M 63.5 0 112 47296 EP AQE RSN WME > root@fbsd:/home/yo9fah # Same deal here. RSSI here is 0. That's invalid and bad looking. I'd rather look at trying to fix that up before moving on to the crypto side of things. Have you configured the AP in open (non-WEP/WPA) mode to see if it works? Adrian