From owner-freebsd-questions@FreeBSD.ORG Fri Oct 24 17:08:00 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17C6C17D for ; Fri, 24 Oct 2014 17:08:00 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A08ECFA2 for ; Fri, 24 Oct 2014 17:07:59 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s9OH7poa009123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 24 Oct 2014 11:07:51 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s9OH7pmU009120; Fri, 24 Oct 2014 11:07:51 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 24 Oct 2014 11:07:51 -0600 (MDT) From: Warren Block To: Anthony Simm Subject: Re: wireless networking In-Reply-To: <544A7A19.4080405@gmail.com> Message-ID: References: <544A13D7.7000202@gmail.com> <544A539F.8080103@gmail.com> <544A7A19.4080405@gmail.com> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Fri, 24 Oct 2014 11:07:51 -0600 (MDT) Cc: FreeBSD Questions , Antonio Olivares X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Oct 2014 17:08:00 -0000 On Fri, 24 Oct 2014, Anthony Simm wrote: >> Anthony, >> >> Have you tried Warren's suggestion? >> >>> I would try to check if the driver that is required for that wireless >>> is loaded or not with >>> # kldstat >>> >>> if it is, then why is it not associated? > > > Hello Antonio, > > Yes, I just tried Warren's suggestions. > I overlooked the kldstat suggestion in the first place. > > Here is what kldstat gives > > Id Refs Address Size Name > 1 7 0xc0400000 1289f7c kernel > 3 1 0xc1697000 b9a0 if_wi.ko > > It seems to me that if_wi.ko should be a wireless driver. > > Warren's question as to why it is not associated really leaves me > blank-faced. I have no idea. Not my question. Your private mail identified it as ipw, an Intel 2100 card. That is more like what I'd expect, an Intel wireless card, in fact, an Intel 2100, which is the same thing my T42 has. The license has to be acknowledged for that to work. Add this to /boot/loader.conf: legal.intel_ipw.license_ack=1 Then the entries in /etc/rc.conf are: wlans_ipw0="wlan0" ifconfig_wlan0="WPA SYNCDHCP" Some good news and bad news about that card: Bad news: it is 802.11b only. Good news: that's usually good enough. Bad news: it does not support WPA. Good news: with a firmware update, it can support WPA. Bad news: there are no firmware updates. Good news: updating the Windows XP driver to the last version available silently updates the firmware on the card. Bad news: that driver has to be updated on Windows. Good news: Windows XP probably came with the system.