From owner-freebsd-current@FreeBSD.ORG Mon Jul 17 16:39:12 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 E2E1C16A4DA for ; Mon, 17 Jul 2006 16:39:12 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9676D43D45 for ; Mon, 17 Jul 2006 16:39:10 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k6HGd9vU031576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Jul 2006 09:39:10 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44BBBD2D.5030709@errno.com> Date: Mon, 17 Jul 2006 09:39:09 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.2 (X11/20060508) MIME-Version: 1.0 To: Neil Short References: <20060716224642.65943.qmail@web56511.mail.re3.yahoo.com> In-Reply-To: <20060716224642.65943.qmail@web56511.mail.re3.yahoo.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: ath (Orinoco) card cannot associate X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 17 Jul 2006 16:39:13 -0000 Neil Short wrote: > > ... > status: no carrier > ... > > > Sometimes this means the card has been turned off. My > computer has a little switch on it that enables me to > turn it off. > > If you run: > # ifconfig ath0 scan > and you can see your access point then there is no > problem with your card; but if it does not show up > then there is a physical problem with your card > (broken? turned off?) or your access point is down. > > As a simple test, can you bring up your access point > wide open and connect to it? > > If you can then the problem might be related to your > ifconfig statement. > > I am surprised to see such a long wep key. > > You might try simplifying your statemnt and avoid the > "wepkey" keyword. I spent probably a week with that > keyword and it simply didn't work. A helpful responder > in the mailing lists suggest I use instead the "nwkey" > keyword. Man, it was almost like magic. I was sure I > had done everything right - and I had; but "wepkey" > for some reason didn't work. It's there in the manpage > for ifconfig. FWIW this problem has been resolved. It was a firmware bug in his ap that was causing AssocResp frames to be discarded. I've committed a fix to HEAD. Sam