From owner-freebsd-current@FreeBSD.ORG Tue Jan 4 17:35:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEC6A16A4CE for ; Tue, 4 Jan 2005 17:35:44 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9975743D45 for ; Tue, 4 Jan 2005 17:35:44 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] (sam@[66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j04HZfWi076526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Jan 2005 09:35:44 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41DAD3E7.5000304@errno.com> Date: Tue, 04 Jan 2005 09:35:35 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jeff Stockett References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: problems with ath0 "no carrier" on freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 17:35:44 -0000 Jeff Stockett wrote: >> This may sound stupid, but it happened to me, too. Did you 'ifconfig >> ath0 up'? What is the output of 'ifconfig ath0'? > > > Yes, the interface is up (I learned that requirement early on). I > should have posted that though. Hopefully Sam or one of the other > developers will see my original message and help. > > ath0: flags=8843 mtu 1500 > inet6 fe80::20b:6bff:fe34:1b23%ath0 prefixlen 64 scopeid 0x2 > ether 00:0b:6b:34:1b:23 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (DS/1Mbps) > status: no carrier > ssid "linksys" > authmode OPEN privacy OFF txpowmax 54 > I've seen nothing that would help me diagnose the problem. Try building the 80211debug tool from src/tools/tool/ath then do 80211debug scan+assoc+auth and bring the interface up (this is roughly equivalent to ifconfig ath0 debug but 80211debug is much more useful for controlling the debug msgs in the 802.11 layer). The console log msgs should provide enough information to tell you what's going on. Sam