From owner-freebsd-hardware@FreeBSD.ORG Sat Oct 14 04:21:30 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1F7E16A407 for ; Sat, 14 Oct 2006 04:21:30 +0000 (UTC) (envelope-from aharrison@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4702743D49 for ; Sat, 14 Oct 2006 04:21:30 +0000 (GMT) (envelope-from aharrison@gmail.com) Received: by nf-out-0910.google.com with SMTP id p77so1211992nfc for ; Fri, 13 Oct 2006 21:21:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=OH32aLOM3tPg0aeROi35x1WD+mq6zVEvxVgFa25i5hCrwkhea1yB+HRtnwV9rB83TxHdaZ4+RZgPOqm7avwHn79jdek110BwLSyeiKuigBynjX0R4Zrbob+IinzSlUSw2XBPGHk4jraWKq6WOCFZsGJoL2/AFErMWpgGRM7002I= Received: by 10.78.90.10 with SMTP id n10mr4659413hub; Fri, 13 Oct 2006 21:21:28 -0700 (PDT) Received: by 10.78.176.14 with HTTP; Fri, 13 Oct 2006 21:21:28 -0700 (PDT) Message-ID: Date: Sat, 14 Oct 2006 00:21:28 -0400 From: "Andy Harrison" To: "soralx@cydem.org" In-Reply-To: <200610122255.57752.soralx@cydem.org> MIME-Version: 1.0 References: <200610122255.57752.soralx@cydem.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: iwi: 'no carrier' X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2006 04:21:31 -0000 On 10/13/06, soralx@cydem.org wrote: > > > had anyone ever encounterd a problem with Intel 2200BG wireless card, > when the iwi driver seems to work normaly, but in reality it never > associates with an access point (i.e., 'no carrier' no matter what)? > the driver and firmware were all installed from ports, on 6.2-BETA2 Here's how I got mine working. I have my wap configured to use tkip. You probably won't need all of these options if you're using a simpler configuration. First, make sure your internal nic is not enabled. Here are the lines from my rc.conf hostname="example" bfe_enable="NO" iwi_enable="YES" ifconfig_iwi0="ssid MySSIDstring authmode wpa inet 192.168.66.66 netmask 255.255.255.0" wlan_acl_enable="YES" wlan_wep_enable="YES" wlan_ccmp="YES" wlan_tkip="YES" 192.168.66.66 is a bogus ip, it just doesn't seem to want to work right if you try to turn on dhcp at this point. Here are the lines from my loader.conf if_iwi_load="YES" wlan_acl_load="YES" wlan_wep_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" wlan_xauth_load="YES" When the machine boots, it will show my iwi0 interface status as "associated" by the time I log in a look at it with ifconfig. Then I just run: # wpa_supplicant -B -q -i iwi0 -c /etc/wpa_supplicant.conf My wpa_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 eapol_version=1 ap_scan=1 network={ ssid="MySSIDstring" scan_ssid=1 key_mgmt=WPA-PSK pairwise=TKIP psk="my passphrase string" } Then I'm ready for a real ip: # dhclient iwi0 If you have trouble associating with your wap, run the wpa_supplicant in debug mode: # wpa_supplicant -d -i iwi0 -c /etc/wpa_supplicant.conf The wpa_cli command might also be useful for further troubleshooting. -- Andy Harrison