From owner-freebsd-questions@FreeBSD.ORG Wed Nov 9 01:37:37 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BAEF816A420 for ; Wed, 9 Nov 2005 01:37:35 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from S1.cableone.net (s1.cableone.net [24.116.0.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C6AB43D4C for ; Wed, 9 Nov 2005 01:37:35 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.vulpes (unverified [24.119.122.41]) by S1.cableone.net (CableOne SMTP Service S1) with ESMTP id 36652772 for multiple; Tue, 08 Nov 2005 18:37:57 -0700 Date: Tue, 8 Nov 2005 19:43:18 -0600 From: Vulpes Velox To: Stijn Hoop Message-ID: <20051108194318.1ce71700@vixen42.vulpes> In-Reply-To: <20051031182539.GA52720@pcwin002.win.tue.nl> References: <20051031182539.GA52720@pcwin002.win.tue.nl> X-Mailer: Sylpheed-Claws 1.9.15 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SpamDetect: ******************************: 152.000000 Content: cid=0(152.0) =152.0 X-NotAscii: charset=us-ascii X-IP-stats: Incoming Last 1, First 174, in=291, out=0, spam=0 X-External-IP: 24.119.122.41 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Cc: freebsd-questions@freebsd.org Subject: Re: cannot get IP working between associated ath0 & AP, what to do? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 01:37:37 -0000 On Mon, 31 Oct 2005 19:25:39 +0100 Stijn Hoop wrote: > Hi, > > I have an SMC PCMCIA wireless adapter, model SMCWCB-G, based on an > Atheros 5212 chipset, in a laptop running a fresh install of FreeBSD > 6.0-RC1. > > The card associates fine, but then fails to send any IP packets in > the air, or at least that's what I presume is going on. I cannot > ping the AP, I cannot get a lease using DHCP, basically the only > thing I can do is associate. I think it does associate because when > I set an invalid wep key, the status changes back to 'no carrier'. > Setting a static IP address does not help. > > Any hints on where I might go from here to debug this? I know the > setup should work because in a previous life [1] it Worked With > Windows[TM] (and on the same AP). If it is using wep, set the weptxkey. I had the same problem when moving from a laptop with releng_5 to a laptop with releng_6.