From owner-freebsd-wireless@FreeBSD.ORG Mon Oct 22 00:08:40 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 5A911FA for ; Mon, 22 Oct 2012 00:08:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2599C8FC0A for ; Mon, 22 Oct 2012 00:08:39 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id bi1so1557595pad.13 for ; Sun, 21 Oct 2012 17:08:39 -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=tGKSSpV9B+394Ue6Qv1ImlMsFwsAV4ieYqPCw4uZ0pI=; b=X3cK7T3TbQdOvus6ls9GIBdKDJeEe82YP/9qs1S5FQHedO7CyAn8qpwAk9XcadeHHG MxbXNY+rk/cjqeMn7dvxdGuayUYNTK6aQfRkE2Uj1hQe+1hsRC1/Cp87FME0XdI6rg1A URQ26fGshIzUf36TYh5lO3P0rrl2TXjYad++wY39vsAq5ID9rynTluK8j8i3LI1czzc6 GZc18k/AKJiP9APtwu5Br74CEuxeoOZhD4w/3z0hxvAyIeK/xAhUwmHfyvDNr8+dp25/ rseGd41IrR95xtWq9BuVcbR5Y0b6jBuTP6pteMFyEj1KDxg8fFTbVPc2Mn6/whxi+wiA CHlg== MIME-Version: 1.0 Received: by 10.66.75.132 with SMTP id c4mr21794241paw.2.1350864519534; Sun, 21 Oct 2012 17:08:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.146.233 with HTTP; Sun, 21 Oct 2012 17:08:39 -0700 (PDT) In-Reply-To: <50848DDD.4050301@gmail.com> References: <50847145.6020301@yahoo.com> <50847B79.3080605@gmail.com> <50847F5C.4030208@gmail.com> <50848DDD.4050301@gmail.com> Date: Sun, 21 Oct 2012 17:08:39 -0700 X-Google-Sender-Auth: zvh9PtZw4pDUKE7PsQPEmOqKXn4 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: Mon, 22 Oct 2012 00:08:40 -0000 Don't rush things. * disable encrypion; * associate, then "ifconfig wlanX list sta"; * then "ifconfig wlan0", let's see what it's configured as; * do you run DHCP? Or is it static? * Can you ping the IP of the network gateway? adrian On 21 October 2012 17:05, George wrote: > Pe 22.10.2012 02:06, Adrian Chadd a scris: > >> 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 > > > I disabled my router to WPA2-personal,but it will not work either.Do > not give any error but the result is the same... > > root@fbsd:/home/yo9fah # ping google.com > ping: cannot resolve google.com: Host name lookup failure > root@fbsd:/home/yo9fah # > > > >